Panda88

Another user raised this issue - seems they have changes the naming of one of the keys - need to see if others have changes as well. I will be travelling but will try to get a fix out soon

it is mostly looking at the data returned from calls to Tesla server that may reveal something.

Can you try to enable debug in the log Hopefully it can show more - I do not have access to a car to try so hopefully the log can shed some light on this

You can only have 2 levels of nodes and some of the nodes have subnodes. This is why they are separate (similar to instead devices). I would love to have them together but I have not found a way to make it happen

It is likely an issue with permissions on your policy. It may not bad able to overwrite the files. Maybe reach out to support @ universal-devices

Can you try to rei stall from store? There is a option to install in same slot! That works for me. It is difficult for me to test as i am treated differently as the author of the node

try 0.8.99 - I hope it fixes the issue and it can be installed - what I have been doing lately is to go to node store and select nodeserver and then select install in same slot (halfway up to the right) - that seems to work every time -

99 - means unknow (when not mapped) - it was probably before the new mapping took effect I personally set the off before opening the valve - just to be 100% safe It would be interesting to know if the delay is the one delaying the next command - It should not be the case (I hope)

i'll try to release a new version tomorrow - there may be a bug in the count down delay I need to check

Let me take a look at the counters tomorrow - The couner display is running independend of the actual device (In order not to drain the battery). It is simply counting down I do not understand the battery % - there is no such info - it is a 1-5 value reported by the device.

Try 0.8.97 - Added the battery level. Also found a bug relating to large amount of messages.

I verified the battery level is not show - something happened to the valve controller in my code - it used to be there - probably a bad checkin I have never seen a message from the Yolink app when controlling devices, but I may have missed it - or you may use a different setting

The battery level should be there but let me verify later. It is only 5 level that exist

It is an error that occurs with this type of device - I am told it is a special device type (class c) - I think what is happening is the device is queried (short or long poll) and does not reply (because is it busy with something else) - I guess it is to preserve battery. It is just a guess. I could look at excluding the short poll from class c devices - but I not even sure where to figure out what type the deviceis implemented as - My guess for Yolink it is battery power devices that can get control instructions, but just a guess. I have no idea why the node server is sending an email - it cannot do that from the code (there is no email support in the code). It must be coming from somewhere else. Do you use the yolink delay function in the valve controller (I do that in case the internet goes down while valve is on - the delay timer runs on the device so it will shut off evenif there is an outage of the internet / power outage.

Try 0.8.90 - should fix the issue

I think the ISY restart is only needed when you modify the message text - new fields will be added on the fly. Things may have improved since I worked on it

Yes - As @Bumbershoot mentioned above - at the bottom of the configuration page of the node server (PG3 page) there are TTSn and NBR_TTS (TTS = Text To Speech) fields. You can enter the messages there. I believe if you increase NBR_TTS the TTSn fields should get generated automatically (you may need to restart the node - I cannot remember how it was handled) but you can also add them manually. Note, you need to restart the node server, and more importantly you need to reboot the ISY after changing the message text. It is an issue with the ISY - it only read the configurations at boot so if you change the TTS field it does not update until after a reboot. - I believe new fields works, but existing fields being changed does not work The payment is a question for @bpwwer I believe On a different note - I have had issues running 2 node servers with the same UAID - I have not tried it recently so it may work now, but I had issues in the past and stopped doing it -

I think I released the beta using the same node so it should be possible to install it and replace the existing one (and then do the same again with the released one) - that should prevent having to redo all the AC work Let me know if it is not the case and I can try to do the release again into the beta store I am travelling this week, so no easy access to my system so a new release would have to be next week

Thanks Bob I think it is working now - I can update from configuration now - but it will not go back to YoLink App

This is what I expect - I cannot change the name in the phone app using the API so I wanted the phone app to be the main source I will look at making it possible to change names from PG3 - but it will not reflect back t the phone app.

The node takes the name from the YoLink app - The name does not change right away when you change from the YoLink App - Probably not synchronized at their servers I can try PG3x - I am doing development on Polisy (PG3) but I do have an eISY to try it on I do not believe the code updates the name, if changed in the PG3 interface - Maybe I should look at that

I updates node info - it is a minor change addressing when you have a very large amount of devices installed - I cannot test if it works, as I do not have enough devices to test it

it would be guessing - but is looks like a calculated 0 (not yielding exact zero)

Correct - it is an attempt to limit simultaneous quering when you have a lot of devices - The YoLink MQTT disconnects if you querry too often - no other changes

I have not had this issue - it may be an issue with your specific unit Glad it is working again