Panda88

Do you have a log - Maybe it does not report it (or reports it differently) - I do have one but not installed it yet

Thanks - it is actually a missing update - hopefully 1.6.11 fixes it (just released)

Currently no but i can work with you too get it added if you can provide logs once I get the basic code added I never hear agrees to one so no support so far

Just updated to 0.6.6. There was an update to the underlying API (likely a bugfix) - so a new version is needed to force the latest API use

Just confirming - the power is reported when an alert is generated (no energy though)

Just released 0.6.5 It fixes the issue on my side You may need to refresh the node store for it to show up - it takes a while to propagate on its own

As it was said, they are the same. If you write new programs I would use the one WITHOUT legacy as some time in the future if we run of variables (there are limited variables we can use in a node server) I would sacrifice the legacy for new functionality - Note, this is not very likely to happen (there are still a lot available), but just in case

Triggering is fast in my exeriense - Note, you can trigger on both on and off and the node includes a time stamp in sec, so you can calculate the time it was on and off. I believe the trigger (message generated when a trigger occurs) will include a current power/energy draw report (causing the trigger) - I need to check, but the other devices do this

Just checked - Amazon/Blink has changed the authentication method again - need to figure out how it is done now Don't restart the node until a fix is in place

also note there is a new indoor high power switch that if i remember correct also supports power. i have it but have checked it yet.

currently it is supported. i could add a 24 hour or 1 hour average if that makes sense it reports current power and energy

Can you send (PM) me the full log including the PG3 long and install log?

I often find you need to run the upgrade more than once to everything installed correctly Did you reintall all nodes after the upgrade ? - I wonder if a library is missing - base_url is part of the library

I am working on it - - the motorized valves should be there already 5018 works, and I am working on 5009 and 5029 I am in the process of re-factoring the node, but I have them in the code - probably a few more weeks (Yolink is not consistent how these devices report data, so I have to refactor my code) Note, some of these devices (09,29) are a little difficult to handle, as they go to sleep without activity and then you cannot control them while they sleep (you need to press set, or there has to be activity ) - YoLink is working on a new FW that allow the app (API) to turn off the valve manually. Note, currently the devices need to be awake when you add them - I am working to improve this (part of the refactoring) Anyway, support will get there -

They are two different variables representing the same result so they are programmatically equivalent. I had to do this because people requested UDmobile to show motion in your case and UDmobile shows the ST variable (which for most nodes originally presented online) To make existing program run, I had to maintain the original variable (now named legacy) and then assign the same value to ST Online moved to a new variable in this case