skunkiechris

Weird though, I upgraded to the 25,000 queries/day, as I mentioned, and I'm still getting the original error message, which is confusing. 2023-06-01 11:47:41,784 Command udi_interface ERROR query:query_conditions: No response object in query response. When I manually hit the URL it is displaying in the debug level log literally nothing happens. It gives no success, no fail. nothing at all. 😕 Which make me assume it's not an issue on your side.... 🤷 Edit: My short poll is 300 and my long poll is 1800, well withing the 25,000 limit!!

I ended up upgrading my package to ensure this doesn't happen again, as the weatherbit stats are used heavily in irrigation, especially for some delicate plants that need to be watered during the day! One curiosity. At debug level I get the following message four times every two seconds endlessly: DEBUG Controller:start: *** Waiting for all nodes to be added As far as I can tell, all nodes are there! Any ideas or should I just ignore it? Thanks!

That was helpful, it gave me the URL's that are failing, now it's a 429 (too many requests in a given amount of time) which is weird, since this was an API key that had not been used at all today. I'll just let it sit in the stopped state and try it later/tomorrow. Thanks for your quick response!!

So I swapped it with an API key I have that hasn't been used at all today, changed my polling to only have 48 calls a day (seems the limit is 50), but I'm still having issues: (Also getting 4 lines of duplicates for each message?) 2023-05-31 13:19:09,776 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-31 13:19:09,776 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-31 13:19:09,776 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-31 13:19:09,776 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 10] 2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 10] 2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 10] 2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 10] 2023-05-31 13:19:09,779 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-05-31 13:19:09,779 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-05-31 13:19:09,779 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-05-31 13:19:09,779 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-05-31 13:19:09,780 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-31 13:19:09,780 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-31 13:19:09,780 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-31 13:19:09,780 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}} 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}} 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}} 2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}} 2023-05-31 13:19:09,782 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key 2023-05-31 13:19:09,782 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key 2023-05-31 13:19:09,782 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key 2023-05-31 13:19:09,782 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key 2023-05-31 13:19:09,789 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-31 13:19:09,789 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-31 13:19:09,789 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-31 13:19:09,789 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-31 13:19:09,790 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 - MID: 2 Result: 0 2023-05-31 13:19:09,790 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 - MID: 2 Result: 0 2023-05-31 13:19:09,790 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 - MID: 2 Result: 0 2023-05-31 13:19:09,790 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 - MID: 2 Result: 0 2023-05-31 13:19:09,833 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-31 13:19:09,833 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-31 13:19:09,833 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-31 13:19:09,833 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherBit Weather(controller) [None] 2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherBit Weather(controller) [None] 2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherBit Weather(controller) [None] 2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherBit Weather(controller) [None] 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for current 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for current 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for current 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for current 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 13:19:14,621 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 13:19:23,381 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 13:19:23,384 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,384 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,384 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily 2023-05-31 13:19:23,384 Thread-3 udi_interface ERROR query:_get_weather_data: HTTP request failed for forecast/daily I've attached my config, I can't quite figure out what's wrong? Thanks again!

Ahhhhh, okay - thanks for your help!!

Hello, Have been using the PG2 version of Weatherbit for quite some time now....I noticed today it stopped updating with the above error message. I bought the PG3 module and installed it, but am still getting this message (and nothing updating) as per below: 2023-05-31 12:03:41,520 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 12:03:41,520 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response. 2023-05-31 12:03:49,796 Thread-3 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 12:03:49,796 Thread-3 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 12:03:51,220 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. 2023-05-31 12:03:51,220 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response. Not sure if this is just a weatherbit outage, or if I'm doing something wrong? I have set all the parameters, and in PG2 they have been set for more than a year (so couldn't have been wrong). Thanks!

Will do, thanks!

I had the Kasa node server running perfectly on polisy (PG3). Since upgrading: New nodes are not appearing within Kasa Some old nodes are appearing offline and/or have incomplete information and/or are showing an old IP address I have removed and reinstalled the nodeserver, at which point only the controller is populated in eisy, not child nodes, and in PG3 there are no child nodes populated either after restoring a backup of PG3 and eisy to the state they were at when it was migrated, back to the original - some nodes are offline, some have incomplete info, etc. The log shows various errors, such as: 2023-05-17 13:39:55,488 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed 9c53229e0811.runCmd(DON) Communication error on system:set_relay_state Traceback (most recent call last): File "/usr/local/lib/python3.9/asyncio/streams.py", line 52, in open_connection transport, _ = await loop.create_connection( File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1050, in create_connection sock = await self._connect_sock( File "/usr/local/lib/python3.9/asyncio/base_events.py", line 961, in _connect_sock await self.sock_connect(sock, address) File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 500, in sock_connect return await fut asyncio.exceptions.CancelledError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/asyncio/tasks.py", line 490, in wait_for return fut.result() asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/protocol.py", line 131, in _query await self._connect(timeout) File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/protocol.py", line 81, in _connect self.reader, self.writer = await asyncio.wait_for(task, timeout=timeout) File "/usr/local/lib/python3.9/asyncio/tasks.py", line 492, in wait_for raise exceptions.TimeoutError() from exc asyncio.exceptions.TimeoutError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/smartdevice.py", line 251, in _query_helper response = await self.protocol.query(request=request) File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/protocol.py", line 73, in query return await self._query(request, retry_count, timeout) File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/protocol.py", line 148, in _query raise SmartDeviceException( kasa.exceptions.SmartDeviceException: Unable to connect to the device: 10.214.126.99: The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 889, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/udi_interface/node.py", line 166, in runCmd fun(self, command) File "/var/polyglot/pg3/ns/0021b9026524_12/nodes/SmartPlugNode.py", line 40, in cmd_set_on super().cmd_set_on(command) File "/var/polyglot/pg3/ns/0021b9026524_12/nodes/SmartDeviceNode.py", line 334, in cmd_set_on self.set_on() File "/var/polyglot/pg3/ns/0021b9026524_12/nodes/SmartDeviceNode.py", line 164, in set_on res = fut.result() File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 446, in result return self.__get_result() File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result raise self._exception File "/var/polyglot/pg3/ns/0021b9026524_12/nodes/SmartDeviceNode.py", line 169, in set_on_a await self.dev.turn_on() File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/smartplug.py", line 58, in turn_on return await self._query_helper("system", "set_relay_state", {"state": 1}) File "/var/polyglot/pg3/ns/0021b9026524_12/.local/lib/python3.9/site-packages/kasa/smartdevice.py", line 253, in _query_helper raise SmartDeviceException(f"Communication error on {target}:{cmd}") from ex kasa.exceptions.SmartDeviceException: Communication error on system:set_relay_state After restarting, the following occurs: 2023-05-17 13:39:13,465 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartDimmer', 'name': 'Driveway Overhead', 'host': '10.214.126.180', 'mac': '34:60:F9:F5:7A:D3', 'model': 'KP405(US)', 'address': '3460f9f57ad3', 'emeter': False, 'id': ''} 2023-05-17 13:39:13,466 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse', 'host': '10.214.126.176', 'mac': '10:27:F5:9C:5D:0D', 'model': 'KP115(US)', 'address': '1027f59c5d0d', 'id': ''} 2023-05-17 13:39:13,467 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Polisy2', 'host': '10.214.126.184', 'mac': 'B4:B0:24:E0:E2:82', 'model': 'HS103(US)', 'address': 'b4b024e0e282', 'id': ''} 2023-05-17 13:39:13,468 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Butler Pantry', 'host': '10.214.126.178', 'mac': '1C:61:B4:B0:B3:9B', 'model': 'HS200(US)', 'address': '1c61b4b0b39b', 'id': ''} 2023-05-17 13:39:13,469 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Pi', 'host': '10.214.126.181', 'mac': 'B4:B0:24:E0:F0:89', 'model': 'HS103(US)', 'address': 'b4b024e0f089', 'id': ''} 2023-05-17 13:39:13,469 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse fan', 'host': '10.214.126.99', 'mac': '9C:53:22:9E:08:11', 'model': 'HS103(US)', 'address': '9c53229e0811', 'id': 'SmartPlug_NN'} 2023-05-17 13:39:29,679 Thread-62 udi_interface WARNING SmartDeviceNode:handler_poll: greenhouse fan: Node not ready to poll, must be disconnected or slow to respond? 2023-05-17 13:39:35,455 Thread-8 udi_interface ERROR SmartDeviceNode:connect_a: greenhouse fan: Unable to update device 10.214.126.99 will try again later: res=False 2023-05-17 13:39:55,488 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed 9c53229e0811.runCmd(DON) Communication error on system:set_relay_state These are all devices online in the Kasa app. 10.214.126.99 is not the correct IP address for greenhouse fan, it should be 189, but it's not updating. Hasn't been 99 in several weeks. After restarting, all nodes disappear, and the following: 2023-05-17 13:49:03,930 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-17 13:49:03,930 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-17 13:49:03,994 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 12] 2023-05-17 13:49:03,994 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 12] 2023-05-17 13:49:03,995 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-05-17 13:49:03,995 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-05-17 13:49:03,995 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-17 13:49:03,995 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.0.21', 'requestId': False}} 2023-05-17 13:49:03,996 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.0.21', 'requestId': False}} 2023-05-17 13:49:03,998 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_12.cert 0021b9026524_12.key 2023-05-17 13:49:03,998 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026524_12.cert 0021b9026524_12.key 2023-05-17 13:49:04,005 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-17 13:49:04,005 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-17 13:49:04,005 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_12 - MID: 2 Result: 0 2023-05-17 13:49:04,005 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_12 - MID: 2 Result: 0 2023-05-17 13:49:04,048 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-17 13:49:04,048 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-17 13:49:07,043 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2023-05-17 13:49:07,043 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2023-05-17 13:49:07,044 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2023-05-17 13:49:07,044 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2023-05-17 13:49:17,360 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartDimmer', 'name': 'Driveway Overhead', 'host': '10.214.126.180', 'mac': '34:60:F9:F5:7A:D3', 'model': 'KP405(US)', 'address': '3460f9f57ad3', 'emeter': False, 'id': ''} 2023-05-17 13:49:17,360 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartDimmer', 'name': 'Driveway Overhead', 'host': '10.214.126.180', 'mac': '34:60:F9:F5:7A:D3', 'model': 'KP405(US)', 'address': '3460f9f57ad3', 'emeter': False, 'id': ''} 2023-05-17 13:49:17,361 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse', 'host': '10.214.126.176', 'mac': '10:27:F5:9C:5D:0D', 'model': 'KP115(US)', 'address': '1027f59c5d0d', 'id': ''} 2023-05-17 13:49:17,361 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse', 'host': '10.214.126.176', 'mac': '10:27:F5:9C:5D:0D', 'model': 'KP115(US)', 'address': '1027f59c5d0d', 'id': ''} 2023-05-17 13:49:17,362 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Polisy2', 'host': '10.214.126.184', 'mac': 'B4:B0:24:E0:E2:82', 'model': 'HS103(US)', 'address': 'b4b024e0e282', 'id': ''} 2023-05-17 13:49:17,362 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Polisy2', 'host': '10.214.126.184', 'mac': 'B4:B0:24:E0:E2:82', 'model': 'HS103(US)', 'address': 'b4b024e0e282', 'id': ''} 2023-05-17 13:49:17,363 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Butler Pantry', 'host': '10.214.126.178', 'mac': '1C:61:B4:B0:B3:9B', 'model': 'HS200(US)', 'address': '1c61b4b0b39b', 'id': ''} 2023-05-17 13:49:17,363 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Butler Pantry', 'host': '10.214.126.178', 'mac': '1C:61:B4:B0:B3:9B', 'model': 'HS200(US)', 'address': '1c61b4b0b39b', 'id': ''} 2023-05-17 13:49:17,364 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Pi', 'host': '10.214.126.181', 'mac': 'B4:B0:24:E0:F0:89', 'model': 'HS103(US)', 'address': 'b4b024e0f089', 'id': ''} 2023-05-17 13:49:17,364 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'Pi', 'host': '10.214.126.181', 'mac': 'B4:B0:24:E0:F0:89', 'model': 'HS103(US)', 'address': 'b4b024e0f089', 'id': ''} 2023-05-17 13:49:17,364 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse fan', 'host': '10.214.126.99', 'mac': '9C:53:22:9E:08:11', 'model': 'HS103(US)', 'address': '9c53229e0811', 'id': 'SmartPlug_NN'} 2023-05-17 13:49:17,364 Thread-8 udi_interface WARNING Controller:_discover: Adding previously known device that didn't respond to discover: {'type': 'SmartPlug', 'name': 'greenhouse fan', 'host': '10.214.126.99', 'mac': '9C:53:22:9E:08:11', 'model': 'HS103(US)', 'address': '9c53229e0811', 'id': 'SmartPlug_NN'} 2023-05-17 13:49:33,520 Thread-62 udi_interface WARNING SmartDeviceNode:handler_poll: greenhouse fan: Node not ready to poll, must be disconnected or slow to respond? 2023-05-17 13:49:33,520 Thread-62 udi_interface WARNING SmartDeviceNode:handler_poll: greenhouse fan: Node not ready to poll, must be disconnected or slow to respond? 2023-05-17 13:49:39,421 Thread-8 udi_interface ERROR SmartDeviceNode:connect_a: greenhouse fan: Unable to update device 10.214.126.99 will try again later: res=False 2023-05-17 13:49:39,421 Thread-8 udi_interface ERROR SmartDeviceNode:connect_a: greenhouse fan: Unable to update device 10.214.126.99 will try again later: res=False 2023-05-17 13:50:03,550 Thread-69 udi_interface WARNING SmartDeviceNode:handler_poll: greenhouse fan: Node is now ready to poll 2023-05-17 13:50:03,550 Thread-69 udi_interface WARNING SmartDeviceNode:handler_poll: greenhouse fan: Node is now ready to poll All of the nodes other than greenhouse fan do respond even though they have disappeared in PG3 and it says they didn't respond to discover. The fan which is still the wrong IP does not respond. And no new nodes I've added to Kasa appear.... This is a lot I know, I can provide specific actions and associated logs if needed. Thanks! Edit: I restored everything from backups from the migration day, did another migrate on PG3x, unplugged and plugged in all the Kasa devices, and the existing ones seem to be working mostly now, but still not seeing anything I've added since the eisy migration.

Hi...migrating from a Polisy with the Zooz dongle to the ZMatter board. The plugged in Z-Wave devices (various) and door locks (Kwikset) worked fine. However, not a single motion sensor (Zooz ZSE-09, Dome DMMS-1) or leak detector (Ecolink FLF-ZWAVE5-ECO) would interview after many, many attempts and bringing the devices directly next to Polisy. (Operating on 5.5.6) I tried reducing speed, no help. At this point I've rolled back. Has anyone had any success with any of these devices? Any suggestions? I have 8 of those motion detectors and 3 of the leak detectors. Also I saw this asked in another post but there was no reply, is there no way to see the routing info any longer? Thanks... Edit: Realizing now that I probably should have captured ZWAY.LOG to provide here. 🤦‍♂️ I'll go back and do that...

Did you have battery powered devices and if so, how did they go?

Yeah, door locks are a little different than things like motion detectors....door locks can generally be queried and woken up remotely. What I'm concerned about is things like motion, water, etc., when IoX can't query them during the migration if they just go away or if they can be woken up later and manually interviewed.

I've seen mixed comments on this....what happens to battery powered devices upon the migration when IoX can't interview them? Do they disappear, or go into a pending state? This thread has people saying both. Haven't clicked the button yet as I have 40+ battery powered z-wave devices!

Apologies if this has been covered, I could only find speculation... Given the uncertainly of when a z-wave migration script from Zooz to ZMatter will be available, will the Zooz USB stick work with eisy, or will z-wave support on eisy be 100% dependent on the ZMatter board? (Meaning if we're waiting on a script to migrate, we won't be able to switch to eisy when it ships?) Thanks!

Sorry, I was referring to this line on the pre-order page:

Just curious about the "Want a discount? Become a member!" tag. I don't see any actual instructions or what the discount is. I tried logging in through the ISY portal but nothing changed, and nothing in that line of text is clickable. I have a 994 pro, a polisy, and a zooz 700. Not sure what this is referring to unless it's the zooz stick discount? Apologies if I'm missing something obvious!

I have one that triggers pretty much every time we have rain (it switches on a wall fan in the basement), but nothing nearly that often. That said, I've had that for maybe two years and have yet to change the battery.

I have several Ecolink Zwave Plus Flood & Freeze Sensor, White (FLF-ZWAVE5-ECO) and love them. They come with a remote probe, and battery life is great. I had tried several other remote sensor water detectors, and this one by far works the best. (Available on Amazon.)

Ha, I never even realized that was an option. Definitely more usable than direct https remoting in, for whatever reason. Thanks!!

Just wondering if anyone ever figured out a way to reverse proxy the SOAP subscription. I set up an Apache reverse SSL proxy to offload TLS as it's basically unusable remotely before realizing this limitation. The proxy works fantastic and speeds it up to non-SSL speeds, but obviously fails at "Starting subscription..."

I have a few ZOOZ 4-in-1 multisensors, and was having intermittent problems with one of them. When doing a sync it always failed, so I eventually decided to try removing and re-adding it. Mistake...it adds successfully but doesn't have near the number of nodes it should including, most importantly, motion. It adds Notify, Tamper, and Multilevel, and is missing Binary, Glass Break, Intrusion, Low Battery, Motion, and Tamper Code. I left nodes unfrozen in ISY hoping when it detected motion it would add the node, but it does not. It changes the state of the binary node, but never adds motion. Not positive if this is a z-wave beta dongle issue or a 5.0.13A issue, but figured I'd post over here. Log attached... ZOOZ 4-in-1 Multisensor.txt

Have to say, after reorienting the ISY I've had no signal strength issues. Everything is working quite well! Also, is a backup supposed to be much faster now than on the old dongle? Just want to make sure that's expected and it is indeed working...

Agree with the above - I had an external antenna on the old board and definitely had better range.

I have a Utilitech flood alarm that had been previously working at one point. I noticed that only its battery level was populating, not the status, so I attempted to synchronize a few times and it was of no help. I set it off by actually wetting the probe, and still nothing for the ISY. I tried repairing links, but it always came back with writing 0 bytes. For lack of anything better to try, I excluded it and reincluded it. It is only showing the battery level node, no status node, and it looks as though it's not actually writing any links to the device (log below). I literally picked the device up and was standing next to the ISY when doing this...I tried 3-4 times, all with the same result. I did try setting it off for the heck of it and as expected, no acknowledgement by ISY. To be honest I'm not positive if it stopped working with 5.13 or with the z-wave 500 series dongle. It definitely hasn't had a status since the dongle upgrade, but it was so close to the 5.13 update that I never checked between the two to see if it was working (I just assumed it was). Edit: This log below is 5.0.13A Anyway, log below... Tue 07/17/2018 04:06:27 PM : [ZWAVE-TX-NR ] [0105004AC1ED9C] REQ ZW_ADD_NODE_TO_NETWORK Tue 07/17/2018 04:06:27 PM : [UZW-CMD 1 ] Start Include Tue 07/17/2018 04:06:27 PM : Listening for Z-Wave devices to add to the network Tue 07/17/2018 04:06:29 PM : Z-Wave device detected, retrieving info 2 Tue 07/17/2018 04:06:30 PM : Z-Wave device detected, retrieving info 3 Tue 07/17/2018 04:06:42 PM : Z-Wave device detected, retrieving info 5 Tue 07/17/2018 04:06:42 PM : [ZWAVE-TX ] [0105004A85EEDB] REQ ZW_ADD_NODE_TO_NETWORK Tue 07/17/2018 04:06:42 PM : Adding Z-Wave devices stopped Tue 07/17/2018 04:06:42 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Tue 07/17/2018 04:06:42 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Tue 07/17/2018 04:06:43 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Tue 07/17/2018 04:06:43 PM : Device 81 of type 4.161.2 included into Z-Wave network Tue 07/17/2018 04:06:43 PM : [ZWAVE-TX ] [72/04] CC=0x72 cmd=0x04 [] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:43 PM : [ZWAVE-RX ] [72/05] CC=0x72 cmd=0x05 [0060000B0001] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:43 PM : [ZWAVE-TX ] [9C/03] Sensor Alarm Supported Get ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:43 PM : [ZWAVE-RX ] [9C/04] Sensor Alarm Supported Report[0x01] 0x20 cmd=0x04 [0120] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:43 PM : Adding ISY node(s) for new Z-Wave device 81 type 4.161.2 Tue 07/17/2018 04:06:43 PM : [ZWAVE-TX ZW081_1] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:43 PM : [ZWAVE-RX ZW081_1] [85/06] Assoc Groupings Report supported=0x02 ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:44 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:44 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x01 max=0x01 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:44 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x02 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:44 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x02 max=0x03 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:44 PM : Adding additional nodes for new Z-Wave device 81 Tue 07/17/2018 04:06:44 PM : ...addNodes(uid=81,VERSION,cc=134,ver=0,sec=F) Tue 07/17/2018 04:06:44 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [86] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:45 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [8601] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:45 PM : ...addNodes(uid=81,MANUFACTURER_SPECIFIC,cc=114,ver=0,sec=F) Tue 07/17/2018 04:06:45 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [72] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:45 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [7201] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:45 PM : ...addNodes(uid=81,ASSOCIATION,cc=133,ver=0,sec=F) Tue 07/17/2018 04:06:45 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [85] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:45 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [8502] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:45 PM : ...addNodes(uid=81,WAKE_UP,cc=132,ver=0,sec=F) Tue 07/17/2018 04:06:45 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [84] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:46 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [8402] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:46 PM : ...addNodes(uid=81,BATTERY,cc=128,ver=0,sec=F) Tue 07/17/2018 04:06:46 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [80] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:51 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [80] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:52 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [8001] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:52 PM : [ZWAVE-TX ZW081_1] [80/02] Battery Get ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:53 PM : [ZWAVE-RX ZW081_1] [80/03] Battery Report level=0x64 ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:06:53 PM : ...addNodes(uid=81,CONFIGURATION,cc=112,ver=0,sec=F) Tue 07/17/2018 04:06:53 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [70] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:06:59 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [70] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:00 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [7001] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:00 PM : ...addNodes(uid=81,SENSOR_ALARM,cc=156,ver=0,sec=F) Tue 07/17/2018 04:07:00 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [9C] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:01 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [9C01] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:01 PM : ...addNodes(uid=81,BASIC,cc=32,ver=0,sec=F) Tue 07/17/2018 04:07:01 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [20] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:01 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [2001] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:01 PM : ...addNodes(uid=81,NOTIFICATION,cc=113,ver=0,sec=F) Tue 07/17/2018 04:07:01 PM : [ZWAVE-TX ZW081_1] [86/13] CC=0x86 cmd=0x13 [71] ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:02 PM : [ZWAVE-RX ZW081_1] [86/14] CC=0x86 cmd=0x14 [7101] ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:03 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:03 PM : [UZW-CMD 45 ] Get NodeDef : ZW081_1 Tue 07/17/2018 04:07:03 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x01 max=0x01 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:03 PM : [ZWAVE-TX ZW081_1] [85/01] Assoc Set grp=0x01 nodes=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:03 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:03 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x01 max=0x01 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:03 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x02 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:04 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x02 max=0x03 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:04 PM : [ZWAVE-TX ZW081_1] [85/01] Assoc Set grp=0x02 nodes=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:05 PM : [ZWAVE-TX ZW081_1] [85/02] Assoc Get grp=0x02 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:05 PM : [ZWAVE-RX ZW081_1] [85/03] Assoc Report grp=0x02 max=0x03 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:05 PM : Initializing ISY as wakeup target for new Z-Wave device 81.0 Tue 07/17/2018 04:07:05 PM : [ZWAVE-TX ZW081_1] [84/05] Wakeup Interval Get ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:05 PM : [ZWAVE-RX ZW081_1] [84/06] Wakeup Report interval=3600 seconds, notify uid=0xFF ACK,AUTO,EXPLORE From=0x51 Tue 07/17/2018 04:07:05 PM : [ZWAVE-INIT 81] Assigning Wakeup to ISY (id=1), Interval 3600 seconds Tue 07/17/2018 04:07:05 PM : [ZWAVE-TX ZW081_1] [84/04] Wakeup Set interval=3600 seconds, notify uid=0x01 ACK,AUTO,EXPLORE To=0x51 Tue 07/17/2018 04:07:08 PM : [D2D EVENT ] Event [ZW081_1] [BATLVL] [100] uom=51 prec=0 Tue 07/17/2018 04:07:08 PM : [ ZW081_1] BATLVL 100 (uom=51 prec=0) Tue 07/17/2018 04:07:08 PM : [All ] Writing 0 bytes to devices Tue 07/17/2018 04:07:09 PM : [All ] Writing 0 bytes to devices

After a few days now, reliability is definitely lagging behind the old dongle and external antenna. Devices that were 95%+ reliable are now more like 70-80%. This includes two motion sensors that are one floor directly above the ISY on the ceiling, with a repeater plugged in at ground level. And they do indeed show both the repeater and the ISY as neighbors. They fairly regularly miss on or off actions. I also have a series of Enerwave ceiling mounted motion PIR's that seem to refuse to work at all through repeaters. I suspect their neighbors got blown away during the original heal I did, and I cannot get them back. When I do a restore links on them they show the green indicator of waiting to write...if I then bring one close to the ISY, wake it up, and write changes, ISY immediately puts it back to sleep with 'no work pending'. I haven't tried updating to 5.0.13a yet, will do so this morning. These motions aren't critical as they were mostly replaced with the Dome sensors a while back when support for them was wonky, but nonetheless something to report. (Side noe, 'control' is not available for them in programs any longer either - I think that disappeared a build or two ago. Programs that had 'control' still have the line and it works, but if I try to update/change it, it's no longer available - only status. These report as binary devices.)

Two Kwikset locks here, no issues after the upgrade - statuses are being reported, no errors in the log associated with them (at least that I've noticed) and they are reliably controllable.