Panda88

The current release does not support it. I am working on an update that supports it - with other internal improvements Hope it can wait until I release the new version (it is a bigger update to easier handle Yolink changing API calls)

Are you sure it is not working after restart = no ERRORs reported - the should show as individual nodes I see a leakSensor a temperature sensor and the water controller (and a hub) - They all report data There is still an issue with the leak sensor Ibelieve - Yolink updated the API so some data is reported differently (basic leak detection should still work) - I am working on an update for the node and it will get fixed with that release (it is a bigger update as I am changing the internal structure of the data - to allow easier changes when Yolink change the reported data)

all nodes are separate. hub is just a node

Can you try to include a restart in the log file - just restart with debug enabled I can see some errors, but not sure what causes them - it is like data is not reported correctly Sometimes PG3 has an issue and need to be restarted - I think it relates to both solutions uses MQTT (but just guessing)

Can you send ma a log with debug enabled - you can PM it Not sure what watervalve you have -= some need to press the set button the first time to activate - they go to deep sleep Also what do you have in the config?

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.