TRI0N Posted March 29, 2023 Posted March 29, 2023 Since the PG3x update I pressed a scene controller button just 5 minutes ago on my ZEN32 that will turn the hallway Kasa Switch on. That was up until last nights patch. I press that button and the attic lights come on now. It's like there is a break somewhere and its targeting the wrong device. I have checked all my button programs and have checked to make sure no kasa devices have changed or missing in the programs. So I'm stumped on that... Going to hold off a few hours for a response here and then try restarting the Kasa Node Server to see if that helps. TRI0N
TRI0N Posted March 29, 2023 Author Posted March 29, 2023 Problem resolved after restarting Kasa Node Server with update to 3.0.21.
Jimbo.Automates Posted March 29, 2023 Posted March 29, 2023 Well, glad that resolved it. The only explanation I can think of is that the IP addresses of your Kasa devices changed so the attic light is using the IP address of the hallway lights at the time the Kasa nodeserver was started up. The NS tries to realize this happens and fixes its references but it's possible that logic is not correct. You could send me a log package, but if logging is not in debug mode then I can't see the issue.Ideally you should probably reserve IP addresses for all Kasa devices in your DHCP server.Sent from my Pixel 6 Pro using Tapatalk
Recommended Posts