You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't try too hard to uniquely identify anything, but it is still grabbing unique IDs for my gear because they are all different models. It also does it far faster with less errors and lower latency than I can manage on ESPresense.
The way it handles switching between nodes is my favorite though. It has configurable RSSI "Present" and RSSI "not present" values where you can leave a gap in between. This gives devices room to jump around a bit in RSSI without flipping back and forth between nodes. Being the distance calculation is ESPresense usually doesn't even come close to the actual distance, dealign with RSSI values is more natural too.
Also, being able to manage all you nodes in ESPHome with full logs and OTA access is so much nicer, and doesn't lock the unit down to only doing presence.
I ended up switching back to ESPPresense for the following reasons
Identifying people instead of simply presence can be useful for personalized routines
It does not recognize my girlfriends Watch 5
Each of those is probably trivial to resolve for someone who knows what they are doing
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was playing with this repository last week and feel it has some good ideas on how it identifies and handles presence between nodes.
https://github.com/dalehumby/ESPHome-Apple-Watch-detection
It doesn't try too hard to uniquely identify anything, but it is still grabbing unique IDs for my gear because they are all different models. It also does it far faster with less errors and lower latency than I can manage on ESPresense.
The way it handles switching between nodes is my favorite though. It has configurable RSSI "Present" and RSSI "not present" values where you can leave a gap in between. This gives devices room to jump around a bit in RSSI without flipping back and forth between nodes. Being the distance calculation is ESPresense usually doesn't even come close to the actual distance, dealign with RSSI values is more natural too.
Also, being able to manage all you nodes in ESPHome with full logs and OTA access is so much nicer, and doesn't lock the unit down to only doing presence.
I ended up switching back to ESPPresense for the following reasons
Each of those is probably trivial to resolve for someone who knows what they are doing
Beta Was this translation helpful? Give feedback.
All reactions