11 minutes ago, drprm1 said:

Again, where do you see “toggle”

Is it a single node or associated with something else?

It is a separate node

Sorry, I have no node called “toggle”

Thanks for you help though

42 minutes ago, Panda88 said:

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 

 

Absolutely!

I

1 hour ago, Panda88 said:

It is a separate node

Well I don’t have it

 

 

When I implemented finger it seemed to take control of the garage sensor ns.

Not sure how

2 hours ago, drprm1 said:

When I implemented finger it seemed to take control of the garage sensor ns.

Not sure how

 

2 hours ago, drprm1 said:

I

Well I don’t have it

 

 

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

  

2 hours ago, drprm1 said:

When I implemented finger it seemed to take control of the garage sensor ns.

Not sure how

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)

8 hours ago, Panda88 said:

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)

Greatly appreciate your help with YoLink!

3 hours ago, drprm1 said:

Greatly appreciate your help with YoLink!

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 finger update does control the door  by hitting the toggle button….

Kind of a pain to have to change over to a different screen to tell if the door is open or closed

 

 

I had the garage status Yolink before getting the finger controller. (They have to change the name)

When finger was set up it meshed with the status device to show on one page.

 

 

1 hour ago, drprm1 said:

The finger update does control the door  by hitting the toggle button….

Kind of a pain to have to change over to a different screen to tell if the door is open or closed

 

 

I had the garage status Yolink before getting the finger controller. (They have to change the name)

When finger was set up it meshed with the status device to show on one page.

 

 

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.4.0 

Added support for Control (and state) in relevant nodes 

Let me know it works

Installed 4.0

Nothing different on any of my nodes.

1 hour ago, drprm1 said:

Installed 4.0

Nothing different on any of my nodes.

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?

Can’t speak for motion detectors as I have none.

The nodes show up in programming

Here are programming options for finger and a plug

 

While there is no control over the door on the node page of AC there is in UD mobile

 

2 hours ago, drprm1 said:

Can’t speak for motion detectors as I have none.

The nodes show up in programming

Here are programming options for finger and a plug

 

the changes are in the IF portion

2 hours ago, drprm1 said:

While there is no control over the door on the node page of AC there is in UD mobile

 

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 

Odd, I install ver 4.0 and looks OK for a few seconds then reverts back to ver 3.6.  I have uninstalled and reinstalled several times, same issue

A thousand pardons. This is what I should’ve shown

 

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 

29 minutes ago, jkraus said:

Odd, I install ver 4.0 and looks OK for a few seconds then reverts back to ver 3.6.  I have uninstalled and reinstalled several times, same issue

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

OK now 4.1 so that worked, but my Motion sensor is gone, but may be an issue on my side not sure, but was working before

29 minutes ago, jkraus said:

OK now 4.1 so that worked, but my Motion sensor is gone, but may be an issue on my side not sure, but was working before

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

Edited June 11, 20224 yr by Panda88

well "on-line" for a MS?  it showed up on the config portion of your NS, but yesterday it showed up on the AC but not now.  attached is log file

UDReport.txt