Reply to thread

Message

<blockquote data-quote="Rick164" data-source="post: 1179293" data-attributes="member: 17766">Yeah, that one is fixed in attached build <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Still not sure what is causing it at this point because if it fails to connect with the AtmoHue_v0101_TEST3 build then it means the bridge just isn't reachable, could try a different app name and key to rule out any issues with it but it shouldn't make any difference .Also make sure no other Hue apps are running at the same time on the same machine.Correct, that is something that the bridge does although not consistently with a :80 (webserver port) suffix.For now I trim that off so that you are left with 192.168.1.112 however either with or without :80 it works here and for a few others a while back at least as the underlying library (Q42.HueAPI) accepts both formats.</blockquote>

[QUOTE="Rick164, post: 1179293, member: 17766"] Yeah, that one is fixed in attached build :) Still not sure what is causing it at this point because if it fails to connect with the AtmoHue_v0101_TEST3 build then it means the bridge just isn't reachable, could try a different app name and key to rule out any issues with it but it shouldn't make any difference . Also make sure no other Hue apps are running at the same time on the same machine. Correct, that is something that the bridge does although not consistently with a :80 (webserver port) suffix. For now I trim that off so that you are left with 192.168.1.112 however either with or without :80 it works here and for a few others a while back at least as the underlying library (Q42.HueAPI) accepts both formats. [/QUOTE]

Verification