Breezyken

I have removed the Kasa trial version(expired) and installed the paid version. Configured according to instructions and it shows connected on admin console. There are no nodes (plugs) shown. Upon restart I recieve the following error: 2024-12-23 11:29:39.536 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 192.168.1.38 trying to connect to 192.168.1.38 Discover is not working for the plug nodes. How do I get them installed? I disabled my firewall and I did another restart and discover in PG3 and get the following error: 12/23/2024, 11:35:25 [pg3] warn: Request for customtypedparams. Not found in database Also, I have set change_node_names to true. The existing names have been picked up from the app on my phone. Is this a problem/conflict? Looking for answers. Thanks!

I have a Kasa HS300 6 outlet plug strip and I want to install the node server on my eisy. I previously had the trial version of the node, so I deleted that, purchased the current paid version and installed that. Going to the admin console I selected Kasa, but was unsure how to proceed from there. My choices are ADD NODE or ADD ALL NODES. Selecting Add Node gives me a list of Kasa devices but no model numbers. I might guess at any of the first four, but then I get a window asking for Name(whose name?), Node Address, Primary Node Address(what is this?), so I stopped there. So far the Kasa Controller shows up in the admin console Device list, but no outlets. Searching the wiki's etc. I found one that said all this should be automatic and #1 do NOT open the Node Servers option. General info about installing node servers does not help. I believe I am up to date with Kasa 3.1.4, PG3x 3.2.17 & IoX 5.7.1. I've been at this for over three hours now, and it's very frustrating. I just stopped the server and will wait for help. LOG Follows: 2024-12-22 12:42:29.797 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: User=0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njg6MzciLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6Ik0/VGwqSndEZ2tOJkN4V2EiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-12-22 12:42:29.798 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-12-22 12:42:29.834 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-12-22 12:42:30.334 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-12-22 12:42:30.558 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-12-22 12:42:30.559 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2024-12-22 12:42:30.560 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-12-22 12:42:30.560 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-12-22 12:42:30.659 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 4] 2024-12-22 12:42:30.659 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.38', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2024-12-22 12:42:30.660 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2024-12-22 12:42:30.660 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2024-12-22 12:42:30.660 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026837_4.cert key: 0021b9026837_4.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-12-22 12:42:30.660 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2024-12-22 12:42:30.660 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2024-12-22 12:42:30.661 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds. 2024-12-22 12:42:30.710 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success 2024-12-22 12:42:30.710 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:68:37_4 - MID: 2 Result: MQTTErrorCode.MQTT_ERR_SUCCESS 2024-12-22 12:42:30.752 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0'] 2024-12-22 12:42:30.836 Thread-5 udi_interface WARNING Controller:handler_data: No custom data 2024-12-22 12:42:30.980 Thread-11 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded params=None data=True... cnt=600 2024-12-22 12:42:32.152 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a14343 not found in database. 2024-12-22 12:42:32.239 Thread-20 udi_interface WARNING Controller:handler_data: No custom data 2024-12-22 12:42:35.241 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434301 not found in database. 2024-12-22 12:42:35.242 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434302 not found in database. 2024-12-22 12:42:35.242 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434303 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434304 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434305 not found in database. 2024-12-22 12:42:35.243 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434306 not found in database. 2024-12-22 12:42:35.402 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434301 not found in database. 2024-12-22 12:42:35.403 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434302 not found in database. 2024-12-22 12:42:35.403 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434303 not found in database. 2024-12-22 12:42:35.404 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434304 not found in database. 2024-12-22 12:42:35.404 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434305 not found in database. 2024-12-22 12:42:35.405 Thread-12 udi_interface.interface WARNING interface:db_getNodeDrivers: 5091e3a1434306 not found in database. 2024-12-22 13:09:07.511 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-12-22 13:09:07.511 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: User=0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026837_4 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njg6MzciLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6Ik0/VGwqSndEZ2tOJkN4V2EiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-12-22 13:09:07.512 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-12-22 13:09:07.549 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-12-22 13:09:08.051 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-12-22 13:09:08.277 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-12-22 13:09:08.278 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-12-22 13:09:08.279 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-12-22 13:09:08.353 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 4] 2024-12-22 13:09:08.353 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.38', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2024-12-22 13:09:08.354 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2024-12-22 13:09:08.354 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: tplkasactl not found in database. 2024-12-22 13:09:08.354 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026837_4.cert key: 0021b9026837_4.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-12-22 13:09:08.354 MainThread udi_interface.interface INFO interface:addNode: Adding node Kasa Controller(tplkasactl) [None] 2024-12-22 13:09:08.355 MainThread udi_interface.interface INFO interface:setController: Using node "tplkasactl", driver "ST" for connection status. 2024-12-22 13:09:08.355 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds. 2024-12-22 13:09:08.406 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success 2024-12-22 13:09:08.407 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:68:37_4 - MID: 2 Result: MQTTErrorCode.MQTT_ERR_SUCCESS 2024-12-22 13:09:08.450 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0'] 2024-12-22 13:18:53.241 Thread-203 udi_interface ERROR udi_interface:write: Exception in thread 2024-12-22 13:18:53.241 Thread-203 udi_interface ERROR udi_interface:write: Thread-203 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: : 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2024-12-22 13:18:53.242 Thread-203 udi_interface ERROR udi_interface:write: self.run() 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2024-12-22 13:18:53.243 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 461, in handler_typed_data 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: self.add_manual_devices() 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 140, in add_manual_devices 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: res = future.result() 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 446, in result 2024-12-22 13:18:53.244 Thread-203 udi_interface ERROR udi_interface:write: return self.__get_result() 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: raise self._exception 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026837_4/nodes/Controller.py", line 147, in _add_manual_devices 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: LOGGER.info(f"Adding manual device {mdev['address']}") 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: KeyError 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: : 2024-12-22 13:18:53.245 Thread-203 udi_interface ERROR udi_interface:write: 'address'

And then I created a new account at Resideo.com and I still can't log in to the redirect in API configuration. error shown in attached clip.

I'm having similar problems. I've had a developer account for several years, but my old API did not work. I created a new API, got my Keys, and when I enter my Keys on the azure website and asked to log into Honeywell Home, I'm told my login is incorrect. I'm not sure if this is the same site I use to access my thermostats, but I can log into that site (https://www.mytotalconnectcomfort.com/portal) successfully. Do I need an account on a third site? Attempts to reset my password fail (as others have stated above), saying my email address is unrecognized in the system. I'll stay tuned here to see what develops.

Thanks Bob, that fixed the Daily and Month observations. The log is still showing the same parsing error for the yearly obs. Ken

I have installed the current DavisWeather poly (2.0.1), configured the settings, and loaded all the nodes. However, only the current conditions from the console are displayed. None of the observations data is being filled in. I queried the server with https://api.weatherlink.com/v1/NoaaExt.json?user=<my Station ID>&pass=<my password>&apiToken=<my token> and that returns ALL the data, including Daily, Month, and Yearly (But maybe not enough data to parse?). My configuration parameters were copied directly from the node configuration and pasted into the URL. Why is it not populating on the admin console? My station is a Vantage Pro 2. I don't have a solar radiation sensor. I've attached the first part of the log, but the rest is just repetition of the parse error. I also attached a sanitized response to the API call. DavisWeather Debug Log.txt JSON Message.txt

I just upgraded to EISY and Kasa is one of the first node servers I have installed, although I had WeatherLink running on Raspberry Pi earlier. I have been having similar problems as above with the HS300 power strip, with the admin console showing Kasa connected, but no nodes appeared. I have Iox 5.7.1, Kasa 3.1.4, PG3x 3.2..16, udx ?.? (don't know where to find that one). I finally installed the Dev packages, reinstalled Kasa node server, restarted everything, and the power strip appeared in the admin console, so now it is working fine. Thanks for all the background and answered queries above.

Thanks to everyone that jumped in to solve this mystery. The technique in the YouTube video to start linking revealed that what my old eyes thought was a 40 was actually a 4D. Everything went smoothly once that was corrected. Fri 09/10/2021 12:50:09 PM : Start Insteon Device Linking Mode Fri 09/10/2021 12:50:09 PM : [LNK-BGN ] 02 64 01 00 06 Fri 09/10/2021 12:51:03 PM : [LNK-STAT ] 02 53 M(01) gid=00 4D.4E.13 0124 42 Fri 09/10/2021 12:51:03 PM : [4D.4E.13 00] Linked device type=01.24 fw=42 Fri 09/10/2021 12:51:03 PM : [4D 4E 13 0 ] Added to list of devices to link to ISY Fri 09/10/2021 12:51:03 PM : [LNK-BGN ] 02 64 01 00 06 Thank You

Attached is the diagnostic results of trying to add the 2474d dimmer. It looks like there is no communication to the device. I am using a valid load (2 60 watt incandescent bulbs). Thanks for the links to the Insteon command list and device tables. The Youtube video is helpful and I will check all the details and try the method in the video to establish communication.

Attached is the diagnostic results of trying to add the 2474d dimmer. It looks like there is no communication to the device. I am using a valid load (2 60 watt incandescent bulbs). Thanks for the links to the Insteon command list and device tables. The Youtube video is helpful and I will check all the details and try the method in the video to establish communication.

I am using a compatible load (2 60 watt incandescent bulbs). I have tried both 2474D modules as well as the auto detect function. The error "Cannot determine Insteon Engine" says to me the device has been detected but the software is not correct (and I'm probably wrong. It would be nice if the device type was ordered by part number, but Category and subcat must mean something to someone. Any more thoughts and is there a definition/description of Cat & Subcat? Thanks

I have installed a new 2474D 2-wire dimmer switch but when I try to add it to the ISY994i I receive the error message "Cannot determine Insteon Engine". I know this device is RF only, but there are several dual mode Insteon devices nearby. In the list of Insteon devices the 2474D is described as a "Companion Dimmer'; not sure what that means. Any hints to decrypt the error message and get this linked would be appreciated.

OK, now that makes sense since there is no common reference point between AC ground/neutral and the 12 (20) volt unregulated supply. That can float almost anywhere referenced to "ground". Let's hope these things keep working until a quality interface becomes available.

Now I'm curious where you are measuring the unregulated supply voltage. Are these functioning modules? 330K should have no effect on the voltage measurement. Maybe try using a simple VOM? I'm not adverse to putting a meter on any point in a line powered device, but if I need to use the scope I use an isolation transformer on the device.

There is an isolation boundary separating the AC line from the primary 12 volt supply voltage consisting of T1 and U2, the optical isolator which provides feedback to the switching supply. There is no "ground" on the AC side of the supply where the 4 power diodes are. The 12 volt supply is referenced to the isolated side of the supply, such as the negative sides of C7, C13, and C14, and of course T1. Maybe you are picking up some stray field from T1 and associated high frequency traces. It's been almost four years since I repaired my 2413S PLM V1.B/1351 and it is still going strong!