Panda88

Did you try to run an update modules from the AC - if not try to contact Michel - he helped a similar issue I had

Sorry - it is an issue with having to update the version number multiple places (and remember to do it everywhere) when releasing the node. There are at least 3 places that needs to be in sync. BTW - you are correct - I did not update the run-time display of the node number to latest version I think PG3 compare that to the number in the node store to determine if an update is needed I did update the node number now - but I'll be looking to add a sleep parameter to the status node to update the car state so a new version will be required

Thanks - What about the node version besides purchase options in the developer page? I try to update both - My impression is it actually uses the node version for checking - you can show different version under purchase options as I understand - I may be wrong

Thanks It is a slightly different behavior than I would expect - I had expected the car to set online to False (and my code is working that way) - it almost looks like an issue connecting to getting data from the Tesla Cloud. The sleep feature is there indirectly with time since last update fields (assuming they work correctly) - but I can add a dedicated sleep state in the status node - with offline, sleep, online, and unknown states - does than make sense? I feel it is too much to say the node is not online - as it is after you wake the car - I see the connection as the indicator - not the car Do you have a little longer snippet of the log so I can see what happens next

Sorry - it is an issue with having to update the version number multiple places (and remember to do it everywhere) when releasing the node. There are at least 3 places that needs to be in sync. BTW - you are correct - I did not update the run-time display of the node number to latest version I think PG3 compare that to the number in the node store to determine if an update is needed I did update the node number now - but I'll be looking to add a sleep parameter to the status node to update the car state so a new version will be required

Thanks - I can update the app to use 'battery_range' Should not take long - look for 0.2.8 shortly

The range is a bug - I converted the miles to km for both miles and km - 0.2.7 is released The short poll currently supposed to check if car is on-line - if it is, it will poll car data - if not, it will use the cloud data without waking the car - Naturally this I what I believe the car is doing - There may be a bug. Naturally, I could use cloud data only - but then there is likely some delay - even when car is online (I have no way to check this as I do not have access to car) I would imagine plugging the charger in would wake the car - I am not sure

Just released 0.2.6 - some new functionality - A reboot of IoP is probably needed to enable all

Just released an update - I hope it fixes the disconnect issue - I think over time I was consuming the 5 connections that are allowed by Yolink - I believe I disconnect before reconnecting now - but it could mean a few sec of no connection (only happens when link is down anyway) Also added support for smart lock

Just released a node to control Blink Cameras Mostly to control arming and disarming, but one can also take a snapshot and a video on demand - Node can email pictures by email (as they get overwritten) - videos can be viewed in Blin App (I'll look into email videos as well) there is a bug in the API - it cannot handle special characters in the camera/Syncunit names I would love to support automatic notification if motion is detected, but have not found a way yet - Yo can poll for motion, but do not poll too often or blink will throttle the connection

Moved server to production store - Added support for email pictures

I believe it occurs if you enable 2 way authentication

It should report if the auth key is missing - I think it is only needed first time you log in with the credentials I remember adding it once (get it from the app) - but I have never seen it again so I really do not remember what I did - sorry SYNC_UNIT is the sync unit (module name) - the cameras registered on that unit will show as sub-nodes - it is a separate node in ISY - not under the controller . You can specify NONE for the sync_unit - it will list all the cameras you have under a syncunit namesd NONE - it is not optional - I either need a list of sync_unit names or NONE Send a log file and I can see what is happening

Uploaded a beta version of a Amazon Blink camera control node server Primary function is to control arming and disarming of cameras, but it also allows taking pictures and videos Might be a few bugs left - still ironing them out

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