Panda88

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

the code for wake does a loop until the API responds (but you will not see this from the ISY. I could possibly make the status or climate node return a ON/OFF (a control for the node in the ISY) so it will change state when car goes from sleep to awake) but it has not been done yet - let me think about it - I do not have a car my self to test on and I only know people say the response is fairly fast these days - 30 sec or less worst case Also - the long poll wakes the car if a sleep so this should be a worst case scenario - you could use heart beat (short poll) at half the long poll duration and then program after a delay on either On or Off for the heart beat - I believe the PG poll is synchronized initially so they should happen aligned

It looks like the token does not work correctly - it could be the API has locked you out (go to www.tesla.com and try to log in) - if that is ok try to generate another refresh token. If not recreate your credentials You can also try to erase the REFRESH_TOKEN entry under config - both key and token and then restart node server - it should auto generate the entry again. I think I did change the code to handle a car with no name, but we are not even getting that far here.

Are you running on stand alone ISY or IoP (ISY on Polisy) - my guess it is what is happening is the ISY is slower than my setup so it is not ready when the code starts querying the nodes Can I get you to try again with login set to debug. - it is info now - but you previous screen shot showed debug I made some changes to ensure the node is ready before querying data from it - I hope it works as I cannot test as I am travelling (It is a minor change - no other functionality)

Looks like the return structure from Tesla has changed a little - need to look through the changes and make appropriate modifications

Can you try to erase the REFRESH_TOKEN key save (not just the value but the key)- and then restart? It seems to old token is somehow stuck in polyglots database

looks like something went wrong during installation - Can you try to remove it (fully) and install again - it is like it is not registered correctly in the node store

try to start again but get the log from upper right corner - it looks like the node server does not start at all

ny chance you can provide a full log - the error happens earlier - but it does look like the token did not refresh corectly Tesla does change their API once in a while and as there is no official API it takes a little while to get it updated It can also happen they log you out if you poll too often so try to log in at website to see if that works I am travelling now so there will be some delay on support

t looks like you found the place to put it (at the bottom - REFRESH_TOKEN) - Is the one shown one you entered - if not clear the filed and replace it with your token - make sure that there is not a blank space at the end of the token - I had that issue in the past. If it does not work, can you post a log file there - I need to know what it is wrong. Also it the version looks wrong - but it could be related to the node not starting

I believe a full power cycle should do it -unless you had a very early version I think you may have the latest version already