Another problem with no devices found

[bw23198]

I figured I'd start a new thread in case my issue turns out to be different than others.

I installed a new eISY today by backing up my ISY994 and restoring it on eISY.  I was previously using a Raspberry Pi to run PolyGlot 2, and had the Kasa NS installed.  I took the Raspberry Pi offline and have been reinstalling all of my NS within PG3.  So far I've gotten most of them to work.  However, Kasa is throwing the following error in a loop:

2023-12-26 19:38:29,958 MainThread udi_interface      INFO     polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-12-26 19:38:29,958 MainThread udi_interface      INFO     __init__:<module>: UDI interface initializing
2023-12-26 19:38:29,958 MainThread udi_interface      INFO     __init__:<module>: User=0021b9026812_8
2023-12-26 19:38:29,958 MainThread udi_interface      INFO     __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026812_8
2023-12-26 19:38:29,958 MainThread udi_interface      INFO     __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026812_8
2023-12-26 19:38:29,959 MainThread udi_interface      INFO     __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njg6MTIiLCJwcm9maWxlTnVtIjo4LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6IkpGdzhoVGY4VW9aNSohMEkiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNiIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJGcmVlIn0=
2023-12-26 19:38:29,959 MainThread udi_interface      INFO     __init__:<module>: Loading interface module
2023-12-26 19:38:30,003 MainThread udi_interface      INFO     interface:<module>: Loading MQTT module
2023-12-26 19:38:30,450 MainThread udi_interface      INFO     interface:<module>: MQTT module loaded
2023-12-26 19:38:30,674 MainThread udi_interface      INFO     __init__:<module>: Loading udi_interface module
2023-12-26 19:38:30,674 MainThread udi_interface      INFO     __init__:<module>: Loading node module
2023-12-26 19:38:30,675 MainThread udi_interface      INFO     __init__:<module>: Loading custom module
2023-12-26 19:38:30,675 MainThread udi_interface      INFO     __init__:<module>: Loading isy module
2023-12-26 19:38:30,675 MainThread udi_interface      INFO     __init__:<module>: UDI interface initialized
2023-12-26 19:38:30,675 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting...
2023-12-26 19:38:30,677 MainThread udi_interface      ERROR    udi_interface:write: Traceback (most recent call last):
  File "/var/polyglot/pg3/ns/0021b9026812_8/kasa-poly.py", line 12, in <module>
    from nodes import VERSION,Controller
  File "/var/polyglot/pg3/ns/0021b9026812_8/nodes/__init__.py", line 9, in <module>
    from .SmartDeviceNode      import SmartDeviceNode
  File "/var/polyglot/pg3/ns/0021b9026812_8/nodes/SmartDeviceNode.py", line 8, in <module>
    from kasa import SmartDeviceException
ModuleNotFoundError: No module named 'kasa'

I'm running 5.7.1 of eISY and 3.1.4 of Kasa.  I've tried rebooting eISY, deleting/re-installing Kasa, restarting Kasa.  I'm not quite sure what "recently run an update packages so you have the latest release" means.  I looked for 'update packages' but can't seem to find that setting.

Any ideas?

[bw23198]

I found the 'upgrade packages' option.  I'm trying that now and will report back.

[Jimbo.Automates]

Yes, this is the same issue reported and fixed in the other thread. Sorry I misspoke upgrade vs. update. But good you figured it out.

ModuleNotFoundError: No module named 'kasa'

Sent from my Pixel 8 Pro using Tapatalk

[bw23198]

And that fixed it!  The key was to look for that option within the eISY under Configuration | System.  I was looking everywhere in the PolyGlot web interface. 

-Brian

[dblee1950]

Thanks, Brian.  This was very helpful

[dblee1950]

OK, got connected but it doesn't find my devices.  Just starting with TP-link, this is a couple of smartplugs, EP25P4.  Log says:

2023-12-29 10:13:19,184 Thread-12 kasa.discover DEBUG discover:datagram_received: [DISCOVERY] Unsupported device found at 192.168.0.164 << {'result': {'mac': '48:22:54:A2:5F:40', 'tmp_port': [20001], 'hardware_version': '1.2', 'group_name': 'UHJpZGVfQmx1ZmY=', 'need_account_digest': True, 'owner': 'ad7e01492048820889f788af8a048f0b', 'master_device_id': 'cd38fde4457325ab88372467a44194ef', 'ip': '192.168.0.164', 'device_type': 'HOMEWIFISYSTEM', 'role': 'master', 'channel_2g': '4', 'device_model': 'X55', 'device_id': 'cd38fde4457325ab88372467a44194ef', 'group_id': '67f4dcb8697afc57459b1657a28f744f', 'channel_5g': '48', 'factory_default': False}, 'error_code': 0}

 

Does this mean that the smarplugs cannot be used with eisy at this time?  I have some switches coming in in a day or two that are new.  Will this only work with older devices?  thanks

 

[Jimbo.Automates]

7 minutes ago, dblee1950 said:

OK, got connected but it doesn't find my devices.  Just starting with TP-link, this is a couple of smartplugs, EP25P4.  Log says:

2023-12-29 10:13:19,184 Thread-12 kasa.discover DEBUG discover:datagram_received: [DISCOVERY] Unsupported device found at 192.168.0.164 << {'result': {'mac': '48:22:54:A2:5F:40', 'tmp_port': [20001], 'hardware_version': '1.2', 'group_name': 'UHJpZGVfQmx1ZmY=', 'need_account_digest': True, 'owner': 'ad7e01492048820889f788af8a048f0b', 'master_device_id': 'cd38fde4457325ab88372467a44194ef', 'ip': '192.168.0.164', 'device_type': 'HOMEWIFISYSTEM', 'role': 'master', 'channel_2g': '4', 'device_model': 'X55', 'device_id': 'cd38fde4457325ab88372467a44194ef', 'group_id': '67f4dcb8697afc57459b1657a28f744f', 'channel_5g': '48', 'factory_default': False}, 'error_code': 0}

 

Does this mean that the smarplugs cannot be used with eisy at this time?  I have some switches coming in in a day or two that are new.  Will this only work with older devices?  thanks

 

As mentioned in the first paragraph of the README https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md

This nodeserver relies on a mostly undocumented and unofficially supported local API which of course TP-Link could break at any time, and has in the past, but luckily others figure it out.

They have broken it with the newer devices...

And more about TAPO here

https://forum.universal-devices.com/topic/42251-tp-link-kasa-and-tapo-support/#comment-374057

There are people working to try and get this working and progress is being made.  I'm not up-to-date on all the issues, but some of the newer devices support Matter, so hopefully ISY can eventually talk to them directly.

Personally I would not use Kasa for many things, because of these issue, but also because they do not provide real time updates, the node server has to "poll" them for updates.  I like their power strips, light strips, and bulbs, but do not have any switches.

 

[dblee1950]

thanks