Plugin (Node) Not Available for a Program

[Ross]

I'm not sure this is a YoLink issue as much as it's either a Plugin issue or a "me" issue...

I have several YoLink temperature sensors which I use in programs to do something or notify me when a temperature condition is reached.

Now, when I create a new program, I click Condition and select Status, but the YoLinks do not show up as a selection in the next dropdown box.

If I click Control, they do show up, but that's not helpful as I need the status (temperature), not whether it's on or off.

The strange thing is that my current programs using YoLinks continue to work.  So, I copied a working program and tried to edit it, but the same thing happens - the YoLink in that program doesn't appear in the dropdown.

The YoLinks all appear in the Main tab under Nodes and they do reflect current conditions.

I have reinstalled the plugin into the same slot with no effect.

Below are some screenshots.

Thank you for any and all assistance,

Ross

Main tab

YoLinks should appear below WeatherLink when I select Status, but don't:

YoLinks do appear if I select Control (which is of no use to me, though)

[maxnorth]

This happened to me with the Tasmota node server at one point, and the developer fixed the node server.

[Panda88]

I do not have this issues in my setup - both status and control work for temp sensors 

Can you try to install in a new slot - just do a backup before you try it

Note, you can use condition - it is the internal trigger (high and low warnings) level set in the yolink app - and it is actually preferred as it updates quicker than status, but you can only use one of the two if you cannot get the condition I guess  

Are you fully updated on AC and PG3x?

[Geddy]

@Ross not seeing this on my side. Meaning I DO have status options to select from.

If you reinstalled the plugin have you closed and relaunched admin console? Even though you see the nodes in the main portion sometimes reloading admin console might bring everything current again. Random would be to clear java cache and get a new start.jnlp from UD and load IoX Launcher fresh on the system. 

What IoX version are you running? Browse to this site when local to your device: https://eisy.local:8443/WEB/sysconfig.txt  (if you have polisy replace eisy with polisy or use your device internal IP address)

Look for IoX/ISY version: (Recent version showing)

Quote

************ IoX ************
isy-5.9.1_18
Name           : isy
Version        : 5.9.1_18
Installed on   : 

 

[bpwwer]

This type of issue tends to be related to the node definition files for the plug-in.  

When the plug-in starts, it sends the node definition files to the IoX.  There's no retries on this so if the IoX rejects it or something else disrupts that send, the files on the IoX may be missing or incomplete.  The plug-in details page has a button "Load Profile" that when pressed, will resend the files to IoX.

The admin console reads those files from IoX when it starts (and only when it starts).  So if the files are sent to IoX while the AC is running, it won't see the updates/new files.  You need to restart the AC for it to re-read the files.

Lastly, if there's been an update to the plug-in and the node definition files were changed, that could have introduced an error into the files that cause both IoX and the AC to fail while parsing them. 

@Geddy suggestion to restart the AC is the first step.  I'd also suggest that you use the "Load Profile" button first, give it a minute and then restart the AC.