Panda88

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

It should be ok - just realize you cannot control the power wall when only connecting locally You can look at readme on how to get the online token

Hi Somehow the requirements.txt files was missing in the latest distribution - it forces the install of the tesla_powerwall module and after that it hopefully works Let me know if this solves the issue

I have not given up - I am travelling and will not be back until early August - I have some code ready but need to test it locally so it will have to wait until I am back

I think CLITEMP must have special properties on ISY - I changed it to generic value - hopefully that allows the unit to update I think you thinking is correct on the long and short poll I found that I did not wake the car before different commands - I hope it is fixed now I may have had a typo (capatalize) in the online command - see if it works now 0.1.15 releasing soon

0.1.13 released - should fix temp setting issue

probably not -

Do you have a log - just making sure it is the same scenario as I am trying resolve

added a little debug to code - can you try to run with debug in log and send me a part of the log when you temperteu updates and when you set unit to F thanks

Let me see if I can find the bug on temperature - I do not know the timing for going to sleep - I wake the car on every communication if needed so changing the poll seems right

Thanks I think there are still a few more tweaks needed, but it is getting closer Can I assume that everyone has a hub in their setup? I need a common device to ping regularly

Released new version 0.1.9 to address changes in the tesla API

Just released 0.1.11 to address changes in the Tesla API Let me know if it works as I do not have a car to test it on - works for the power wall

Correct - most changes are related to the connection to Yolink - as mentioned I am still waiting to hear the best way to know if the connection to Yolink is still active or just appear to work - I have not heard back yet on this one, but released 0.4.4 as it does improve connection stability

0.4.3 Did a small change to how often the MQTT Check for connection - it may help the lost connections - I have not had a chance to check, but it should be change Still travelling so no access to setup

I normally use WinSCP to move files to and from Polisy. There should be 3 text files containing the packet seem from YOLink API - It is jus the raw packets with timing added Maybe you can check if the event that are supposed to happen are there - then for sure it is my code

I am also trying to understand what is happening, but it is not easy - I believe the MQTT connection is somehow shutting down -the code stops receiving the messages being sent (even with external sniffer). Note, the YoLink app must use a different API than the one that is presented to external users, as it has more information available that what the API I use offers. I have noticed that it seems that only 1 credential can be used - e.g. you cannot use the same credential for multiple applications (ie. running both on HA and Polisy). - only one for them seems to be served by the API If you know how to log into polisy and retrieve files there are files logging all MQTT events that are recorded by node server. there you can see if the event get generate a log entry that was not passed to ISY I cannot rule out that I am doing something wrong in the code (I probably am and I am no expert in MQTT - it is my first project on MQTT), but it is very difficult to debug. It seems the API suddenly stops reporting events - When I detect it I restart the connection, but it does not make sense to me that I have to keep polling the connection (that is not the idea of MQTT) and furthermore, the even could still happen between connection is lost and the next poll. Th main issue is to understand why the connection stops. The question about removing and reinstalling the nodes - I do it because of a bug that you cannot remove a mode from the polisy interface once created. The bug may have been fixed by now, but I have not seen it being important to change the code - nodes will get same names and everything should b the same - also - I hope to get to a point where there should be no need to restart the node server. Lastly - on my own local setup the connection remains up (or gets restarted) - I may miss events 0 I have not been focusing on that, but my garage door controller keeps working (to open /close) - it used to stop working after a while - naturally it does not mean there is no issues in the code - just makes it even more difficult to debug

can you send a log again

Looks to me you have more than 1 version of yolink running - can you try to power cycle the Polisy? There are quite a few other node servers generating errors as well I did notice the motion sensor sends an openReminder that I did not know exist - it is not documented what the API can send as events - I am not sure if that is the root cause - I'll see if I can find a way to handle it cleanly - maybe even find a way to use it in ISY

thanks - do you have the polyglot log as well

something is likely happening - need to take a look at it, but I am travelling without access to a debug setup so unless you can catch a log file showing what is happening it will have to wait until I return