@TJF1960 FYI.. when I go to UDM and do a Sync.. the plugin throws an error for each node. So with 2 plug ins running, I get 72 errors..

See below for example of first page.

I ran sync yesterday after updating all four plugins I have running on each eISY I have and didn't get one error. 

I am at work now but ran sync again, still no errors. 

I'm not saying there isn't anything wrong with the plugin, but I can't reproduce it here.

Maybe @Javi can help?

could have it have anything to do with the Json line?  mine is blank.

No, I don't think so. 1 of mine in both eISY's also do not have a Json file. 

I just resync'ed again, no errors. 

Do all of your temp data jive with the admin console or the webcontrol console?

Is the heartbeat switching between -1 and 1 every shortPoll?

Does the time/date update also every shortPoll?

I quess it would be easier to have asked, is the plugin working fine in UDM, just with the errors?

See answers in CAPS

Do all of your temp data jive with the admin console or the webcontrol console? YES

Is the heartbeat switching between -1 and 1 every shortPoll? YES

Does the time/date update also every shortPoll? YES, buts it one hour off. (DST?), Eisy was correct

I quess it would be easier to have asked, is the plugin working fine in UDM, just with the errors? YES appears that way.

I don't think this error will affect functionality, but there may be something missing or invalid in a plugin's definition files.

The plugin in slot 18 has an NLS file (en_us.txt) which appears to have many lines with something like ND-str-1 which is invalid as all prefixes with "ND-" should be followed the NodeDef ID then by "NAME" or "ICON", i.e. "ND-nodeDefId-NAME=Lamp Switch"

If you pull the file we can see the exact errors

/rest/profiles/family/10/profile/18/download/NLS/en_us.txt

 

 

Hi @Javi, thank you. Question, why might my UDM is not reporting the errors as well? I presume @dbwarner5 are on the same fw levels.

First question is if the plugin in slot 18 is your plugin.  Then my guess is the NLS is written programmatically and something has gone wrong.

@dbwarner5, I will look over the NLS file and update it, I may not get it done until this weekend but I will try for sooner. I will update the store when complete. 

Hi @dbwarner5, please give 1.0.12 a go.

-Tim

Solved it!  thanks!