Reply to thread

Message

<blockquote data-quote="Rick164" data-source="post: 1179247" data-attributes="member: 17766">Attached a sample configuration file with your device settings and mine combined which are the default for testing, few questions / steps so we can test some things:- Is the Philps Hue bridge completely updated (thru their app)?- Re-run locate and register after using the new configuration file, if it doesn't work afterwards manually fill 192.168.1.112:80Tried it with a clean AtmoHue 0.01 (v0100) install under Windows 10 just now and while locating is slower (~10s) than it used to it found 10.1.2.74:80 and successfully paired, not sure why it would break on certain systems yet but must be either some incompatibility with the bridge or being blocked.// UpdateFinally finished the display of the bridge connection state (connected / disconnected) and should now always be correct, actual connection setup is still the same though and this is only so you know it has connected properly <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Test build is attached (0.1.1).</blockquote>

[QUOTE="Rick164, post: 1179247, member: 17766"] Attached a sample configuration file with your device settings and mine combined which are the default for testing, few questions / steps so we can test some things: - Is the Philps Hue bridge completely updated (thru their app)? - Re-run locate and register after using the new configuration file, if it doesn't work afterwards manually fill 192.168.1.112:80 Tried it with a clean AtmoHue 0.01 (v0100) install under Windows 10 just now and while locating is slower (~10s) than it used to it found 10.1.2.74:80 and successfully paired, not sure why it would break on certain systems yet but must be either some incompatibility with the bridge or being blocked. // Update Finally finished the display of the bridge connection state (connected / disconnected) and should now always be correct, actual connection setup is still the same though and this is only so you know it has connected properly :) Test build is attached (0.1.1). [/QUOTE]

Verification