gklimo

Sorry to hear my outcome didn't work in your situation. Possibly one of the bulleted items listed in my original post at the top of this thread allowed mine to work. For example, my installing the Development Packages via the Admin Console might be related. Unfortunately, I've since discovered I can only turn my dimmable Kasa HS220 switches on and off from within my eisy. Kasa dimming control doesn't seem to work using the Kasa Beta Node Server. Hopefully that gets resolved. However, full Kasa switch control works just fine from within Home Assistant, including dimming. As a result, I'll use native Home Assistant Automations for my Kasa devices and continue to use eisy Network Resources to externally control Home Assistant via its API as needed. The majority of my environment is Insteon based, which has been rock solid. As a result, I've been a long time ISY then Polisy and now eisy user. Best of luck. I hope to see an update with some success.

RESOLVED I switched to the Non-production Store within the PG3x Plugin Store and installed the 3.2.4 / Standard [Beta] version of the Kasa Node Server to the same slot previously used. The Key section within the Node Server Custom Configuration Parameters then offered the following entries. user password I entered my Kasa account username (case sensitive) as the user Key Value and my Kasa account password (case sensitive) as the password Key Value. I restarted the Kasa Node Server and relaunched the Admin Console after giving the Node Server a chance to discover the Kasa devices. All of my Kasa HS220 and HS200 switches were successfully found. They now appear in my eisy Admin Console node list and can be controlled.

Would appreciate some guidance on the following. Thanks in advance, I recently purchased and installed the TP-Link Kasa Node Server on my eisy. I'm running the current 3.1.4 version. My eisy is running IoX Version 5.9.1 with PG3x Version 3.3.18. Unfortunately, the Kasa Node Server is not discovering any of my Kasa switches. I currently have two Kasa HS220 switches that are Hardware Version 3.26 and Firmware Version 1.1.1. I also currently have two Kasa HS200 switches that are Hardware Version 5.26 and Firmware Version 1.0.3. These switches work from other resources on my network. They work fine from the Kasa app and also work fine from within Home Assistant. Since Discovery was not finding the switches, I performed the following steps without success. Assigned a static IP address to each Kasa switch. Increased the discover_timeout significantly. Installed the eisy Development Packages via the Admin Console (as mentioned by some). Manually added each switch IP into the Node Server Configuration section. Stopped and restarted the Node Server numerous times. Exited and relaunched the Admin Console numerous times. Invoked Reinstall all Plugins from within PG3x. Rebooted the eisy. Unfortunately, the eisy Admin Console still only shows the Kasa Controller node. No switches appear. The Kasa Node Server also reports only one node (Kasa Controller) with NodeServer Online within PG3x. Since the Kasa HS220 (US) is listed as supported, I hoped to see at least that switch model appear. After attempting to manually define each switch IP (since discovery was not finding them), the logs observed indicate "Unsupported device" as follows. Any suggestions on how to get things to work? Line 5499: 2025-05-13 07:22:53.398 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Unsupported device 192.168.1.231: {'result': {'device_id': '2072eb696f928b3b0209fd2439cfb420', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS220(US)', 'ip': '192.168.1.231', 'mac': '8C-90-2D-80-9F-FC', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.231 Line 5501: 2025-05-13 07:22:53.416 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Unsupported device 192.168.1.241: {'result': {'device_id': '6eb0794588d4ee5eb5f0e3c050b15789', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS200(US)', 'ip': '192.168.1.241', 'mac': 'DC-62-79-9A-27-F2', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.241 Line 5503: 2025-05-13 07:22:53.424 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Unsupported device 192.168.1.210: {'result': {'device_id': '29fa577f06cfa6d09781e25548b35471', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS220(US)', 'ip': '192.168.1.210', 'mac': '8C-90-2D-80-A7-A0', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.210 Line 5505: 2025-05-13 07:22:53.432 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Unsupported device 192.168.1.220: {'result': {'device_id': '177b54ce12e07e4380c01f455eac6cd5', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS200(US)', 'ip': '192.168.1.220', 'mac': 'DC-62-79-9A-11-9F', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.220

I installed an Insteon Heavy Duty 120-277V Load Controller Assembly 1470 from Innovative Home Systems to programmatically control when my pool filter runs. It works great. Mine has an oversized 40AMP relay, which should last a very long time. I also purchased the optional switch cover. https://innovativehomesys.com/products/wifi-heavy-duty-120-277-volt-40-amp-automated-load-transfer-assembly-1470 I chose the Insteon version since my Insteon environment has been rock solid for many years. But it's also available in Wi-Fi, Z-Wave and HomeKit versions if preferred. Here's a couple of pictures for reference.

I realize this original post is somewhat dated. But wanted to respond to "Can I use an old Polisy for anything? The hard drive went corrupt and I moved to Eisy. Can I put another operating system on it?". The following link provides an overview of how I successfully installed Debian 12.10.0 on my old Polisy hardware.

DreamerI90, I suspect the hardware is still good and the data on the internal mSATA is somehow corrupted. If my suspicion is true, you may be able to resurrect your Polisy Pro hardware and use it for other purposes as I did. If that's of interest, please see the link that follows.

FYI; I noticed the same 2-hour difference in the PG3x v3.2.10 logs and performed a subsequent full reboot of my Polisy. The PG3x log time stamps are still 2-hours earlier than the system time displayed within the Admin Console.

Agree, ZMatter is probably the best way to go. But was hoping I could continue to use what already worked on Polisy. I purchased the Zooz stick based on it being the suggested compatible brand. Thanks

Correct on both. Both the Firmware and UI on the Help | About screen report IoX v5.5.5. I was sure to delete the Java cache after each firmware update prior to accessing IoX Launcher. I also did not select the Migrate to ZMatter button observed prior to restoring the backup from the ISY994i. I assume it's no longer visible since Polisy is no longer detecting the Zooz Z-Wave stick.

I'm a long time ISY user with many INSTEON devices and some Z-Wave. The ISY994i-IR-PRO I've used has a Z-Wave 500 Series Module within. I also have a Polisy PRO (5200), currently running IoX v5.5.5. My Polisy was mainly used to host Node Servers for the ISY994i. But it also had a Zooz USB 700 Series Z-Wave Plus S2 Stick ZST10 700 installed. IoX on Polisy supported a handful of Z-Wave devices by way of the Zooz Z-Wave USB stick. The Zooz stick worked fine on Polisy with IoX v5.5.x until I fully migrated my ISY994i to Polisy. Today, I migrated my ISY994i-IR-PRO configuration to ISY on Polisy. A current backup from my ISY994i was created. A new Serial PLM was connected to Polisy. So Polisy now had the new Serial PLM along with the Zooz USB 700 Series Z-Wave Plus S2 Stick ZST10 700 already plugged in. I removed power from the ISY994i and unplugged its PLM from the AC outlet. I then restored the current ISY994i backup to Polisy, checked both the INSTEON Support and Z-Wave Support check boxes, and instructed IoX to Restore Modem (PLM). All INSTEON devices and IoX programs appear to be working fine. However, none of the Z-Wave devices that previously worked with IoX on Polisy function. When selecting the Z-Wave menu, it states "ZMatter Z-Wave not responding". I also noticed the Migrate to Zmatter button on the Configuration tab is no longer visible. It previously was. I've rebooted Polisy several times, including removing and restoring power. I've also unplugged and re-plugged the Zooz USB Z-Wave stick, etc. with no change. I even installed a short USB extension cable to make sure the Zooz USB stick is properly connected. I've viewed and monitored /var/isy/FILES/LOG/debug.log, but didn't see anything that seems to be related. I'll likely purchase a ZMatter board for Polisy at some point, but just not yet. For now, I'm hoping this Zooz Z-Wave stick issue can be resolved. I look forward to a response. Thanks