Panda88

It is correct - it is a new node with a new code base so not easy to move back into the original one Furthermore, Michel and team have been helping by making and running a server to allow commands to be transferred to the car. If important you could try to reach out to Michel and see if he will allow a transfer - I would be fine with it, but since Michel and team are running a server now to allow commands, I think it is fair they get a little extra income to compensate for this (It is not to make money I do this - it is more for fun and to keep my brain going)

This is correct - it needs debug enabled to see posting from not registered devices

If you go to the log in the node interface. There you can set level to debug. Once that is set I would imagine you can lift the sensor out of the water or wait 4 hours, The water sensor should report an update every 4 hours or so automatically and it should get logged. Then download (save) the log from the log area - it will save a file you can PM me My guess is the history you mention is alarm history You can see the definition for what can be programmed at WaterDepthSensor | YoSmart Doc From the document it seems you can only get alarms when water is higher(or lower) than the alarm level - not a reading of the actual water level - but it may be in the reported data - just not shown in documentation (it is not the first time this happens)

If you can provide me with a log file where the water dept sensor posts data and ideally also an alarm (e.g lift it out of the water) , I can see if I can add it what other devices are not supported - I am willing to help to try to add them, but I need log files as the documentation from Yolink is minimal you can PM me the log file Also - what is the unit/type of theaparm setting - I can see it is a value from 0-1000 but not sure what it represents

Not sure what that means - let me try to rebuild and issue a new version. Mine installs fine, but I have the new library that I added already - Did you try to force an update from the store? Can you PM me the log Package file

release 0.1.37 Fixed some labeling issues Changed AC to display time since last update (minutes) even if car is offline Few other bug fixes

The program is executing to the end In the tracelog I see ST changing to 1 and 5 min later back to 0 - it did work then I need to look once it does not work

The program does complete (but light turned off this time) - It may be a link issue - maybe my card has an issue

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