Error updating RAINRT

[johnnyt]

PG3 is reporting an error updating WeatherFlow NS RAINRT value

11/30/2022, 08:34:05 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 352.140541ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.07758000000000001/46

11/30/2022, 08:41:05 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 357.517191ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.8210999999999999/46

11/30/2022, 08:43:03 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:55:cd] :: [404 - OK] :: 356.864566ms - http://192.168.200.251:80/rest/ns/6/nodes/n006_207296/report/status/RAINRT/0.43776000000000004/46

This seems similar to a previous post I made that I can't find right now where I think the NS was receiving a number in a format it couldn't handle (number of decimals, I think). Strange that I didn't see this particular one when I saw the other ones. I guess I just haven't looked my logs when it was raining...

Here's what the NS shows right now - seems to only accept 5 decimal places when it's getting lots more

How come there isn't an error entry in NS log, only in PG3 log?

here's the 08:43:03 entry in NS log:

2022-11-30 08:43:03,802 MQTT       udi_interface.interface INFO     interface:_message: Successfully set 207296 :: RAINRT to 0.43776000000000004 UOM 46

Is the PG3 error an error?

[bpwwer]

It's not the node server it's the ISY/IoP that won't accept the precision.  The node server is converting units and the conversion results in more decimal places than the ISY/IoP can handle.

Fixed in version 3.0.26

[macjeff]

I saw the message (PG3 3.1.15) and it said version 3.0.26 was avaialable

I hit restart and it took a while and came up.

Message is gone and its running but it still says 3.0.25 not 3.0.26

I can do the reinstall if you want but you had said not to do that unless instructed.

 

WeatherFlow_12-1-2022_72749-AM.zip

[macjeff]

I will PM you the entire PG3 log

Check between 6:30 and 7:30 am my time

[macjeff]

more issues.  We can move to another topic but I think the fix for all of the issues is to erase and install.

I had two units (an old air and sky) replaced by them.

I did this over a month ago

1. Changed the ID for the air and Sky.  New ones showed up.

2. Deleted the old nodes

Then today when I rebooted the two old nodes came back.  I thought I had deleted from the PG3 configuration which auto deleted from the ISY but it did not.

I tried to delete today from pg3 and it says error removing node.

I will send another Pg3 and weatherflow log to you now since I did this after the last log

If erase Node Server is needed I will do that.

[johnnyt]

1 hour ago, macjeff said:

I saw the message (PG3 3.1.15) and it said version 3.0.26 was avaialable

I hit restart and it took a while and came up.

Message is gone and its running but it still says 3.0.25 not 3.0.26

same here.

No rain expected for another couple days so can't say if the issue is fixed but I assume it is.

[bpwwer]

4 hours ago, macjeff said:

more issues.  We can move to another topic but I think the fix for all of the issues is to erase and install.

I had two units (an old air and sky) replaced by them.

I did this over a month ago

1. Changed the ID for the air and Sky.  New ones showed up.

2. Deleted the old nodes

Then today when I rebooted the two old nodes came back.  I thought I had deleted from the PG3 configuration which auto deleted from the ISY but it did not.

I tried to delete today from pg3 and it says error removing node.

I will send another Pg3 and weatherflow log to you now since I did this after the last log

If erase Node Server is needed I will do that.

Changing the configuration doesn't delete any nodes.  You'd have to delete the node from PG3 which should then also delete them from the ISY.   Both the ISY and PG3 keep a record of what nodes were created.  If you delete from just ISY, it doesn't notify PG3 and thus PG3 continues to have a record of those nodes.

Depending on what steps you actually took back then, this may be expected behavior.

[bpwwer]

5 hours ago, macjeff said:

I saw the message (PG3 3.1.15) and it said version 3.0.26 was avaialable

I hit restart and it took a while and came up.

Message is gone and its running but it still says 3.0.25 not 3.0.26

I can do the reinstall if you want but you had said not to do that unless instructed.

 

WeatherFlow_12-1-2022_72749-AM.zip 194.89 kB · 0 downloads

From this log it looks like PG3 didn't detect that there's a new version and thus it didn't do the autoupdate.   

There are two places where it checks for updates.

1) when it pulls a new copy of the node server store data, it compares it with the copy currently in PG3 and if it sees an installed node server with a new version it creates the notice.

2) when a node server starts it compares the version that was running with the current node server store version and auto-updates if they are different.

It sounds like the first is working correctly but the second may still be buggy.  I don't have time right now to look into it as I'm busy helping to get things ready for the eisy and we're on a deadline to get the initial image done.  Once that's out of the way I can start looking into the issues again.

[macjeff]

8 minutes ago, bpwwer said:

Changing the configuration doesn't delete any nodes.  You'd have to delete the node from PG3 which should then also delete them from the ISY.   Both the ISY and PG3 keep a record of what nodes were created.  If you delete from just ISY, it doesn't notify PG3 and thus PG3 continues to have a record of those nodes.

Depending on what steps you actually took back then, this may be expected behavior.

I did try to delete from ISY.  Due to the update issue and this issue, I am going to erase and reinstall this Node Server.  There are only a couple programs that use it so easy to do. 

I will test the bug with next build. Or you can put out a quick update at a later date and I will test it.