Reply to thread

Message

<blockquote data-quote="pavke" data-source="post: 1179399" data-attributes="member: 11916">BREAKTHROUGH !I searched around for some info on the Hue API, found this web app with which it is easy to test the various API calls and set off to x-ray my bridge. One thing that soon became clear, is that the pairing had worked before, because I could retrieve a good number of paired 'users'. What was clear also, is that their 'names' didn't look anything like the credentials used in AtmoHue - more like &quot;24e04807fe143caeb52b4ccb305635f8&quot; or so.However, when I plugged one of these keys into AutoHue, things started working perfectly... !Status was 'Connected', all tests worked, and it even worked with MediaPortal when I did a quick test.So, the (or at least: my) conclusion is that when you pair with the bridge, you use a format that results in a registration that does not quite look like you expect. That, or you do not retrieve the correct 'user name' to use as HueAppKey after pairing - all of this probably due to the fact that the user-creation API has been slightly changed, at least that's what I think.Shouldn't be too hard to fix ... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="pavke, post: 1179399, member: 11916"] [B]BREAKTHROUGH ! [/B] I searched around for some info on the Hue API, found this web app with which it is easy to test the various API calls and set off to x-ray my bridge. One thing that soon became clear, is that the pairing had worked before, because I could retrieve a good number of paired 'users'. What was clear also, is that their 'names' didn't look anything like the credentials used in AtmoHue - more like "24e04807fe143caeb52b4ccb305635f8" or so. However, when I plugged one of these keys into AutoHue, things started working perfectly... ! Status was 'Connected', all tests worked, and it even worked with MediaPortal when I did a quick test. So, the (or at least: my) conclusion is that when you pair with the bridge, you use a format that results in a registration that does not quite look like you expect. That, or you do not retrieve the correct 'user name' to use as HueAppKey after pairing - all of this probably due to the fact that the user-creation API has been slightly changed, at least that's what I think. Shouldn't be too hard to fix ... :) [/QUOTE]

Verification