Reply to thread

Message

<blockquote data-quote="pavke" data-source="post: 1179290" data-attributes="member: 11916">Must confirm just about all of michi216's findings. Also with the latest version, the bridge is only found when Win 8 is unchecked (although both PC's I test with are on 10) - but that's where it stops. Status now always shows 'disconnected', and none of the tests work.What looks strange to me, is that upon startup it says[ 15:23:13.145321 ] - Hue bridge failed to intialize[ 15:23:13.145321 ] - Connection to bridge was successfulalthough Status keeps saying: disconnected .. ?I also have the old bridge, with the newest firmware.Attached please find my settings.xml file...And btw, it still crashes when no ip is present in the settings.xml file.[DOUBLEPOST=1458572383][/DOUBLEPOST]I'm not sure, but in some settings files I see e.g. 192.168.1.112 as the ip, in others 192.168.1.112:80 (presumably the port number ?). Could that account for the invalid ip warnings ?And is the difference that the one format is as set through standard discovery, the other using SSDP discovery ?Could it be that it works for you, because you had it paired before (with an older firmware maybe) - and that with the newer firmwares the pairing itself fails ? Just guessing, because I have no idea whether the bridge pairs based upon the pc name or other id, the program name, the program version, your ip number, ... ?</blockquote>

[QUOTE="pavke, post: 1179290, member: 11916"] Must confirm just about all of michi216's findings. Also with the latest version, the bridge is only found when Win 8 is unchecked (although both PC's I test with are on 10) - but that's where it stops. Status now always shows 'disconnected', and none of the tests work. What looks strange to me, is that upon startup it says [ 15:23:13.145321 ] - Hue bridge failed to intialize [ 15:23:13.145321 ] - Connection to bridge was successful although Status keeps saying: disconnected .. ? I also have the old bridge, with the newest firmware. Attached please find my settings.xml file... And btw, it still crashes when no ip is present in the settings.xml file.[DOUBLEPOST=1458572383][/DOUBLEPOST]I'm not sure, but in some settings files I see e.g. 192.168.1.112 as the ip, in others 192.168.1.112:80 (presumably the port number ?). Could that account for the invalid ip warnings ? And is the difference that the one format is as set through standard discovery, the other using SSDP discovery ? Could it be that it works for you, because you had it paired before (with an older firmware maybe) - and that with the newer firmwares the pairing itself fails ? Just guessing, because I have no idea whether the bridge pairs based upon the pc name or other id, the program name, the program version, your ip number, ... ? [/QUOTE]

Verification