Panda88

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

Can you send me (message me) a log with debug enabled - I only have the old lock and it works - it may need a new Driver - I should be able to see from log

Are you using the old or the new powerwall nodeserver (udiTeslaPW2) The latest should not need the token ( it gets it automatically). I have 2 powerwalls as well (older version). I only need one IP address for both. I think the IP address may be wifi and Ethernet but i do not know the latest versions

I made a new release with some of the requested changes Note, it does not address how to deal with Tesla wanting money to use the API (going forward) - we are looking at different options to address this, but no decision made yet. Note, unless you are on OS14, it seems like it is not possible to update the node - it needs to be reinstalled

Are you looking for notifications in udiMobile - or and automation in the AC I have not looked at notifications in udiMobile - will put it on my list to do You can easily make an ISY/AC automation to shut down when off grid and batter is below XX% If 'PWname' Grid Status is not on grid And 'PWname' Remaining Battery < XX% Then // Shut down some devices Else - No Actions - (To add one, press 'Action')

I woudl create a ticket on universal-devices to see what they say - it may be related to the coming update to os14

I think it is because some of it is cached when the AC starts so it is not aware if changes are made

Did you try a reboot?

Keep fingers crossed - continuing to work on it - I will have an updated version soon - with some more bug fixed

When installing the node a version update should be forced - it needs 3.3.x to support OAUTH. It may be a display issue but this is an issue in PG3. I would contact universal-devices to get help on this one