Panda88

Hi A new release of the Yolink node server (ver 1.8.45). There is a lot of changes below the surface to handle the Yolink API better. Node should be faster and take less resources. Added quite a few devices (Most of the newly released devices and Thermostat2) and updated a few sensor nodes (The Yolink API was updated - THsensor and LeakSensor ) . Note, the new LeakControllers behave a little different than other devices - they go to sleep. Given this one should use the YoLink specified limits to trigger events. Also, they cannot sleep when added. YoLink schedules are now in separate child nodes. As this is a major update, so devices may not work - I have tested the ones I own, but there are derivatives of the devices and a few I do not own, so please help test and let me know if something is not work correctly Note, there is a minor issue with the Dimmer - there is an API problem YoLink is working to fix - I hope once they release the fix the issue is gone, but I have not received the fix yet (probably low priority as it only related to controlling some attributes) - nothing critical

Hi I added a node (KiddeSmokeDet) supporting Kidde Smart Smoke/CO detectors. It is a simple node that pulls data from the Kidde cloud showing if alarms are detected - it also shows CO level and smoke levels It is a main node with child nodes for each Alarm detected It offers simple control to test, Identify and hush the alarm Note, the Kidde API does not seem to poll the alarm when called - just reports the latest data send by the alarm - it may not make sense to poll that often ShortPoll is a heartBeat and LongPoll obtains latest data from the Alarms Note, it is only tested with the DETECT type Smart alarm

Can you send a log. It is possible they have change the api again. Also did you verify the webhook test passes

I am working on a release that supports the thermostat device - we only tester version 2 but API is the same so likely yes

There are some devices in the log that show offline (code 000201) - often you just need to press the set button There is a bug in the THsensor - I am working on a new release that should fix this - it is a race condition during start up I hope to have a release soon - if not I'll move the fix back an release a fix Is it all devices that show the year old data or only a few ones?

Can you send me a log with debug enabled

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 -