Help dialing in speed of node handoffs... #359
Replies: 2 comments 1 reply
-
So, Ive updated the config file... and its actually worse...
|
Beta Was this translation helpful? Give feedback.
-
The With the "time to drop from one node to the next" you are referring to the time it takes for the sensor to update once you have left a room? In that case: Bluetooth Classic is not a fast way to detect presence, since that only works in a round robin fashion. One device to be tracked can only be inquired from a single instance at a time, while one instance can only track a single device at a time. That means a full scan will always take |
Beta Was this translation helpful? Give feedback.
-
Hello fellows...
So, Ive got 8 RPi Zero Ws at the moment throughout my house... looking to add an additional 10 (or so)... but dont want to keep moving in 1 direction unless i can get these things dialed in..
So, for starters... the length of time to drop from one node to the next is INSANE... like, 30 seconds or more...
(That is on my Galaxy S10+ using bluetooth classic... im having a heck of a time getting BLE to work with any kind of consistency on my Galaxy Watches, but am less worried about that at the moment...)
I have to assume theres something i screwed up...
I set up following the general guidelines on romeassistant.io for classic bluetooth... i then followed the few instructions for BLE... I then installed the newest version of BlueZ (i was having major issues with i/o using hcitool lescan (I would get: Set scan parameters failed: Input/output error, unless i restarted the dbus service... still have issues after updating BlueZ)...
Anyway, below is my config file... its the same on my HA build running a plugin for RA as it is on each RPiZw
(I am unsure how to bracket CODE...
Additionally, i get spam errors in RA:
Beta Was this translation helpful? Give feedback.
All reactions