Open tbgoose opened 1 month ago
Ah, yes. The hue app checks some external server at philips for the "correct" software version to expect.
Bifrost is currently reporting a hard-coded string for the version number, so that's going to cause problems.
I'm working on a branch that will allow Bifrost to automatically update to the newest version found online.
In the meantime, you might be able to work around this problem, like so:
state.yaml
in an editorsoftware_version:
where the value is 1.66.1966060010
1.66.1966060010
with 1.66.1966117030
This may or may not be enough, and is only intended as a temporary workaround, until we get the new branch landed. But maybe you can give it a try?
Hi @chrivers
I have tried the workaround and unfortunately it did not work. I have a hue zigbee hub and checked the version currently running it's the "1.67.1967054020". I did change the values in both of software_version instances, however it does not work and when I go to the bifrost bridge information on the hue app it still show the hardcoded version "19660660010" and not "1.67.1967054020" also no point between numbers as opposed to my official hue Bridge.
do you know if there is somewhere else that hardcoded version so I can changed it ?
Thanks for your help
Since yesterday I can't access hue and receive the following message. Can't get past it and obviously it doesn't update...
Any idea how move past this? Presume it was related to my former bridge, which is now removed from the hue app...