While in the process of migrating from my ISY94i to ISY on Polisy, I'm attempting to clean up loose ends as I find them.

One I've run into today is attempting to surface my Kasa TP-Link plug (via the Kasa Node server) to Alexa. In the ISY portal, I wasn't able to add it, getting the error: "HTTP error 400 : Device cannot be added to the spoken database". I researched the forums and the wiki to find that I needed to add a device hint "2.0.0.0".

When I edit it in the Device Hint Indicator all looks fine:

And I get a successful hint updated message but I continue to get the error "HTTP error 400 : Device cannot be added to the spoken database" when I try to add it to the Amazon Echo device list in the ISY Portal.

Oddly, when I pull up the same device again in the editor, it shows the hint values reversed!

So, I tried entering it backward 0.0.0.2 and that apparently saved it as 2.0.0.0 and then I was able to add my plug.

It seems the Hint Editor is not working correctly on the Portal.

I'm on Polisy v.5.4.4

 

Edited May 26, 20223 yr by DaveStLou
Added firmware version

On 5/26/2022 at 11:39 AM, DaveStLou said:

 

And I get a successful hint updated message but I continue to get the error "HTTP error 400 : Device cannot be added to the spoken database" when I try to add it to the Amazon Echo device list in the ISY Portal.

Oddly, when I pull up the same device again in the editor, it shows the hint values reversed!

So, I tried entering it backward 0.0.0.2 and that apparently saved it as 2.0.0.0 and then I was able to add my plug.

It seems the Hint Editor is not working correctly on the Portal.

I'm on Polisy v.5.4.4

 

In the enclosed list, what is the format I would use for a Zone?  I get errors for most things I try. 

Do I need to start with the parent and the sub categories? or just 0.0.0.2?

 

Really trying to do a dimmer switch via a node.  Thanks.

 

 

In reading further posts, specifically the one below, I think it would be 1.1.2.0

For a dimmer switch it would be: 1.2.9.0 ? 

Opened an Elk Node for an output and it was prepopulated with 4.3.2.1, yet in PG3, it looks to be the reverse: 0x01020304

So entered it as 1.2.3.4. It came back as 4.3.2.1

Then I decided to try entering it as 1.1.2.0. It accepted it, but now that node is no longer visible in the drop down menu to change it back to its original setting. 

 

Something is clearly amiss in this area.

On 7/7/2022 at 9:41 AM, dbwarner5 said:

Something is clearly amiss in this area.

Agree, this is still broken. I just entered something and found I had to enter it in reverse order to get it to work.

On 7/7/2022 at 9:41 AM, dbwarner5 said:

Then I decided to try entering it as 1.1.2.0. It accepted it, but now that node is no longer visible in the drop down menu to change it back to its original setting.

My node did not disappear. In order to change it back to default I had to enter it as 0.0.0.0. I was then able to change it to the reverse order work around (e.g 0.0.0.2 -> 2.0.0.0).

@Michel Kohanim Should I open a ticket on this or is a known issue?

@dbwarner5,

Yes, please!

With kind regards,
Michel

Refreshed my ticket on this subject as device is still missing in my portal. thanks. @Michel Kohanim

@dbwarner5,

Thank you. Definitely a bug and related to big/little endian conversion from 994 to Polisy.

With kind regards,
Michel