Panda88

Latest version is 1.0.8 after another minor bug fix for the water meter controller

New Node server for smart valve products from Netatmo. I do not have a boiler controller but if someone can give me access I can add support Requires PG3x - will not run on PG3 - Does implement the latest Oauth login

Latest version is 1.0.7 after another minor bug fix

It is always difficult to handle connection when there are multiple connections - one is from node to ISY - the other is node to YoLink API I have used ST (shown above to show connection to ISY I have used GV20 to show connection state to Yolink API I believe the leak sensor should be fixed in 1.0.7

I fixed the garage door controller to show connected (even if it was not activated) I also found that I somehow had commented out the connection change in the leak sensor (it was the one I used for main development) - it is also fixed 1.0.7 is coming soon

What variable are you referring to - Online-Offline/suspended is GV20 ST is supposed to show connection to ISY - I think I did default it to no-connected until first transaction The leak sensor (first one) seems to show GV20 = 0 - so connected - 1 is suspended due to too many calls and 2 is offline

If you can send a log - with debug I can try to see what is going on - It may be in needs to wait until first poll - Garage controller is trick as you cannot poll it

Version 1.0.6 is available Mostly a fix for off-line reporting for sensors

Working to Finish the tesla power wall node first (as I have access to one) - allowing me to test the API After this the I am on to looking at the EV server. I did do the initial changes, but testing will not be as easy as I need access to a car to test it (I no longer have my tesla) - and it requires authendication

Try https://discord.gg/FMpyub5T and https://discord.gg/P7wQuKCK - these at the 2 discord groups I know of

Release 0.1.2 is available - fixes a bug on force update on the main node

0.1.2 released and should fix this

From discord it is confirmed that local API will be available for this hub in the future - they are still working on the SW - Seems that the older hubs will not have local API - but it is me reading between the lines

The HUB3 was released - but out of stock again It will support local API but not yet Christian

Version 1.0.3 available Added support for schedules. My main use is to disable/enable schedules but one can also create schedules dynamically. Schedules will run off-line so works if internet is down Improved delay setup input - Both can be set in same operation as enabling them. (I may remove the old version as it takes extra screen space, but it will require programs to be updated. Delays also run off-line Added support for the new switch with 2 extra buttons and second programming of delays - make sure to update firmware. Buttons works like the FOB/Remote - only tested YS5708 Added support for Alerts in power sensing outlets (trigger on high power, low power etc) Added preliminary support for watermeter (there is no official API yet) Fixed few bugs relating to on-line state Moved to different MQTT method - seems to match closer what YoLink uses for counting API calls

YoLink makes a temp/humidity sensor with display - I find it handy in the bathroom. Naturally it is 2 devices if you also want motion What is the issue with doing relative changes - I believe you can transfer the device temperature/humidity to a variable (press the "play" top change input types for variable assignment)

I am working on a few other issues but I have the oauth working. The issue is it is a rewrite of the node as most apis have changed. I'll get to it but it is a significant effort unfortunately

I am not aware if there is a way to get MP3 files from the API (which is used to program from the Node Server) - it may be possible to load them in them using the YoLink app and just refer to them from the Node server - say you load MP3 into message

Hope the authentication will work for everyone - I have tested it as much as possible but it becomes difficult after a while (no clean installs) If there are issues - clear cookies in the browser and try again

I have been playing with this for a while. What I would suggest is to average - maybe make 10 measurements some time apart and then decide if a large percentage indicates water is low However, I found that the continuous on/off drains the battery quickly of the leak sensor (when close to needing to fill). What I ended up doing may be a little elaborate. I took a Yolink Siren (without siren - essentially a programmable power supply) and used that to enable the sensor of the water leak sensor (open or close the connection through the cable. Then when I need to make a measurement, I enable the sensor (power on siren) and get a reading (or multiple) from the leak sensor. After that I power the sensing (siren power supply) off again (so it will always read open / close when not in use - thus not sending status change to the HUB). It takes a transistor and a few resistors so it may not be for everyone. I run the above on a schedule so it only fills the pool at a certain time of day when needed.

After you specify TTS. There is a parameter for number of TTSses You need to restart eisy after saving the tts. It may no longer be needed but earlier releases required it

Hi A new node supporting Netatmo's latest authentication is uploaded in the beta area. Please give it a try and let me know if the authetication works NOTE - the node server only works under PG3x - PG3 does not support udi's authentication handler (which is used) You still need client_ID and client_secret but the node server will now take you to the Netatmo website where the data access is approved and then returned to the node server - suggest to install from PC. The node server supports multiple weather stations (can be selected until configuration)

The location of the UAID etc moves around with updates in the Yolink app - Difficult to keep up with this

I replied already - you need to generate UAID and secretKey in the yolink app and copy them to the configuration of the node server

Only the alarm is control I believe it should appear under status