Recently Hue has updated the Firmware (swversion) of their Bridge.
A new Software Version is introduced.
In general diyhue does not use the swversion. It is only used for emulation.
However: Changing swversion can also imply changes to how things are handled on genuine hardware.
That being said it is possible that updating swversion without changes to diyhue could cause bugs.
In order to Update your swversion follow these steps:
OLD MASTER BRANCH (DEPRECATED):
Stop Emulator or Docker Container
edit config.json
in key "config" change "swversion":"XXXXXXX" to "swversion":"1949203030"
Note: do not change version in Lights!
save
restart Service or Docker Container
CURRENT BRANCH (MASTER):
Navigate to your diyhue Web UI
Edit Bridge Config via Web UI
API : 1.49.0
Software Version: 1949203030
Update Message should be gone.
Best Practice is to Pull the latest Docker Image and redeploy!
Dev Note: you can set "swversion":"1999999999" to eliminate any future update requests but be advised as this may cause unkown error.
Hi Mevel, i did update the SWversion in the config. The hue app is not asking for the update anymore but has the message making connection and won’t pass that screen now.
you can try and delete the app cache on Android or reinstall the app on iOS. might be a problem with the certificate then.
also:
we recommend Hue Essentials App for Android and iOS. We are in close contact with the dev.
note: since May and in particular with this swversion the new Hue API v2 is in place. However the new API is reverse engineered at this point and implemented in the beta branch.
you can give it a try
does that work out?
I just got my first hue devices and a hue bridge, and I’m trying to get a diyHue up and running to unify some other lights with the Philips bridge. I’ve followed the steps suggested in the original post, but it’s not working for me. Something I’ve noticed though:
In the Hue app, my genuine Hue Bridge has a software version of 1.45.1945091050.
When I run the docker version of diyHue, I can get the emulated hub up and running. I can see the activation button page at {ip address}/hue/linkbutton, and from the Hue app I can even successfully find and connect to the hub by searching for the ip address, however it demands I update the software on the hub. If I enter 1945091050 then I can see the hub in the Hue app, and I can see the link button page just fine, but it the app still says the software version is wrong.
If I try to enter 1.45.1945091050 into the config.json file, then the docker no longer runs. I can’t see the hub in the app, nor can I access the linkbutton page.
Has Philips changed their software versioning schema? Does the inclusion of the periods break something in the json? I shouldn’t think so since there are a lot of other places where they are allowed.
well, it’s a step forward. I was able to update the config.json (after I was having problems to get the configuration changes to stay changed, until I read three times again your steps that said to stop the service before changing the configuration)
so now I am:
able to connect the the hub,
I do not receive the update request,
I’m able to click the button on [IP]/hue/linkbutton and having the hub recognize that
The next step would be to complete the inclusion of the hub in the Hue App,
but that’s where I’m stuck, as it keeps trying to connect without ever succeeding.
Maybe because I have an actual hub and this would be a second one (to add wLED lamps)?
I was able to add the hub to “Hue Essential” and to add a light there, but that’s not what I’m looking for.
I want to use the Hue app.
