leonpc

Hi Bumbershoot Thanks for pointing out this post. I have tried some of the solutions mentioned in here. I get error message when running these commands. As it is I already had the dev packages installed but tried to install them again just in case those were not updated when upgrading from 5.8.3 to 5.8.4. It goes very quick. I have restarted EISY after that but still no luck.

I was having issues connecting to my Bond devices. While troubleshooting I noticed that Eisy updated to v5.8.4 back in June. I followed the instructions and upgrade to v5.8.4 and now all my bond devices are active and working but I cannot connect to any of the LIFX and Roomba devices. In the PG3 dashboard I see both node servers show as disconnected. Looking at the Lifx log I see the following: 2024-10-20 12:43:39.342 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b90266f4_2/lifx-poly.py", line 10, in <module> 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: import lifxlan 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: : 2024-10-20 12:43:39.343 MainThread udi_interface ERROR udi_interface:write: No module named 'lifxlan' Looking at the Roomba log I see a slightly different message: 2024-10-20 12:46:20.198 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.14 Starting... 2024-10-20 12:46:20.218 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-10-20 12:46:20.218 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b90266f4_5/roomba-poly.py", line 19, in <module> 2024-10-20 12:46:20.219 MainThread udi_interface ERROR udi_interface:write: from roomba import Roomba 2024-10-20 12:46:20.219 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b90266f4_5/roomba.py", line 42, in <module> 2024-10-20 12:46:20.219 MainThread udi_interface ERROR udi_interface:write: from collections import Mapping 2024-10-20 12:46:20.220 MainThread udi_interface ERROR udi_interface:write: ImportError 2024-10-20 12:46:20.220 MainThread udi_interface ERROR udi_interface:write: : 2024-10-20 12:46:20.220 MainThread udi_interface ERROR udi_interface:write: cannot import name 'Mapping' from 'collections' (/usr/local/lib/python3.11/collections/__init__.py) In both cases it is just looping through these messages. I have restarted the eisy and power cycled it. I have reinstalled the plugins for both Lifx and Roomba After the upgrade to v5.8.4, I installed the Developer Packages. still no luck to get these to work. Any ideas would be appreciated

I think I have found the answers to my questions is this excellent post of @Bumbershoot

@gviliunas I have read the various posts from you surrounding the LIFX firmware v3.90. I am a little confused and would like some clarification. In your post it looks like you are saying you should use the serial number of the bulb when setting up the devlist. But elsewhere you say that you should use the MAC address of the bulb. Since you used the documented serial number in the devlist which stopped working with the change that started with the firmware update, it seems like you should be using the MAC address. Am I correct? @xKing when you set up the devlist, what are you looking for? the serial number of the bulb or the MAC address of the bulb? Thanks Leon

Thanks for all the good input... I started down the road to figure this all out and then got pulled into a project at work that has consumed all my time. I have not looked at anything HA related and my wife has been creating a backlog of things to be fixed. Starting today I have some time available and I will go back and setup the devlist.txt. I already assign ip addresses to the lights so that the ip addresses do not change. Thank you @gviliunas and @bigDvette.

@Michel Kohanim When i restart the node server I see the following error: 2024-02-01 16:49:05,629 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2024-02-01 16:49:10,719 Thread-4 udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:39:e8:51 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> Once I get this error none of the LIFX bulbs are discovered and none of the controls work. I have added a devlist.yaml and when I do that it looks like the bulbs are discovered until the last few lines when I get a a series of messages that manual discovery failed. I have now removed the devlist.yaml I am opening a ticket... thanks

Have you found any solution to this. Lifx was working for me until about a week ago... and then it stopped. I have the same errors in my logs and was considering using the devlist.yml but if that does not work... Where t now?

What happens if you only have the eisy? How do i setup the Python dev environment on eisy. Obviously I am missing it in the docs. Thanks

Yes the devices it is complaining about are 4 light bulbs and the switch is off. I can grab a trace with the switch on if it will help.

I have updated IoX to the latest and then restarted the eisy. After that I updated the Kasa module to v3.1.4.. I now am getting an error during startup that discovery is not working. Eventhough the devices are displayed in the ac it is not working. I have tried to update across the board twice and am still seeing the same issue. Kasa_12-21-2023_34154_PM.zip

Thanks @firstone this makes a lot more sense. Now that I understand the intent I see many possibilities on how to use this.

Thanks for all the replies. i have used other ways to set dates around holidays to turn lights on but they all seem to use multiple lines of code. Seeing the Holidays node sever I thought I could simplify things but reading the instructions did not make sense to me. I also looked at the HolidaysGoogle node server but it currently has an issue with connecting the node server to Google. @tlightneThanks this is what I was looking for.. I still have questions how to setup rules and define new holidays but it is a step in the right direction.

Obviously I am missing something but how does this node server work? I would like to use this to do something like the following If 2 weeks before Christmas then Turn on xmas lights But I do not see the holidays mapped. How is this suppose to work?

Yes seeing the same behavior. Can upload logs but you already have 2 sets

Thanks.. will try this now

Do we have any update on this?

Thanks. Let me know if you need anything else from me to help speed up the resolution.

I had the Kasa Node Server installed but added two devices. While adding the devices I named it for a location but decided to change the names of the devices. After the change I stopped and started the NS and the change still did not display. Yes I have the change_node_names parameter set. I then reinstalled the node server from the node store into the same slot. Now the node server does not want to start and in the logs I see the following error scrolling every 10 to 15 seconds: 2023-11-04 15:03:23,799 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-11-04 15:03:23,799 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-11-04 15:03:23,799 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.3 Starting... 2023-11-04 15:03:23,802 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b90266f4_15/kasa-poly.py", line 12, in <module> from nodes import VERSION,Controller File "/var/polyglot/pg3/ns/0021b90266f4_15/nodes/__init__.py", line 9, in <module> from .SmartDeviceNode import SmartDeviceNode File "/var/polyglot/pg3/ns/0021b90266f4_15/nodes/SmartDeviceNode.py", line 8, in <module> from kasa import SmartDeviceException ModuleNotFoundError: No module named 'kasa' 2023-11-04 15:03:25,013 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-11-04 15:03:25,014 MainThread udi_interface INFO __init__:<module>: UDI interface initializing

I noticed the eWelink Node Server and was wondering if it supports the NSPanels from Sonoff. I also noticed that the NSpanels from Sonoff uses zigbee3 and was wondering if that is supported directly eisy with zwave/zigbee/matter extension?

Thank you all for the info. I have been looking at the Shelly RGBW2 devices as well because they will allow me to use a variety of brands but have a single interface. Only downside is... it is an additional cost and with that additional component I am not sure I would have any better control over the colors. It is is only on or off, it may make more sense to use smart switches to turn the strips on and off I like what I see from Twinkly but they seem pretty expensive and if the NS will only switch them on and off I would it may not be worth the investment. I like the LIFX strips I have but they are not rated for exterior use. I would say based on what I have read my choice is between Hue and the TP-Link Tapo if the Node server gets updated to support TAPO instead of just CASA I would still like to hear from other people what there experiences were.

Thanks for the quick reply.

I am not sure where to post this question as it covers a few different topics. I have used Lifx, Kasa and Novostella lights and each have their strong points. I even have a few LIFX LED strips but I do not think they are good for the outside. Each of the brands also offer LED light strips. I am looking at add some LED strips to my setup and to use them outdoors. I was wonder if anybody would care to share their experiences with LED light strips and the integration with eisy. Thanks

Does the TP-Link NS support both KASA and TAPO devices? I notice the TP-link application has now merged in a single application.

Over the years I have started building a node server for LG Thinq multiple times but there are stumble blocks. LG themselves make it as difficult as possible. They have changed the Api 3 times now and the api across devices are fragmented. And even the code that is available on github is pretty outdated.

Thanks for pointing me to this. Not sure why I did not see this when I searched the forums. I have it setup but have not had the ability to test it yet.