skunkiechris

I have an old pg2 instance running LiFX, which I'm finally ready to move to eISY's polyglot. I am using a devlist.yml file, as auto discovery is not reliable. I've put my devlist.yml into the nodeserver directory and changed the owner, but every time I start the NS, discovery ends with this (different bulb/mac address each time): 2025-02-18 09:48:54.077 Thread-4 (_discovery_process) udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:75:67:e6 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> If I remove the devlist file, it attempts auto discovery (and gets some bulbs) - so it is seeing the file, but it's not working. My devlist file is fine, it's a direct copy of what is in production today. Help?

Getting the attached error message when attempting to execute any network resource via the app. I have synchronized a couple of times. It seems to happen with all network resources. Thanks!

Probably too soon for any subjective feedback, but wondering how much of the performance of IoX is disk based, vs processor & RAM. As in, @Michel Kohanim, is the upgrade worth it just for running IoX, or is this more of an upgrade that is useful for running other tasks (VM's, etc) on eisy? Thanks!

Haven't had the client stopped error a single time since the change....seems to be working!!! Thanks again!!

@DavidV I went through this exactly same thing a few months ago. Opened a ticket, and the suggestion was to migrate from zooz to zmatter. (I had zmatter, just wasn't using it due to migration issues the previous time I attempted it.) I did eventually migrate to zmatter, but one of the releases prior to that (5.7 maybe) seemed to completely solve it for me. It was very mysterious, in the end not entirely sure what exactly fixed it. But like I said, it was exactly the same symptoms!

First reboot, then power cycle after reboot, both resulted in being stuck on Initializing subscription.

Same as above, Vista 21IP, EnvisaLink4. And, same in terms of used to use the IP module for Total Connect, got rid of that part some time ago as well. The only shortcoming that I have hit is that the Vista panels stop reporting sensor activity when the alarm is armed in any state. So, night, stay, away...you won't get motion, door/window, etc activity reported to IoX. Not a deal breaker for me....the couple of spots that I needed that info I've just used insteon or z-wave modules to supplement.

A unplug/plug followed by IoX restart usually works as well.

Just curious as to the reasons behind that suggestion? (I'm not disputing it lol, just curious.)

Hmmm....I hadn't actually grabbed the log yet when it started working yesterday. I just went to look now and I only see a log from today in the logs directory. I guess logs are deleted on a daily basis?

Okay, so, I did absolutely nothing whatsoever. When I left it the main device in eisy was borked, and all my programs had not specified, no nodes in polyglot. Went away, made dinner, turned on the TV, and everything reacted correctly. Looked at eisy/polyglot, and things are normal. So, I guess disregard the above!

@Jimbo.Automates Hmmmm, it doesn't seem to work after the update. My hubs.json is still in the config director, I changed nothing....but it doesn't see the Harmony at all. 2023-12-19 15:35:26,909 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: User=0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: PG3INIT=<redacted> 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-19 15:35:26,955 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-19 15:35:27,483 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-19 15:35:27,712 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-19 15:35:27,714 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.16 [ISY: 5.7.1, Slot: 14] 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'} 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-19 15:35:27,772 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026524_14.cert key: 0021b9026524_14.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-19 15:35:27,773 MainThread udi_interface INFO Controller:__init__: HarmonyController: Initializing 2023-12-19 15:35:27,773 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: harmonyctrl not found in database. 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:addNode: Adding node HarmonyHub Controller(harmonyctrl) [None] 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:setController: Using node "harmonyctrl", driver "ST" for connection status. 2023-12-19 15:35:27,819 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-19 15:35:27,820 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_14 - MID: 2 Result: 0 2023-12-19 15:35:27,861 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': ''} 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-19 15:35:28,115 Thread-5 udi_interface.interface WARNING interface:checkProfile: check_profile: Force is enabled. Seems like maybe that warning line is something? Thanks...

Awesome, I've updated, will let you know, thank you so much!!!

With the move to ZMatter, my motion sensors have two motion nodes now, 155 Motion Sensor, which is what they've always had, plus 380 Binary Motion Sensor. They seem to activate exactly the same. Is there any difference between the two? Thanks!

Thirdreality multifunction motion sensor, illumination sensor, and multicolor nightlight. Currently works as multicolor light with on/off, no motion or illumination sensing. Model: 3RSNL02043Z Amazon: https://www.amazon.com/dp/B0C9LNXYLL

He, I guess I forgot to say that this behavior coincided with the migration from Zooz to ZMatter. But today it seems to be normal, so, who knows.

I have multiple Kwikset 620 Zwave 700 deadbolts. Most work perfectly fine, but one does not operate the vast majority of the time when sent commands, but there is also no failure showing in the log, nor does it ever say can't communicate. In the L3 log these are all the transactions I see, and the lock does absolutely nothing: Tue 12/12/2023 01:57:30 PM : [ZW-TX-A 00127 54.0 ] [ZY054_1] Door Lock Set mode=0 Tue 12/12/2023 01:57:31 PM : [ZW-DONE 00127 54.0 ] [ZY054_1] Door Lock Set mode=0 I've attached the ZWAY log file for the operation, I don't know how to interpret all of that. All the nodes are present on the lock, and I have rewritten links and updated neighbors, there are no communication issues at all. (It's also about....20 feet from the zmatter dongle. Any help would be appreciated!! Thanks! zy log.txt

Thanks so much!!!

Yes I do. Edit: Also, it's interesting that it seems to happen after 3AM, when the query runs. Not sure I need that anymore, maybe I'll disable it and see what happens...

Hello, every few days the node server semi-crashes, semi as in it is non-functional, but it is still running. Here is the log: 2023-12-04 03:02:29,708 read_thread sleekxmpp.xmlstream.xmlstream ERROR xmlstream:_process: Error reading from XML stream. 2023-12-04 03:02:47,204 Command sleekxmpp.xmlstream.handler.waiter WARNING waiter:wait: Timed out waiting for IqWait_d0d0f51b-e409-4549-a109-816ac91d8f77-11 2023-12-04 03:02:47,205 Command pyharmony.client INFO client:get_current_activity: XMPP timeout, reattempting 2023-12-04 03:03:17,209 Command sleekxmpp.xmlstream.handler.waiter WARNING waiter:wait: Timed out waiting for IqWait_d0d0f51b-e409-4549-a109-816ac91d8f77-11 2023-12-04 03:03:17,209 Command udi_interface ERROR udi_interface:write: --- Logging error --- 2023-12-04 03:03:17,212 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-12-04 03:03:17,212 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/pyharmony/pyharmony/client.py", line 78, in get_current_activity result = iq_cmd.send(block=True) 2023-12-04 03:03:17,212 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/sleekxmpp/stanza/iq.py", line 233, in send raise IqTimeout(self) 2023-12-04 03:03:17,212 Command udi_interface ERROR udi_interface:write: sleekxmpp.exceptions.IqTimeout: <iq id="d0d0f51b-e409-4549-a109-816ac91d8f77-11" type="get"><oa xmlns="connect.logitech.com" mime="vnd.logitech.harmony/vnd.logitech.harmony.engine?getCurrentActivity" /></iq> 2023-12-04 03:03:17,212 Command udi_interface ERROR udi_interface:write: During handling of the above exception, another exception occurred: 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 252, in _get_current_activity ca = self.client.get_current_activity() 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/pyharmony/pyharmony/client.py", line 81, in get_current_activity result = iq_cmd.send(block=True) 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/sleekxmpp/stanza/iq.py", line 233, in send raise IqTimeout(self) 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: sleekxmpp.exceptions.IqTimeout: <iq id="d0d0f51b-e409-4549-a109-816ac91d8f77-11" type="get"><oa xmlns="connect.logitech.com" mime="vnd.logitech.harmony/vnd.logitech.harmony.engine?getCurrentActivity" /></iq> 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: During handling of the above exception, another exception occurred: 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-12-04 03:03:17,213 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 1083, in emit msg = self.format(record) 2023-12-04 03:03:17,214 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 927, in format return fmt.format(record) 2023-12-04 03:03:17,214 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 663, in format record.message = record.getMessage() 2023-12-04 03:03:17,214 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 367, in getMessage msg = msg % self.args 2023-12-04 03:03:17,214 Command udi_interface ERROR udi_interface:write: TypeError: not all arguments converted during string formatting 2023-12-04 03:03:17,214 Command udi_interface ERROR udi_interface:write: Call stack: 2023-12-04 03:03:17,216 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 937, in _bootstrap self._bootstrap_inner() 2023-12-04 03:03:17,216 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner self.run() 2023-12-04 03:03:17,216 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run self._target(*self._args, **self._kwargs) 2023-12-04 03:03:17,216 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 859, in _parseInput self._handleInput(key, input[key], None) 2023-12-04 03:03:17,216 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 1007, in _handleInput self.nodes_internal[item['address']].query() 2023-12-04 03:03:17,217 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Controller.py", line 210, in query self.poly.getNode(node).query() 2023-12-04 03:03:17,217 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 94, in query self._get_current_activity() 2023-12-04 03:03:17,217 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 254, in _get_current_activity LOGGER.error('client.get_current_activity timeout',False) 2023-12-04 03:03:17,217 Command udi_interface ERROR udi_interface:write: Message: 'client.get_current_activity timeout' Arguments: (False,) 2023-12-04 03:03:17,217 Command udi_interface INFO Hub:_set_st: setDriver(ST,0) 2023-12-04 03:03:17,264 MQTT udi_interface.interface INFO interface:_message: Successfully set h9bfc75ec675d0 :: ST to 0 UOM 2 2023-12-04 03:03:17,730 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Living Room(h9bfc75ec675d0) 2023-12-04 03:03:17,731 Command udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:03:17,731 Command udi_interface INFO Hub:_set_st: setDriver(ST,1) 2023-12-04 03:03:17,731 Command udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:03:17,731 Command udi_interface ERROR udi_interface:write: --- Logging error --- 2023-12-04 03:03:17,731 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 252, in _get_current_activity ca = self.client.get_current_activity() 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: AttributeError: 'NoneType' object has no attribute 'get_current_activity' 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: During handling of the above exception, another exception occurred: 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 1083, in emit msg = self.format(record) 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 927, in format return fmt.format(record) 2023-12-04 03:03:17,732 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 663, in format record.message = record.getMessage() 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/logging/__init__.py", line 367, in getMessage msg = msg % self.args 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: TypeError: not all arguments converted during string formatting 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: Call stack: 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 937, in _bootstrap self._bootstrap_inner() 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner self.run() 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run self._target(*self._args, **self._kwargs) 2023-12-04 03:03:17,733 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 859, in _parseInput self._handleInput(key, input[key], None) 2023-12-04 03:03:17,734 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 1007, in _handleInput self.nodes_internal[item['address']].query() 2023-12-04 03:03:17,734 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 94, in query self._get_current_activity() 2023-12-04 03:03:17,734 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026524_14/nodes/Hub.py", line 258, in _get_current_activity LOGGER.error('client.get_current_activity failed',True) 2023-12-04 03:03:17,734 Command udi_interface ERROR udi_interface:write: Message: 'client.get_current_activity failed' Arguments: (True,) 2023-12-04 03:04:21,912 Thread-1049 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:04:21,913 Thread-1049 udi_interface INFO Hub:_set_st: setDriver(ST,1) 2023-12-04 03:04:21,913 Thread-1049 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:09:21,913 Thread-1055 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:09:21,913 Thread-1055 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 03:14:21,919 Thread-1061 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:14:21,919 Thread-1061 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:19:21,935 Thread-1067 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:19:21,935 Thread-1067 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 03:24:21,936 Thread-1073 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:24:21,936 Thread-1073 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:29:21,941 Thread-1079 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:29:21,941 Thread-1079 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 03:34:21,942 Thread-1085 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:34:21,942 Thread-1085 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:39:21,946 Thread-1091 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:39:21,946 Thread-1091 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 03:44:21,955 Thread-1097 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:44:21,955 Thread-1097 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:49:21,956 Thread-1103 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:49:21,956 Thread-1103 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 03:54:21,957 Thread-1109 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:54:21,957 Thread-1109 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 03:59:21,960 Thread-1115 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 03:59:21,961 Thread-1115 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:04:21,967 Thread-1121 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:04:21,968 Thread-1121 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:09:21,969 Thread-1127 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:09:21,970 Thread-1127 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:14:21,970 Thread-1133 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:14:21,971 Thread-1133 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:19:21,981 Thread-1139 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:19:21,981 Thread-1139 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:24:21,983 Thread-1145 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:24:21,983 Thread-1145 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:29:21,992 Thread-1151 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:29:21,992 Thread-1151 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:34:22,001 Thread-1157 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:34:22,001 Thread-1157 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:39:22,017 Thread-1163 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:39:22,018 Thread-1163 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:44:22,024 Thread-1169 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:44:22,024 Thread-1169 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:49:22,031 Thread-1175 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:49:22,032 Thread-1175 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 04:54:22,033 Thread-1181 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:54:22,033 Thread-1181 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 04:59:22,035 Thread-1187 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 04:59:22,036 Thread-1187 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 05:04:22,044 Thread-1193 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:04:22,044 Thread-1193 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 05:09:22,061 Thread-1199 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:09:22,062 Thread-1199 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 05:14:22,066 Thread-1205 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:14:22,066 Thread-1205 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 05:18:29,475 Command udi_interface ERROR Hub:start_activity: No Client 2023-12-04 05:19:22,076 Thread-1211 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:19:22,076 Thread-1211 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 05:20:23,055 Command udi_interface ERROR Hub:start_activity: No Client 2023-12-04 05:24:22,078 Thread-1217 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:24:22,078 Thread-1217 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 05:29:22,081 Thread-1223 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:29:22,081 Thread-1223 udi_interface INFO Controller:heartbeat: hb=0 2023-12-04 05:34:22,096 Thread-1229 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:34:22,096 Thread-1229 udi_interface INFO Controller:heartbeat: hb=1 2023-12-04 05:39:22,104 Thread-1235 udi_interface INFO Hub:check_client: Client was stopped. clientNone 2023-12-04 05:39:22,105 Thread-1235 udi_interface INFO Controller:heartbeat: hb=0 It just continues to repeat the 'client was stopped' message until I eventually notice and restart the nodeserver. Thanks!

Just FYI, once I copied over the hub config file, everything worked perfectly from there. 🙂 (I had been using the PG2 version until now.) Thanks for all your work!!

Same experience. I grabbed my hub file from PG2 and moved it over, so I'm okay. But auto discovery was on the completely wrong subnet for some reason, and manual didn't work for me either.

Hi, a long time ago back in the 500 ISY zwave days, my Kwikset locks had support for creating user schedules in ISY. It disappeared some time ago, and has never come back. I now have 700 series Kwikset 620 deadbolts, on zmatter, and wondering if support can be added for creating schedules? Can't quite recall if we're supposed to open a ticket for requests like this... 🙂 Thanks!

Hello, Does anyone know if the Rainbee8 is fully supported by IoX, as a replacement for the EZFlora? (Here.) I haven't seen any mention of it on the forums anywhere....wondering if it's backwards compatible enough and just the new functions won't work, or if support has been added, or it won't work at all! Thanks!

The limit on the free account is 50 queries per day (as of when I have no idea). So a short poll of 300 will quickly exceed your max. I'm not sure how they work that, as when I was experiencing it I waited a day but still got nothing. I eventually upgraded to the $40 plan and everything started working fine.