Panda88

I am not using the IP address directly - I do an updateProfile() that may read data from ISY/IoP and that will fail in your case. Other nodes may not do that - just guessing I am doing the same as you - so I have no magic setting - I do not think you can use local loop on the IoP connection (127.0.0.1) - it would be nice, but I think I tried and did not make it work

Looks ok - maybe restart AC and see if that helps

It should not take that long - do you have a log file?

It does look like an issue to connect with PG3 - I have noticed the same with another node - when uninstalling and reinstalling that node it went away (ping node) I'll see if I can figure out why this happens

Looks to me like the node server is doing what it is supposed to do - it is getting commands and updating values - not sure why it does not get to ISY . I'll need to dig deeper, but it may be related to 3.1.10

Posted 0.5.5 on beta site Trying to improve connection stability - improved QoS strategy There have been a few outages from YoLink side the last week or so

On controller functionality in scenes on IoP I have been looking at emulating switches (and outlets for that matter) as controller for ISY/IoP. Unfortunately there is no way to identify a key press vs a state change - My assumption is only a key press should result in a control event for a scene. I could have the device send (DON/DOF - control for scene) on all changes of state but it is not emulating what Insteon does. Not sure how to move forward on this - Any inputs My current thinking is to let sensors send DON/DOF but not to enable it for switches/outlets - Garagedoor controller can send both DON and DOF when pressed (as there are no other ways to control it - although it is not a keypress per say) That said programs are an easy way around this Let me know

Did a quick release of the retrying to connect on error 5 Give it a try to see if it helps NO other changes included

It is the same error - it is somehow losing the credentials - I am trying to add a fix for this - but I am looking at improving the nodes DON/DOF behavior (A few days is my hope)

no problem - I will assume it is the same issue

I saw you restarted it Do you have a log from last night to ensure it is the same issue - It is likely an issue on YoLink side, but I can try to see if there is a way to handle it I may issue a beta release you can try - in order to not effect other users I am looking at supporting fast on off etc. Still working on the possible use scenarios

It suddenly complains about authentication error (nothing seems to happen before that) - not sure how that happened Maybe I need to handle that case differently - complete disconnect and reconnect (not sure) - right now I am just trying to reconnect as I was told by the yolink people It seems it came back online at the end of the log file There is still a race condition when the node server starts - I am trying to find a way to get a more controlled startup (not relying on sleep) - but I am still trying different ways

Got it I think the push is offered by the Phone - you subscribe to a push and the push is send to the phone that then wakes the app etc. I do not see a way to do this using the API - I can see if a SW update is pending from the API but not push a message - I get the info when polling data

Is it the estimated range you are looking for? Any other fields - e.g. estimated full range? Let me know and I can give it a try in next release

Log File shows authentication error - Maybe try to generate new credentials and restart

What devices are you using? Do you have a log file - It works fine with my devices - I think you need to restart the ISY session for it to take effect

I released ver 0.5.1 - It fixes a delay for the motion sensor (bug on my side).

Just uploaded version 0.5.0 Probably have some bugs - Let me know if it can remain on-line I'll keep testing the coming days, as I am sure there are still a few bugs (did a lot of rewrite to the core), but hopefully someone will try and let me know of issues

I think I found the issue with power strip - mine does connect without issue now

Just a quick update - I think I found my issue and I am updating the code What I have done to test is disconnect my ethernet cable and then reconnect it to make sure the node server recovers after it is reconnected Any other ideas on how to test it? Thanks

yes - if you poll often the car never goes to sleep (I am told) - Unfortunately I do not have a Tesla so I cannot experiment Setting the long polling interval to a large number allows the car to sleep - you can wake the car (from the ISY) if you want data updated

I am trying to figure out why the connection to the YoLink API is lost - I am also working on a way to detect a disconnect and re-connect but I really hope to find the root cause

I hope Bob can help this issue

Not that I am aware of - it appears the YoLink is loosing the connection - I am trying to discoven when it happens and reconnect

Hi I have been working on some improvements (keep fingers crossed) - I believe the issue is the same as I have been trying to fix - but have been travelling lately - I'll try to fixes once back next week and then release once my local build seems to work