I installed the Yolink plugin and configured the UAID and secret key. I currently have a vibration sensor and a weatherproof temperature sensor (set up for testing). The nodes came up fine, and the status display for each device appears to be correct. But I'm trying programs and things aren't working as I would have thought. I created two test programs, one for each device.

1- I created a test program for the vibration sensor (configured as a DON/DOF device), first to detect a control event:

yolink vibration test - [ID 00BF][Parent 0001]

If

'Vibration Sensor' is switched Vibration Detected

Or $s_yolink_trigger > 0

Then

$s_yolink_vibration += 1

The "Or s_yolink_trigger > 0" statement is just to test that the program is running ok and that the variable display in admin console is updating in realtime. The sensor detects vibration ok (LED blinks), and triggers a Alexa message that I set up in the Alexa app, but the s_yolink_vibration variable doesn't increment. As if the plugin wasn't seeing it. Even if I wait 10 minutes or more for the time to go beyond the "last poll time" in the Yolink Setup node (shows as online and ready).

I then modified the program to look for a status change instead.

yolink vibration test - [ID 00BF][Parent 0001]

If

'Vibration Sensor' Vibration State is No Vibration

Or $s_yolink_trigger > 0

Then

$s_yolink_vibration += 1

The first quirk is that no matter if I choose "Vibration" or "No Vibration" for the Vibration State status and click on update, the program line always shows "No Vibration" as above. There are also two "Vibration State" statuses to choose from in the list, but both only show "No Vibration" when you update the line. Ok, so I tried making it "if is not No Vibration" a double negative... But no matter what I try, the variable never increments.

2- I thought I'd then try the temperature sensor. Created the following test program:

yolink temperature test - [ID 00C0][Parent 0001]

If

'Temperature Sensor' Sensor Temperature > Updating (may take up to 1 hour)

Or $s_yolink_trigger > 0

Then

$s_yolink_hightemp += 1

The first quirk is that in the program editor, what I actually entered is if the temperature is > 26, but the program always shows as "Sensor Temperature > Updating (may take up to 1 hour)". I can't get it to display the temperature value I programmed, though it seems to save it correctly because if I go back to the program editor, the value I entered is still there in the bottom part of the screen. So I have no idea what IoX is seeing. But the program doesn't detect the temperature going over 26 C, even though I do see it update correctly if I view the temperature sensor device node directly.

So the device nodes seem to be working, but not when referenced in programs.

Another quirk is if I edit the node names and reboot the controller, the default names come back.

I'm testing this with IoX 6.0.0

Edited 18 hours ago18 hr by Guy Lavoie

Can you enable debug in the log and do a few actions and PM me the log - I can take a look

It does appear something has changed in 6.0 with how AC works with temperatures - I am still battling this - I do see the same issue

I think it is related to having multiple definitions for editors - I have one for unknown and one for actual data -

I believe there are some tickets already filed

In general, I recommend using the alarms in yolink sensors, but getting the status should work as well

Ok, I'll try and do that either later this evening, or tomorrow.

6.0.0 does seem to have affected some plugins, as we've seen on the forum.