glarsen

@kzboray, I did notice at the time that I updated to 5.8.3 that none of my Python plugins started initially either, but after a second reboot they all came up properly. And under 5.8.4 they all seem ok too.

@tmorse305, the issue for some seems to have arisen after updating to IoX 5.8.4.

And yet all of mine are fine...including RainMachine. Which hardware are you on - Polisy or eisy? Not that it should matter, but....

@chadm, Meteobridge 3.2.0 is available which incorporates indoor temperature, humidity, and dew point. Let me know if you have any issues.

There's a new version of Meteobridge that I just uploaded incorporating some changes requested by another user. The file for both Polisy and eisy is identical and runs fine on both of my Polisy and eisy, so I'm not sure why you're seeing that. In any case, try 3.2.0 and see if it works.

Don't see why not. Give me a couple of weeks and I'll get it done. Just finishing up a move into a new location and still finding things.

I'll have a look as soon as I can. We're just finishing up moving and setting up my development platform should be done by the weekend. What type of weather hardware are you using? Also, please set the logging to debug and restart the plugin. Then download the lig package and PM it to me.

@cosyn, sorry I've been unable to respond or help. I'm in the process of moving and have no access to any of my dev stuff (since Dec. 27), and not for another week or so yet. Finally got a laptop fired up today in a hotel room and saw all of this. I can't remember what forced the change to the node names since it was more than a year ago-I had even forgotten about that until I saw this thread. I'm glad UD was able to help. Thanks for your patience.

First off, make sure that the plugin is installed in the same slot in PG3x as it was in PG2. There were no code changes in the functional code between PG2 and PG3x so it should work the same way.

I tried uninstallating, rebooting and reinstalling, all with no success. And it's been over 24 hours now so it doesn't seem that anything is changing.

And I see the rust installation in /usr/local, including the compiler in bin, so I dunno.

Do I need to open a ticket with UDI? Or do you have a suggestion to fix?

DId the last version depend on Rust too? It ran ok.

Done

Yes, I'm at 5.7.1_2

Upgraded to 3.1.1 it seems successfully, however the PG3 dashboard shows it as "Disconnected" , the ns seems to be restarting over and over. I see this in the log 2023-11-26 09:37:47,933 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-11-26 09:37:47,935 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902628f_16/kasa-poly.py", line 12, in <module> from nodes import VERSION,Controller File "/var/polyglot/pg3/ns/0021b902628f_16/nodes/__init__.py", line 9, in <module> from .SmartDeviceNode import SmartDeviceNode File "/var/polyglot/pg3/ns/0021b902628f_16/nodes/SmartDeviceNode.py", line 8, in <module> from kasa import SmartDeviceException ModuleNotFoundError: No module named 'kasa' 2023-11-26 09:37:49,168 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-11-26 09:37:49,168 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-11-26 09:37:49,168 MainThread udi_interface INFO __init__:<module>: User=0021b902628f_16 repeatedly. I'm on PG3 3.2.16. I've restarted PG3 as well as reinstalled the plugin with no effect.

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