glarsen

Hi Jim, I'm seeing this error on "Purge Execute" when updating elements on my Harmony Hub. 2023-11-25 10:30:56,006 Command udi_interface WARNING Controller:purge: Deleting Activity for "Media Room Hub" that is no longer used a45241859 "Watch Fire TV" 2023-11-25 10:30:56,006 Command udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-11-25 10:30:56,006 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed harmonyctrl.runCmd(PURGE_EXECUTE) 'Controller' object has no attribute 'controller' Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902628f_12/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 960, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/pg3/ns/0021b902628f_12/.local/lib/python3.9/site-packages/udi_interface/node.py", line 172, in runCmd fun(self, command) File "/var/polyglot/pg3/ns/0021b902628f_12/nodes/Controller.py", line 642, in _cmd_purge_execute self.purge(do_delete=True) File "/var/polyglot/pg3/ns/0021b902628f_12/nodes/Controller.py", line 499, in purge self.controller.poly.delNode(address) AttributeError: 'Controller' object has no attribute 'controller' 2023-11-25 10:30:56,029 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-11-25 10:30:56,113 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices The purge fails, though the plugin remains running. Edit: It does appear that manually deleting the affected nodes does work though.

Sinope TH1300ZB, TH1124ZB, TH1123ZB would be a good addon here! https://sinopetech.com/en These are: 1) floor heat thermostat, 2) 4000 and 3000 watt electric baseboard heat thermostats respectively eisy 5.7.0 w USB Zmatter finds them and lists them as "unsupported work queue request 6 ignored" Sinope also offers dimmers, switches, load controllers, water detectors and other elements in either Zigbee or Wi-Fi

Oh, OK. I thought you were referring to the Intesis NS. Sorry

Where do you see that? It was never availablke for V2, only V3.

Yes

There is one that uses the Intesis WI-Fi adapter. I built it because I have 2 Daikin Heat Pumps in my home. Simplistic but reliable.

I just paid for it on Sept 30th, hence my frustration.

The problem seems to have returned for me. For 2 days now I have been unable to successfully restart this node server. Might be time to give up and request a refund.

I just swapped out my Schluter Thermostat for a NuHeat and it's been working fine for over 3 years. A bit more expensive than a node server, but if there isn't one. ....

Update to 3.2.23 seems to be OK here.

I had a "!", same thing, no change.

@Goose66, I am also experiencing the same issue as @dbwarner5. Several attempts over the past 36 hours result in the same error. PG3x 3.2.9, ISY 5.7.0_4. Thanks

I experienced the same situation with this upgrade on my eisy. All disabled programs were showing enabled and the error log showed nothing unusual. I needed to perform a restore to get things back to the proper state.

Once you click on Timedata in the store, the page that comes up will have an "Install" button which will then allow you to choose which PG3x slot to insta6it in.

For simple time and date information the built in ISY functions are fine and even recommended. This Node Server offers a bunch of mundane variants on the concept of time 🙂. See Docs/TimedataPG3/README.md at main · ve7gel/Docs (github.com) for some idea.

It turns out, after running your sample program overnight, that it doesn't replicate this every hour, only periodically, with no pattern I can discern. I'm thinking it has something to do with timing related to when the Node Server was started (how close to the change of the actual minute), which then may cause some logic confusion in the ISY. There is nothing in the Node Server code that would make it trigger differently from one minute to the next, nor is there any dependency on the hour changing. Are you able to use the built-in time/date functions of the ISY for this? The Node Server only changes the display of the minute on the next shortPoll after the minute actually changes, which may be up to 59 seconds late, depending upon when in the minute the Node Server was last started.

While I can replicate this phenomenon, I am not clear on why it is happening. In checking both the code and my local logs, the Node Server only updates the minute value once each time the minute changes. I can't explain why the program is triggered on the 00 minute of the next hour. Try reversing the order of the hour and minute conditions in the program and see if it makes any difference. Also, you can try changing your shortPoll value to 60 from the default of 30. :

Same for me this morning

Same here.

I also reinstalled using 1.0.9. Everything thing works as expected.

So, the heartbeat fix was trivial. 3.2.1 is indeed there now with the fix. Note: Since 3.2.0 was so old, and with significant changes to PG3x since it was released, you may have to re-install rather than just restart to update.

I've noticed that ping error too, but haven't had time to look into it. I thnk something changed with the ping API call. It's only a status check and had no operational effect on the NS, so I haven't prioritized it yet. There is no 3.2.1, that seems to have crept in during another node server update. (though I guess there will be once the ping check is fixed)

See the same thing - the Confirm/Cancel dialog is greyed out/inactive after installing 3.1.24

Updated to 5.5.9 with no issues on eisy with pg3x 3.1.22. The "Update Packages" message seems to have gone.

@jwagner010, @bpwwer, thanks for your patience and help in resolving this. A brain **** when cleaning up old node server entries in my dev list caused it all.