Anyone else seeing HUE stop connecting after a few hours? I have a SmartThings and Hubitat Hub and Brilliant switches all connecting to the Hub with no issues. Any clues?
Logger: homeassistant.config_entries
Source: config_entries.py:1049
First occurred: 7:05:10 AM (20 occurrences)
Last logged: 11:05:10 AM
Config entry 'Hue Bridge ’ for hue integration not ready yet: Error connecting to the Hue bridge at ; Retrying in background
thats the problem, Nanoleaf sucks. I was not been able to apply any update for over a half a year already. It gives me errors all the time.
O M G. This makes me so happy. My Switchbot’s finally native into HA and responding thanks to the Bluetooth Proxy update! I can drop the ESP solution finally and rewrite my automations to use the native devices instead of MQTT!? Really happy as somebody who’s Switchbots are generally out of range of my Home Assistant.
I do not have any Bluetooth adapters plugged into my HA and BT proxy works with my switchbots now.
I’ve had this problem several times before as well. Try removing it from nanoleaf/HomeKit and factory resetting it. Not sure if the same procedure for the strip lights, but turning the bulb on and off 5 times quickly initiates the reset. Then re-add it to nanoleaf/HomeKit and then try the firmware update.
Me too. Pretty sure I dont have any ibeacons.
Could it maybe a tile tracker I have lying around somewhere?
When I first enabled ble sensors last release I started seeing my neighboors grill temperature sensor. I was tempted to text him that his grill was at the correct temp
Ive got an inkbird bt temp probe… might give it a try…
Have you figured out what device it sees? It is growing for me (again). Upto 25 devices, most are unknown.
Thanks for yet another comment. Why are there always only people responding who feel addressed but can’t really help. I’d rather have someone who doesn’t speak up but says: "I know what it is. Communication via docker has changed. I have to adjust this and it works again. "
People who are not responsible for this should not feel offended. By the way, you do have a point. I will add a link next time because I even had trouble finding my problem again.
And as for updating. When I update, I can no longer use Appdaemon and my wall-mounted iPad is unusable with a black screen.
No, only recognize the Govee, the rest is jibberish
I mean I feel like I did help? You gave random numbers, I turned them into links that humans can click and follow. The second one is pretty relevant as there’s a ton of discussion. Having that link increases the chances someone can help. As someone who has debugged a lot of addon and supervisor issues I can tell you your first post didn’t have enough info for anyone to figure out what was going on.
I mean I might be responsible, I am one of the main supervisor devs. I’m not offended though.
If you can’t update supervisor then you should submit an issue here. Although it sounds like you can update supervisor it’s just doing so breaks appdaemon. Which based on the discussion in the linked bug above sounds like an issue for here.
Alright, I guess my bluetooth devices just don’t work with this setup. I am trying to get the Yale Access Bluetooth integration running and it keeps failing to initialize or says to move the adapter closer, but it is two feet away.
Is your supervised system in a healthy state? I can install and run appdeamon on my NUC running HA Supervised without issues.
As I said you where absolutely right about the links. As you might have seen I added the links and even an extra one with the same issue reported as an add-on issue.
And forget about supervised. That is solved. I only can’t upgrade HA-releases on my NUC because of AppDaemon. By the way I saw issue #207 was closed again but not solved.
I think you’re behind on all the necessary updates that Supervised has gone through over the past year.
