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.

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?

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'.

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.

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.

Yes, I know. That is an ISY on Polisy issue, and has nothing to do with what my Node server displays.

It should be fine after restarting, as mine (on Polisy) was good after the restart. I did find a bug where the sunset/sunrise times were not being updated properly. The code was only checking for DST at startup, not every longPoll and release 3.2.21 corrects this. Timedata calculates Sunrise/Sunset times itself, independently of the Polisy/ISY, so the Timedata times should be correct now.

I just looked at this. I did find something that is related to the change to/from DST, so will issue an update in a bit. Restarting the polisy would restart everything, PG2, PG3 and all node servers.

Try restarting the Node server. If I recall correctly, I think calculations happen at midnight and of course the time change is at 2am. I'll look into this tomorrow when I get back home.

Yes, mine upgraded successfully too, showing the same log entries. My Polisy is also one of the early ones (geek release ?)

3.1.5 has been uploaded and @bpwwerhas confirmed the correct file is available on the PG3 server.

It was definitely uploaded. I installed it myself from the store and the correct version is running. I can try re-uploading tomorrow again. I have another minor update to post anyway.

Upgraded with no apparent issues. UI and backup work normally.

Yikes...actually it was simply matter of reading the screen and unticking a box...arghh. The migration is simple then, you can select Alexa, Google, IFTTT/Webhooks, License migration and update preferred ISY and migrate some or all. ?

Thanks @vbphil that's what I was wondering. I have paid licenses on both, so i can't use the portal migration tool directly. I'll open a ticket.

Thanks to @dbwarner5 for the effort in building this wiki. Meanwhile, how does one migrate from and ISY994i to ISY on Polisy (IoP) if both devices already have a license. When I try Maintenance: Migrate to: the result is an error telling me that my device already has a license, and no migration occurs. Is there another path? (short of re-entering them one at a time) Thanks!

US units have been changed to GPM. Requires at least ISY on Polisy version 5.4.0

Did you figure this out? in PG2 where you used :${sys.node.n014_timedata.GV10}, the PG3 version now uses: ${sys.node.n014_controller.GV10}

Sorry, as the nodeServer name and docs imply, it only supports the PureCool. I have no means of testing any changes that support another model as I only have a TP07. I can try making some changes for you to test, but it might take some time. I had planned to eventually add further settings for the oscillation function when time permits.

@jwagner010, sorry for the late reply, I didn't know that this thread existed, or i would have been following it. That looks for some reason like PG3 doesn't like something in the nodeserver installation. Could you please PM the pg3 logfile to me? I'll take a look at it.

Hi @Javi, As far as I can tell the node setup in both the ISY and PG look normal. This happens with a NS I'm developing, as well as any of the others I have installed, whether or not they're mine. If you'd like to try the remote diagnostic I'm open to it, I am indeed connected to the Portal. Thanks. G

@Javi, no, I don't have multiple instances operating. PG2 is connected to my isy994, and PG3 is connected to IoP. PG2 and PG3 are both operating on the Polisy.

Sorry, I missed this message. It's been a couple of weeks now....have you had any success in getting this NS to run? What version of ISY, PG3 and TimeData are you using? Thanks.

Sorry, @Javi, I'm not sure what you mean by "will any of the node servers work without hardware". The fault does seem to be specific to PG3 nodeservers - I have a couple of the same ones running on both PG2 and PG3. Another thing I notice is that it seems to be related somehow to editors or nls. I haven't checked enough times yet to confirm but it seems that when the item being set/changed/cleared has a uom of 25 with text in the nls, the error occurs. Doing something like changing a temperature setpoint for instance, with a pure number, doesn't cause an error. If you like I can send you the profile files of one of my PG3 nodeservers that is exhibiting this behaviour. Thanks, G

@Javi, same thing with both ELK and Hue disabled. I don't recall what the last version of PG3 was before installing 3.0.40. Each time I make attempt this is all that appears in the ISY error log: Time User Code Message Thu. 2022/02/10 04:29:00 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Thu 2022/02/10 04:30:10 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Thanks, G