Rainmachine unplugged for 6 days causing issues

[stevehoyt]

Hi

 

I was gone for 6 days and while I was gone someone unplugged my rain machine. When I got back I noticed the poly was getting errors to the effect " controller not found in database".  Also it showed as disconnected in the PG3 display. Most status in the admin console appeared ok however. Anyway I  restarted it to see if that would fix it. No change. I then deleted and reinstalled it in the same slot. It no longer will install. I also rebooted the polyglot along with re powering up the polisy. No luck.  I am not sure what to do next. I have attached various log files and screen caps. Not sure if they will be of value as it was down for so long.

Any help to get it back up would be appreciated.

debug.log pg3-current.log

[glarsen]

Looks like you have a dead copy still connected to MQTT, although I would have thought the restart would have fixed that.  Are you able to ssh to your polisy to kill it?

ps ax|grep rm-poly
84788  -  I       96:50.60 python3 ./rm-poly.py (python3.8)

sudo kill 84788 (this number will be different, specific to the your copy)

After doing that, restart the rainmachine Node server.  It should be showing 3.1.5.  As far as I can tell, it looks like it installed ok, according to the PG3 log.

Edited March 13, 2022 by glarsen

[bpwwer]

Just to add some clarity, there is not an error "db_getNodeDrivers: controller not found in database".  That is a WARNING. It may or may not indicate something is wrong.   It is more of an informational message for node server developers.  There are cases where not being able to find something in the database could be the reason for something not working as expected and there are cases where this is normal.   In this case, since it happens right at the start, it most likely is because the database that it's checking has not yet been loaded and is empty so it is an expected warning.

Remember PG3 is in a alpha state.  There are going to be a lot of log messages that won't be of much use to users but are there to help developers debug.

[stevehoyt]

@bpwwer  @glarsen

 

 I tried what you mention above. No luck see the screen caps below. 

It won't let me install it still.

Any ideas for what to try next

 

[stevehoyt]

I talked to support and they had me update and upgrade. That appears to have fixed my issues and I can install rain machine again. I used the same slot ( 12 ) as before. 

Everything looks ok. I can see each zone etc. I have a new problem. My programs are now getting errors. I can no longer access the status variable in them. All was running fine before. I am running them on a standalone isy at 5.3.4. Could you check this please.

 

Thanks

[glarsen]

23 hours ago, stevehoyt said:

I talked to support and they had me update and upgrade. That appears to have fixed my issues and I can install rain machine again. I used the same slot ( 12 ) as before. 

Everything looks ok. I can see each zone etc. I have a new problem. My programs are now getting errors. I can no longer access the status variable in them. All was running fine before. I am running them on a standalone isy at 5.3.4. Could you check this please.

 

Thanks

It would be helpful if you could provide some additional information to troubleshoot this, such as:

1. Version of Polyglot (i assume you're using PG3?)

2. Version of rainmachine installed.

3. Set the rainmachine log level to debug and restart the Node server.  Then zip the log file and PM it to me.

4. Exactly what you are trying to do with the status variable. 

I haven't had any issues with this Node server working with either my ISY at 5.3.4, or IoP at 5.4.1, so I have no idea why your installation isn't working correctly.

Thanks.

[stevehoyt]

here you go.. sorry for not providing enough info the first time. The first screen shot is the program that has been running for a couple months now without any issues. It now does not trigger on the if statement being true. You will notice the program names are all yellowed out now. The second capture show many programs as out of memory. This is a  typical problem I see when some statement has an error. If I try to fix the problem in this example, that the if statement is not being triggered, I am no longer able to see the status in the pulldown menu for the if statement. It does show up in the list of items for my site.  See next capture . Versions I am using are last capture. I installed it in the same PG3 slot as before, but am guessing the link to the status variable for the if statement, somehow got messed up. Let me know if you need the log file after all. 

 

Thanks

 

 

[Bumbershoot]

@stevehoyt, for the programs that are yellowed and say "Out of Memory" in the status page, the first thing to try is to simply re-save these programs.  They may or may not need an edit (I would inspect them), but clicking on the "Save Changes" button might restore the functionality of the programs.   This is a problem that was encountered often when folks upgraded from the v4.x.x firmware to 5.x.x firmware in the ISY994.  It's a simple thing to try, at least...

[glarsen]

15 hours ago, Bumbershoot said:

@stevehoyt, for the programs that are yellowed and say "Out of Memory" in the status page, the first thing to try is to simply re-save these programs.  They may or may not need an edit (I would inspect them), but clicking on the "Save Changes" button might restore the functionality of the programs.   This is a problem that was encountered often when folks upgraded from the v4.x.x firmware to 5.x.x firmware in the ISY994.  It's a simple thing to try, at least...

Thanks @Bumbershoot.  I also experienced some of this when moving from PG 2 to PG3.  The fix was also as suggested, to click on an element, then 'Update', then 'Save Changes'.

[stevehoyt]

Thanks @glarsen and @bumbershoot. I have tried to change the if statement and cannot. If I change another statement and do a save the yellow goes away. I'll see if they start running again. If I try to create any new programs, I still am not able to create an if statement checking whether a circuit is running. It no longer appears in the pull down list. 

is it possible for one of you to try createing an if statement to check for a circuit running? and see if it works for you. Then I will know it is a problem just with me. 

Perhaps I should delete the node server and reinstall it in a different slot.

Thanks

Steve

Edited March 17, 2022 by stevehoyt

[Bumbershoot]

2 hours ago, stevehoyt said:

is it possible for one of you to try createing an if statement to check for a circuit running? and see if it works for you. Then I will know it is a problem just with me. 

I haven't turned on the system yet, still too many freezes overnight, and I'm still running on my ISY994 and PG2, not IoP and PG3.  The Node server is running normally...

[glarsen]

Steve, can you confirm which version of ISY you are running.  I'm assuming you are still on the ISY994i, and not the ISY on Polisy, correct?

[stevehoyt]

yes I have a standalone isy running 5.3.4 and admin console at 5.3.4 . Michael asked me to do a complete reinstall which I just completed. Here are a few screen caps I sent to him also. The first 3 caps show the server being uninstalled and verified cleared out of admin console, and programs missing ref to the node server. Then the reinstall and reboot of ISY along with programs now referencing the variable but again now yellowed out. Am still not seeing the zones in the pull down of the if statements. Also not sure if he told you, I installed a second copy on my second rain machine in a different slot as test and got the same results. The nodes get populated and report the change in status just fine, so that part is good just can't reference in an if statement it appears. The screen caps seem to out of order I am not sure why. 

Edited March 18, 2022 by stevehoyt

[glarsen]

@stevehoyt, I've discovered something, just don't have the answer yet.  There is something different about the way the Node server loads into the ISY994 and the ISY on Polisy.  The identical code and profile work as expected on IoP, yet zone status seems to be missing from the ISY installation.  Other nodes statuses are fine, just zones seem to be different.  Still trying to figure out why.

[stevehoyt]

Great news. I wonder what changed recently, as it has been running fine for a couple months.

It is not urgent to get it running right away. I have a couple months before I need my app. Michael has also discussed the possibility of moving to isy on Polisy if the fix is too hard. As you know, I was waiting for the official release before doing that, but can move it up if the fix on an i994 does not make sense. 

 

 

[glarsen]

So far I have no idea what the issue is, the profiles and code are identical whether you're using an ISY or the IoP.  I do see the same thing as you, here, but can't explain it yet.   Michel has mentioned he would suggest migration to you. 

[bpwwer]

30 minutes ago, glarsen said:

So far I have no idea what the issue is, the profiles and code are identical whether you're using an ISY or the IoP.  I do see the same thing as you, here, but can't explain it yet.   Michel has mentioned he would suggest migration to you. 

Have you tried enabling the java console and starting the admin console for the ISY?  If the ISY has issues parsing the profile files, it should log those to the java console.

There shouldn't be any difference in the ISY vs. IoP parser but given that IoP has been getting a lot of updates recently something may have been fixed that and not in the ISY firmware.

[glarsen]

@stevehoyt 

This is the reason.  I had forgotten about this until now.  The profile changes in this version break it for the ISY994.

 

The PG2 version works but does not support flow rate

Edited March 18, 2022 by glarsen

[glarsen]

55 minutes ago, bpwwer said:

Have you tried enabling the java console and starting the admin console for the ISY?  If the ISY has issues parsing the profile files, it should log those to the java console.

There shouldn't be any difference in the ISY vs. IoP parser but given that IoP has been getting a lot of updates recently something may have been fixed that and not in the ISY firmware.

@bpwwer, the issue is that there is a UoM being used in the PG3 version that is only available on the IoP.  See the linnk above.

Edited March 18, 2022 by glarsen

[stevehoyt]

@glarsen 

Ah Ha....and I was the one that requested you add it.

Poetic Justice I guess huh

It does however bring up an issue. If I remember correctly, you or someone else, said that there were not going to be any further code releases for the 994 version. 

It seems this is the first of many examples, I would expect, where the PG3 version of a node server is going have to be classified as for IoP only. 

I would expect that UDI will have to start documenting these prerequisites.  

Would you like to have the discussion of your findings with @Michel Kohanim or should I bring it up. 

[glarsen]

I have already updated Michel

4 minutes ago, stevehoyt said:

Would you like to have the discussion of your findings with @Michel Kohanim or should I bring it up. 

I have already updated Michel.  The pre-requisite is documented in the Node server documentation.

Quote

It does however bring up an issue. If I remember correctly, you or someone else, said that there were not going to be any further code releases for the 994 version. 

I don't believe there are any further firmware releases planned for the ISY994i, and it does not have UoM support for GPM, and a number of other new UoMs. I'm also not planning any further releases for the PG2 version of the Node server.

Edited March 18, 2022 by glarsen