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.

[Ross]

Thank you all for your help.

@Panda88 I installed YoLink in a new slot, but there is no change.  It does not appear in Status and appears in Control.

I am using an ISY and a Polisy for the Plugins.  ISY firmware and UI are both 5.3.4.  The Polisy version and Frontend version is 3.1.13.

@Geddy I've restarted the Plugin and restarted the AC several times.  Browsing to your link replacing EISY with Polisy and also using my internal IP address both returned "This site can't be reached".

I've had trouble updating my java on my computer - it gives me an error.  I will look into it further this weekend.

@bpwwer I've clicked the Load Profile, waited a minute to several minutes, and then restarted AC a few times.  No luck each time, though.

Ross

[Panda88]

It may be related to you setup with separate ISY - any particular reason not running it internally on the Polisy?

I know this node has some "optimization" on how the NLS file is made and I wonder if that could cause this - I can try to change it to not use common NLS settings - I know it affects the REST interface in some cases

[Geddy]

2 hours ago, Ross said:

I am using an ISY and a Polisy for the Plugins.  ISY firmware and UI are both 5.3.4.  The Polisy version and Frontend version is 3.1.13.

Seems like you’re trying to run current plugin on an outdated system. I don’t think PG3x allows or is setup to have an external ISY (ISY994). The current PG3 version is 3.3.18 (at leased based on my system currently). I suspect you haven’t updated the Polisy. I suspect your setup is blocking some advanced settings and you are seeing that with unexpected results in information being shared back to an old ISY994. 

[bpwwer]

The PG3 version shouldn't be the cause.  However, the ISY994 is EOL'd and is not getting the firmware updates that Polisy/IoX eisy/IoX are getting and there have been changes in the profile file support in the new firmware that could be the cause.

 

As you can see, we've been throwing out random suggestions on things to try but we don't really have enough information to determine what the issue is.  Whenever there is a problem with a plug-in, you'll get the best support if you follow these steps when posting about the issue:

1. Change the plug-in's log level to debug
2. Restart the plug-in
3. Do whatever makes the issue apparent
4. Download the plug-in's log package
5. PM the log package to the plug-in's author (or attach it to your post)
6. Include the ISY/IoX firmware version and PG3 version information

If you end up submitting a ticket to UDI, attaching the log package to that is also very helpful.

[Panda88]

I can provide a non-production store release with traditional config file to see if that fixes your issue

Let me know and I can prepare it - if OK I'll make a full release of the node 

[Ross]

@Panda88 I've been running the ISY and the nodeservers on the Polisy for a long time without any YoLink Issues.  This only broke because last week I thought about how well the system had been running for so long...

@bpwwer I did #1 and 2.  Not sure what to do for #3, but I restarted the AC and YoLink still doesn't show up if I want to use the status in a program.  I then downloaded and attached the log package.  The temperatures update on the Main tab, but I can't use YoLink in a program.  I also noticed that any program using YoLink (i.e., update a variable if the temperature changes) doesn't work.

ISY firmware and UI are both 5.3.4.  The Polisy version and Frontend version is 3.1.13.

@Panda88 I don't necessarily want a special program for me.  Your plugin/nodeserver has worked great for a long time and then all of a sudden stopped.

If you can't glean anything from the log, then I'll submit a ticket.  I've been waiting for an "event" to upgrade to EISY.  Perhaps this is what I needed to do so.  I just hope the problem doesn't transfer to the EISY.

Thank you again,

Ross

YoLink_5-7-2025_85038-PM.zip

[Panda88]

I am not expecting a special version for you - just for you to test if it helps before I would release it as a new version (there is no need to do a new version if it does not help)

Nothing obvious in the log (from my side)

[Ross]

@Panda88 I appreciate that - but I messed myself up loading 2 different Kasa plugins and I still haven't been able to get it to work.  I don't want to mess up the YoLinks I have working (and I know I would!).

I've submitted a ticket and I'll report back.