Jimbo.Automates

The HS300 is one of my test devices and works perfectly with the latest production and beta releases of the plugin. Something on your network is stopping the eisy from seeing that device. Also, as I mentioned you should not have to manually enter any IP addresses for devices if they are all on the same network and you have no network rules in your router stopping them and decent WiFi coverage to the HS300. The "Can't find db_getNodeDrivers" is a result of failure to communicate with the IP address you entered. See the earlier errors. 2024-12-27 16:30:20.160 Thread-11 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 192.168.1.189 trying to connect to 192.168.1.189 2024-12-27 16:30:21.018 Thread-11 (run_forever) udi_interface WARNING SmartDeviceNode:connect_a: SmartStrip 5091E3A14343: Device 192.168.1.189 responding again 2024-12-27 16:30:21.018 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:set_connected: SmartStrip 5091E3A14343: failed: You need to await update() to access the data 2024-12-27 16:30:21.019 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:connect_a: SmartStrip 5091E3A14343: Unable to connect to device 192.168.1.189 will try again later: You need to await update() to access the data 2024-12-27 16:30:23.236 Thread-515 (handler_poll) udi_interface WARNING SmartDeviceNode:handler_poll: SmartStrip 5091E3A14343: Node not ready to poll, must be disconnected or slow to respond? 2024-12-27 16:30:23.723 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:update_a: SmartStrip 5091E3A14343: failed: Unable to query the device 192.168.1.189:9999: [Errno 54] Connection reset by peer

Awesome! Glad its finally working. The new library has the ability to query features supported by the device so I need to do some rework on how I create the node so it properly shows the features it supports, like voltage and current.

Please try 3.2.4

You should not have to add the HS300 manually, it should be auto-discovered if they are on the same network, if you have multiple subnets at your place then you will can add that sub-net to the list on the configuration page and allow discovery across the subnets. If your device is 192.168.1.38 the error says your IoX is not able to see that device so discovery and communication will not work. Something on your network is stopping the IoX from seeing that device. The "warn: Request for customtypedparams" is a PG3 error, so will need info from @bmercier why that is happening. The change_node_names setting should not be any issue. Sent from my Pixel 8 Pro using Tapatalk

@mjrush Thanks for the log package, it showed there was an install error. Please try 3.2.3.

Must have been an install error, please "Download Log Package" and PM it to me.

You should post in the Kasa sub-forum https://forum.universal-devices.com/forum/313-kasa-tp-link/ It looks like you did a "Add Kasa Device" in the configuration page, but didn't enter a address. I'll fix that crash at some point, but if you "Delete" it, "Save Changes" and restart it should clear the error.

I just updated the beta Standard to 3.2.2, @bmercier said if you own the production standard you can install the beta standard. Let me know.

Thanks, I submitted a support ticket Sent from my Pixel 8 Pro using Tapatalk

And if you activate what happens? It should just authorize thru the portal and let you install? Sent from my Pixel 8 Pro using Tapatalk

Those of you trying to install the beta (non-production) version, are you selecting 3.2.2 - Free - Trial? I just tried on my system and it worked as expected.

@bmercier can you check into this and the beta issue as well? Sent from my Pixel 8 Pro using Tapatalk

@mjrush Did you purchase it? It's free so there should be no charge. @bmercier I have the beta version Edition: Free License Type: Trial Recuring: 1 Recuring Period: Month Why does it ask them to "Purchase"? - Jim

No, as I said, the beta is not currently working and I'm traveling so haven't had time to look into it. Also, never move to a beta, just test in a new slot. Sent from my Pixel 8 Pro using Tapatalk

No, as I said, the newer devices do not work with the production plugin. Sent from my Pixel 8 Pro using Tapatalk

The production release doesn't work with new devices as I've mentioned in many posts. The beta should work but there are issues with the install and I'm traveling so haven't been able to debug. Sent from my Pixel 8 Pro using Tapatalk

Are you running the beta version? I thought it wasn't working for anyone.

Sorry guys, I'm traveling for the holidays, will try to check when I get a chance. Sent from my Pixel 8 Pro using Tapatalk

Yes, same issue reported here /topic/44337-elk-plugin-failures-after-reconnect/ I need a download log package from the same day the incident happened. Sent from my Pixel 8 Pro using Tapatalk

No worries, just keep this thread open an let me know if it happens again. Sent from my Pixel 8 Pro using Tapatalk

Please install Kasa plugin beta trial 3.2.2 in a new slot and test. I've only done minimal testing so let me know if you have any issues.

Please try Beta version mentioned here: and post in that thread if you have issues once it can be installed.

Thanks Guys for the HS200 and KP125. The good news is that I have released 3.2.0 to Beta, but the bad news is that it requires an update to the python-kasa library I use. So once that library is released you can test. I'll be heading out of town this week but will keep an eye on it and let you know when you can give it a try. Please do not install this beta for production, there were a lot of changes and I've only done minimal testing.

Thanks, I added a black on to the list since it was cheaper. Personally I don't use many Kasa devices since they only update when polled, not push. Hopefully once matter is all working we can just use their matter supported devices. Sent from my Pixel 8 Pro using Tapatalk

Easiest way is with using a Simple shareable notifications where you use ${sys.node.#.name} ${sys.node.#.GV0} For Physical Status, or this for Logical Status ${sys.node.#.name} ${sys.node.#.ST}