Panda88

It is likely and issue for Bob - I sent him a message already

Correct, but it is PG3 handling the update - There have been some changes lately but it is very difficult to test as developer as you have different privileges

did you check the main polisy log (not the individual node log) - to see if there is any info? I have no idea what is happening - it seems to be PG3 - related - maybe bob can help

try to go to store - and install again - click the reinstall here button That way you do not need to reinstall

Did you try to click download log? I find the gui sometmes do not show the log, but it is there if you download it Did you click reinstall here? button when upgrading?

does the main log show something - Maybe try to power cycle your Polisy/eisy What procedure did you use - I have been using replace existing (click half way up when installing the updated node

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.