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.

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

I believe I updated both - 1.6.10 - if it does not show do a store refresh

Ok - I think we found the issue - minor bug in AC (and partially my fault) - Issue occurred when I moved key parameter to ST variable (to show status in UDmobile). I left the original value variable with the same name(to ensure existing programs would still work, but AC cannot handle two variable with same name in the same node - I updated the variable names so ST (shows in UDmobile) gets the original name, and I appended a (legacy) to the name of the original variable. It should not affect existing programs as it updates automatically, but I would suggest moving to the ST parameter (without legacy) when creating/editing/modifying programs Let me know if the issue is fixed in 1.6.10 - refresh store if it does not show yet

it is only when you create a program - correct?

Sure. Hopefully they can find something

Released 0.6.4 Uses the latest blinkpy (0.24.1) so features should be up to date It uses the new login credentials method. It is similar to old version, but it is no longer possible to save the 2FA code, so one will need to add new 2FA code every time node is started. I have tested for 24 hours and it seems token renews correctly Added a time stamp to cameras showing time for the latest poll of data Let me know if any issues occur Note, I have still not figured out how to automatically create the different networks automatically - one need to create them manually by copying the network names to configuration