Panda88

Maybe you can try to stop the regular node server while testing I found part of the issue with the new lock - I can likely get to retrieve data fairly easily, but controlling it may be more difficult without documentation

Seems like the log you sent is old Can you generate a new one - manually opening the lock and then try to control it from teh AC as well . I am a little guessing on the control (until official API is posted)

can you generate a debug log where you open and close the lock and query it

Seems there is an issue - you can try to reinstall I changed the install style

is there a log? Can you try to install in different slot?

It takes some time to propagate - you can try refreshing the page but it can take up to a couple of hours before posting

look for it now

Sorry - I forgot I set it up with fixed file It will have to wait until I get back home - after 4pm PST

Found a bug - please try to delete and install again = hopefully it will show 1.3.13

I seems you got an earlier version where I limited the devices (and not included the lock) - I just put 1.3.12 up - try to update - it may take a little before it is ready

look for 1.3.11 in the non-production store - testYolink node yes - you can store in a separate node (maybe stop your existing one while testing) Make sure you install again - I forgot to add the new lock in the previous version

I did not release a beta version yet look for 1.3.11 in the non-productionstore - testYolink node

It I make a beta release - can you check if the lock works?

i believe it is real. it is not the nls file is parsed. i am using global definition for some common nodes. it seems the rest does not pick this

can you send a log - it should refresh automatically

It seems the command was changed - I'll see if I can support both ways in the lock device

If someone can tell be the command sent from the insteon device, I can see if I can make it work

I found the difference - I use global naming for some of the common parameters - these do not seem to propagate to the REST - but works with AC. Not sure if global naming is supported but it works with AC Maybe ask UDI if it is a bug or if I cannot use global naming I'll fix it if global naming is not supported (but it is some extra work (and a lot of testing) -

i’ll try to see if can find something in the node def setup files. there may be something missing

can you send me a log file? what version is it reporting?

can you send me a log file?

I'll add it in a coming release - with current API

it does not show in the released note but there have been some updates that did not populate so it may be an older version

I cannot find the bad link - which one are you referring to? I'll try to fix it

I hear back that there is a new API, but be old one may work ok for now - the new one is not released yet