Panda88

Hi A new and updated version of the server is live now. Release note: 0.9.63 - Fixed bug with system going offline not showing. Added Smoke detector Added Siren (usable as a controllable 12V supply) Updated sensors to allow config of DON/DOF behavior. Changed use model for delays in switches, outlets (incl multi) and manipulators. Now allows programing both ON and OFF delay in 1 operation (using new drop down) - the delay settings now prepare the delay - not executing it. The main reason for this is to allow a programmed sequence of both on and off (or vice versa) - e.g. to power cycle the internet connection - or ensure a valve turns off even if internet goes down in-between 2 programming operations. (Note, yolink API changed behavior of delay so the delay will now be reset (removed) if a new command if issued after the programming of a delay)

Errors occur in the MQTT library I am using - Probably connection problem - not sure I can do much there

Sorry - it is not possible to control these parameters from the provided API. There must be a superset API, but it is not publicly available

I think you can create a scene to do this (but this is not the node server) - in the node server you would need a simple program, which can allow more flexibility

It is possible I do not update the overall node server - I'll take a look once I return from vacation. I think it is supposed to show it node server is running or not - but I does not seem to match what you describe.

The node server should restart if it detects a fault on the connection to the yolink MQTT server. So you have a debug log?

So you have a log. It works for me (disconnecting the polisy)

Can you try a new install - I am not able to update the node store, but if you install now is should pick the latest code. There are changes in the structure from tesla so there may be other changes needed in the code, but I cannot test as I do not have a car

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 -