Panda88

Yes - AC works fine It is more that 1 device exhibiting this issue I am 5.8.4 and latest UI version

It is a Zooz Zen77 - 3 LED lights It is not the only device having issues - Other Zwave devices have issues as well Also, I can turn it on and off using the mobile App without issues

It comes on, but does not turn off again

Here are the 2 programe - the second is disabled Even if I select run Then - on the second it does not work - it turns on but not off after 5 min BTW - I faid it hard to believe that if conditions change after a program is triggered it will stop execution. E.g. say I have a program to run at 10.00pm - One second later it is false so all execution must happen in 1 sec s DS Hallway Light Copy - [ID 00AB][Parent 000D] If From Sunset - 15 minutes To Sunrise (next day) And 'Alarm Panel / Motion DS hallway' is switched Opened Then Run Program 's DS Hallway Test' (Then Path) Else - No Actions - (To add one, press 'Action') s DS Hallway Test - [ID 00AA][Parent 000D] If Then Set 'Z-wave / DS Hallway 9 / ZW 009 DSHW Multilevel Switch' On Wait 5 minutes Set 'Z-wave / DS Hallway 9 / ZW 009 DSHW Multilevel Switch' Off Else - No Actions - (To add one, press 'Action')

I tried 2 programs - result is the same

I have the board, but I did not mitigate the Zmatter Z-wave

Sure, I can give it a try - but it worked before with a zigbee device I used (replaced it with a Zwave)

Here is an example - on executes - off does not. I realize I can add an off delay to fix it, but there are multiple other examples. It is a Zooz ZE77 switch In general is it not stable - I have other programs that just turn on, but it is not reliable with Zigbee devices (other are fine) Is there a benefit to update to Zmatter - I have not do that yet

The same program works with a zigbee device. My understanding is once the program has triggered it will run to the end even if conditions change Thanks

I am experiencing unstable performance when execution program controlling zwave devices. I can have a program that turns on the device waits 5 min and then turns it off. When execution the device will turn on but not turn back off after 5min. I have not upgraded to Zmatter - would that help? I can control the device reliable from AC so it does not seems like a connection / range issue Any deas?

I have released a new TeslaEV2 node server. It uses the official API (with some restrictions imposed by the API) It uses better security and does not require getting the token It only operates on PG3x There are likely still bugs (especially around sending commands) as I do not have a car locally to test it on The first thing to do is to install a virtual key on the car (allowing commands to be sent) - This is currently only supported for NA EVs On your mobile device open https://tesla.com/_ak/my.isy.io (in browser). It should open the tesla App and you can approve the installation - if the car is too old it may just say it is not needed Next start the node and configure REGION (NA, EU, CN), DIST_UNIT (Km, Miles), TEMP_UNIT (F/C) and LOCATION_EN (True/False) Save and restart - Click authenticate in upper right corner. You should be taken to a Tesla Login page, go through login procedure and approve the selection at the end After this the node should continue and install You will see a main node and separate nodes for each EV registered to your account The EV node has a status page with simple commands and 2 sub-nodes for climate control and charging control Hopefully this will finally end the long wait to get this going again - It has not been easy and a lot of help from Michel and team has been required

It may take a little time to propagate If you want to test the mobile App - I would reinstall in new slot If just using AC - I would just upgrade - it should work - it is difficult for me to test as I do not have an EV to test

Released a new beta 0.1.33 - give it a try - I think it is close Data will remain when EV is asleep or offline (time since last update and state is updated) Fixed some bugs Will try 2 times for commands if first fails (seems to be issue with old cars) There may be an issue with Mobile App - some results shows numbers than text - may be fixed but cannot test it easily - may need to install in new node address

It was a bug in reporting - control updated the state automatically - It is only when something else controls the outlet this happens (i.e. someone presses the local button)

Found a bug - try 1.2.5 just released

@someguy Can you send me a debug log file on the honk horn command that takes 2 tries - I can hopefully fix it to only need 1

It is similar - the car will push the data to the server (either at Tesla or at UD) and the ISY will query the server - It is what is happening now, but there are limits on number of calls to retrieve data (to limit bandwidth at Tesla) - the external server would not have these limitation Currently the poll for more data is API call limited, so fewer updates will happen I think commands count would still be limited, but I do not know for sure. Tesla offers a prototype server to install, but I have not looked at it

Currently - short poll updates data if car is on-line, long poll tried to wake the car and then fetch data, so users can play with these numbers. Tesla does offer an option to have an external server running to collect data and users would then poll this - data would automatically upload from the car once online. However, this will require the UI team to implement and maintain this server - probably depends on number of requests for this - it should be the most energy efficient solution as data only uploads when car is on line Naturally one would be able to wake the car to get it to push data - I assume this is silimar to the tesla approach. Another benefit is there would be no limits on API calls

@someguy Do the commands work in your setup - I think you have an older car that does not support virtual keys. Please let me know as I expected to have to have special code for this case, but maybe Tesla handles this on their side How would you expect the automation to work when car is offline - I assume there will be no triggers as data does not change. Time since last update should show how old the data is, but I still do not see the use of old data in context of automation Again, I am open to change the behavior if people request it

It is default operation at this point when car is offline (not asleep). I could change it to show last data but in my mind that is not useful either. I would wake the car if it shows offline I am open to change it asi am not sure how the border is being used

Is the car online?

i'll try to find where it is in the documentation - Can you send me a log file when you say try to honk horm - maybe it will say something about how to identify if car can support virtual key or not and what to do in that case

Gary From log 2024-10-19 22:32:22.008 Command udi_interface ERROR TeslaOauth:_callApi: Call POST https://my.isy.io/api/tesla/api/1/vehicles/5YJSA1E53PF518311/command/honk_horn failed: 500 Server Error: Internal Server Error for url: https://my.isy.io/api/tesla/api/1/vehicles/5YJSA1E53PF518311/command/honk_horn 2024-10-19 22:32:22.008 Command udi_interface DEBUG TeslaEVOauth:teslaEV_HonkHorn: teslaEV_HonkHorn unknown - {"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_description":""} Looks like the virtual key registration did not work - did you try to open site https://tesla.com/_ak/my.isy.io on your mobile device

Hopefully this help on basic operation. We can look at commands next

Did you register the Virtual key. No commands can be sent without if you have a recent car