@Panda88 ,I noticed last night that YolinkLocal was not triggering programs. I went to UDM, Settings>Plugins and selected YolinkLocal and the little wheel kept spinning, never would stop. I had forgotten about this, it has been this way since I think non-production days. If I back out and select another plugin it wont open either. So I closed it down. Opened it back up and selected a few different plugins and they all would open properly. I once again selected YolinkLocal and it would not open.

I am not sure if this is just a me thing or it just hasn't been noticed and reported before.

Also, as of the last update, yesterday, when I resync UDM it still does complain that slot 15 (YolinkLocal for me) is not setting or hasnt set ST name. or something like that. So I don't know if the two are linked or not.

Thanks!

-Tim

Out of curiosity, I went to UDMobile and settings and plugins. For what it is worth, the yolink plugin opens with no spinning wheel.

30 minutes ago, oberkc said:

Out of curiosity, I went to UDMobile and settings and plugins. For what it is worth, the yolink plugin opens with no spinning wheel.

Interesting! Thank you for checking @oberkc. This is the only plugin out of like 20 that does this. It started with the first or second non-production YolinkLocal. I guess this indicates something on my end, but what? Weird.

Question, when you resync UDM do you get the message to let the dev know about ST name for the nodeserver? That also started with one of the non-production versions as well.

One last detail, if I go to settings plugins and select this plugin, wait 20 seconds or so then close the app, reopen the app and go to settings>plugins I get an error message of:

"Could not get pg3 auth PG3 (Plugin Software) is not online. Then at the end it says :Developer Tip: This issue may be caused by PG3's Portal Connection mismatch. 500"

I have not released the fix for this yet - fighting another issue - and I combined the fix with this thinking it would be an easy fix :-( - not easy to separate it now but I am getting closer to fixing it

31 minutes ago, TJF1960 said:

Question, when you resync UDM do you get the message to let the dev know about ST name for the nodeserver? That also started with one of the non-production versions as well.

I get no such message

11 minutes ago, oberkc said:

I get no such message

Lucky man you are then! Thank you for taking the time to respond, I appreciate it.

Its really not a big deal, unless for some reason I am away and need to restart the plugin. But there are worst things in life.

Thanks @Panda88 for all of your laboring and hard work. I appreciate it very much.

-Tim

I pushed a simple fix - I believe for the ST and SME error is UDM - If you reinstall it should pick it up - Note, it is not a new version - just typos in a text file

4 hours ago, Panda88 said:

I pushed a simple fix - I believe for the ST and SME error is UDM - If you reinstall it should pick it up - Note, it is not a new version - just typos in a text file

I reinstalled about an hour ago, did a hard reboot to eisy. No change. It must be UDM them.

Thanks,

-Tim

@TJF1960 I was a little premature in my proclamation that I do not get any errors. Just now I synchronized and received two errors:

1. could not match ST paramName: AME

2. could not match ST paramName: ST

I see nothing about "let the dev know" or any reference to any node server. I don't know if this is new or whether I just missed it before.

2 hours ago, oberkc said:

@TJF1960 I was a little premature in my proclamation that I do not get any errors. Just now I synchronized and received two errors:

1. could not match ST paramName: AME

2. could not match ST paramName: ST

I see nothing about "let the dev know" or any reference to any node server. I don't know if this is new or whether I just missed it before.

These are benign errors for the user, but useful for Node Server developers.

The NLS file has a "ST" definition which could not be parsed. Appears the "NAME" is missing or is something other than "NAME"
https://wiki.universal-devices.com/Polisy_Developers:ISY:API:NLS:Language_Support

ST-<nodedef.nls>-<st.id>-NAME
GEN-<nodedef.nls>-<st.id>-NAME
ST-<st.id>-NAME
e.g.
    ST-ST-NAME = Lamp
    ST-MYDRAPES-ST-NAME = Drapes

      

2 hours ago, Javi said:

These are benign errors for the user, but useful for Node Server developers.

The NLS file has a "ST" definition which could not be parsed. Appears the "NAME" is missing or is something other than "NAME"
https://wiki.universal-devices.com/Polisy_Developers:ISY:API:NLS:Language_Support

ST-<nodedef.nls>-<st.id>-NAME
GEN-<nodedef.nls>-<st.id>-NAME
ST-<st.id>-NAME
e.g.
    ST-ST-NAME = Lamp
    ST-MYDRAPES-ST-NAME = Drapes

      

@Javi, could this error also cause the inability to open Settings>Plugins>Yolinklocal?

52 minutes ago, TJF1960 said:

@Javi, could this error also cause the inability to open Settings>Plugins>Yolinklocal?

No.
There is a content length limit for remote connections to Plugins, which may be the cause. If you have setup local connections in UDM, try when local, may require swiping app from recents to clear cache.