Panda88

Yes - this is expected

There is no local API yet - they are working on something but not released yet - will likely need a new version of HUB to do it

yes - it detect the motion sensor as off line when installing and then it removes it - It is probably too aggressive - I should just keep it an let it show off-line - I have to assume that devices registered are supposed to exits I'll look at making that change later

I need the log from the node server - go to polisy and go to node server and then download log The on-line checks if the cloud api has a connection/communication with the motion sensor It is possible I made a mistake but mine show up???

If a device is not on line when restarted it is removed - Maybe that is too aggressive - let me know. Send me an log and I can take a look

I forgot to change the version number in the code - did a 0.4.1 - try that

0 means closed - there is an issue that I have been struggling to find on the udiMobile - is somehow does not pick up the number to text conversion

Is this a yolink device ? The door state is an input (opened or closed) - to control the door need to use the finger - issue a toggle to the finger

the changes are in the IF portion

Changes should be int he programming are - if you choose control in the conditional statement the nodes that can be controlled should show up now - e.g. a motion sensor should show up allowing control when there is motion - vs. a state change as before - In my mind there is little difference as the node server is MQTT based so the state change happens at the same time but it does not hurt to support both I guess . Or are you saying you do not see the nodes under control?

Dropped 0.4.0 Added support for Control (and state) in relevant nodes Let me know it works

I think they have an API with more capability that what is offered externally - lot of settings in the APP is not available in the external API. It would have been great to be able to combine the two but unfortunately I do not know how

Dropped 0.3.6 - should support Finger - if you run into issues set debug level to debug and send me the log Hopefully it works, but I have no way to test

The API keeps the two separate - I need to create a finger node for it to work - the yolink app may link them for direct control (no need to go through cloud)

Yes - I need to create a node for the finger controller - i'll see if I can add it tomorrow - and then you can give it a try - I do not have one, so I cannot test it here

It is a separate node

My understanding is the program will execute on a change of state - meaning it will only run once the state change I'll see if I can figure out how to make it control - it does make sense but I am not 100% how to make it a control vs state

I need to implement finger - it is not supported yet - I only use the other garage controller - if you are willing to help test it I can add the code for finger

It is there already as garage controller - I am using it - it is called toggle - you cannot specify open/close - only toggle Unfortunately it is not easy to combine in same node, as the GarageDoorSensor is a generic door sensor in the API - I do not know if it is an open/closed door or a garage door when I get the info from the cloud.

On the motion sensor - How would you use a control? - I can only see it react to a motion event You cannot really query a motion event - it does not check the sensor - only checks what is cached in the cloud

This is what mine looks like - Do you use the "finger" - I have not looked at that as I do not have one

It is there already as garage controller - I am using it - it is called toggle - you cannot specify open/close - only toggle Unfortunately it is not easy to combine in same node, as the GarageDoorSensor is a generic door sensor in the API - I do not know if it is an open/closed door or a garage door when I get the info from the cloud.

Dropped minor release to add setting for temperature unit in Config (TEMP_UNIT) - K/F/C Other minor bug fixes

Not currently, but it should be easy to add - I'll take a look at it

Tesla changed the cloud authentication method so I took the chance to update the code of the Node server - it is now called TeslaPW