nearest scanner doesn't match detected area?? #539
Replies: 9 comments 8 replies
|
Are you sure the proxy/scanner has been assigned to the correct room it is actually in? |
|
Attached is a screenshot. |
|
I mean, I believe you if you say so. 😄 Just trying to eliminate / double check the obvious issue first. |
|
👀 Yup, that's weird! Let's call it a privacy feature, that Bermuda won't follow you into the bathroom. The Is it repeatable enough that you can grab a diagnostics when it's in this state? From that I might be able to work out what's going on. |
|
Yeah, consistent. I can download the diagnostics this evening. |
|
Should I go ahead and filter out non bermuda stuff? file is 105meg. I can try to do a quicker test later for another diag or i can filter out a bunch of the other stuff. |
|
As long as you're able to transfer it that file size is fine with me. If it's the diagnostics then everything in there is Bermuda-related, but if it's a debug log (which might be more likely given the size?) then there might be other stuff in there. I'm interested in Bermuda, ESPHome and Bluetooth things, if you are looking at filtering the file. |
|
i am also thinking of flashing that same esphome setup to another node to test. |
|
Anything happened on this as I am getting the same thing happen. |
|
I have revisited this. I unplugged my masterbedroom node, and sure enough it still showed up as the master bedroom even though i was attached to the bathroom node. I looked and there was another device (unifi) that was attached based on the mac address to the same ha "device" that one had an area attached to it. So I think the issue I ran into was this related to this. I have removed the areas and readding them and readding my esphome device. Will report back shortly. |
|
Ok. I can confirm that seems to be the case. Either bermuda was holding on to an area (unlikely) or it's possible if you have another integration that uses something like network mac addresses to add more entities a device, that integration device could have an area assigned. I removed my device from unifi integration and esphome and re-added to both and it's all working now. |
|
I am having the same issue however for me it's that at least for this proxy (haven't tested others and currently not home) Bermuda is not reading in the new area for the proxy. I changed the area for it and the nearest scanner is accurate but the area is the old area for the proxy. I tried reloading the integration and rebooting HA. I could try removing the proxy and re-adding it to HA but I suspect Bermuda should honor area changes. |
|
Actually I just noticed that I changed the ESPhome entry but not the Bluetooth entry. Updating that then reloading the Bermuda integration fixed it. I'll need to read up more as to why there was a separate Bluetooth integration. However, Bermuda probably should listen to area change events. |
|
Yeah, it was a HA decision to make the bluetooth element of an esphome device a separate "device" in HA. Bermuda checks both devices, and if only one has a defined Area it will use that, otherwise it prioritises the bluetooth device's Area as it can only assume that the user intention was to have the bluetooth device declared as being in a separate area than the esphome device. It's not a great situation and I will be answering this exact question every week for the rest of my days, but I can't see a better way to handle it in Bermuda. I could throw a "repair" warning if it detects the two devices have different areas, but it's a completely valid choice for a site to set themselves up that way. Bermuda does listen to the device registry to catch Area changes, did it update itself when you changed the bluetooth device's Area setting? If it didn't that's a bug, but changing the esphome device's area should not have resulted in an update. |
|
Good to know Bermuda will use the ESP Home's area if the Bluetooth's area is unset. You could throw this info into the troubleshooting section of the Wiki. That should help people like me that don't notice that the bluetooth proxy gets its own device and area that does not auto-sync with the ESPHome device. Personally, I'm going to see if I can set up an automation to throw a repair or even auto fix in those situations because that's how I choose to configure it but like you said, some people might have a valid reason not to. So if you did make it throw a repair, it could be an optional feature (that I would personally turn on and appreciate!). I'll test today after work. After I saw that the BT Proxies were their own devices I changed the area then checked my Tile tracker's entry in Bermuda. It did not update in bermuda. Perhaps I did not wait long enough and Bermuda needs the tracker to be seen again before updating it? I can test again today after work. |
|
I changed the area for the Bluetooth device and it did not update the area of my tile tracker until I reloaded the bermuda integration. I even tried moving the tile to another room, confirm that bermuda update, then moving it back. Related, I just extracted the IRK for my android and added it as a Private BLE. It did not show up in bermuda until I reloaded bermuda. I am on |
|
Thanks for going through that and checking - certainly looks like there are some gaps in Bermuda's area update listeners - and I'll have to check the irk one again too - i know others have hit that previously but sounds like it's not quite sorted yet. Good call re the FAQ / Troubleshooting, I've added an entry for it 👍🏽 I'll look into the change-detection issues. |
Uh oh!
There was an error while loading. Please reload this page.
I am guessing it's something with my ESP32 esphome bt proxy, but I have a BT proxy in my master bathroom. When I am in there it shows i am in the master bedroom. I enabled the "nearest scanner" entity and oddly enough it said that the nearest scanner was the master bathroom, but the "area" entity for my device still showed the master bedroom. Not sure what I did or how to test / correct. Any thoughts?
All reactions