Posted September 15, 20232 yr Old topic, but still an issues: I seem to remember last time I changed the name of one of my Kasa smart plugs on my Kasa phone app it was reflected in the NS and AC, but that is not happening now. How do I get the NS to recognize the name changes? I have restarted the NS a couple of times
September 15, 20232 yr Old topic, but still an issues: I seem to remember last time I changed the name of one of my Kasa smart plugs on my Kasa phone app it was reflected in the NS and AC, but that is not happening now. How do I get the NS to recognize the name changes? I have restarted the NS a couple of timesThere's a configuration param change_node_names set it to true and restart the node server.Sent from my Pixel 6 Pro using Tapatalk
September 15, 20232 yr Author we have discussed the earlier this year, it does not work, at least for me. So when I change the name in the app it does not reflect in the NS or AC
September 15, 20232 yr we have discussed the earlier this year, it does not work, at least for me. So when I change the name in the app it does not reflect in the NS or ACUnless I'm remembering wrong, the problem was the version of PG3 didn't support it. But it should all be working now. I'll try to confirm this weekend.Sent from my Pixel 6 Pro using Tapatalk
September 23, 20232 yr On 9/14/2023 at 9:05 PM, jkraus said: Old topic, but still an issues: I seem to remember last time I changed the name of one of my Kasa smart plugs on my Kasa phone app it was reflected in the NS and AC, but that is not happening now. How do I get the NS to recognize the name changes? I have restarted the NS a couple of times Fixed in 3.1.0
September 23, 20232 yr 4 minutes ago, jkraus said: I upgraded but now no local control on he AC, its blank Looks like it doesn't know what type of device that is, it should show the device type next to where it shows n006_xxx - Check the node server log for ERROR and WARNING. The next enhancement I'd like to work on is making errors show up as notices on the PG3 UI, just ran out of time to do that.
September 23, 20232 yr 1 minute ago, jkraus said: Nevermind, rebooting the system worked Oh that's good! A full reboot of eisy/polisy, PG3 or the node server?
September 23, 20232 yr of the PolisyOk, that is odd. Shouldn't be necessary but glad it's all good.Sent from my Pixel 6 Pro using Tapatalk
September 23, 20232 yr Author BTW, thanks for the upgrade, I can delete devices and change names, great!!! Edited September 23, 20232 yr by jkraus
September 23, 20232 yr Author oops, Kasa NS now "disconnected" and cannot get it to connect even with restarting it and restarting the PG3
September 24, 20232 yr oops, Kasa NS now "disconnected" and cannot get it to connect even with restarting it and restarting the PG3Please download log package and PM it to me.Sent from my Pixel 6 Pro using Tapatalk
September 24, 20232 yr Author got it working. Had to restart the PG a couple of times. I seem to have variable success with KASA devices working in scenes, sometimes they work others not.
September 24, 20232 yr If it has shown disconnected or failed then please download log package and PM it to me.Not sure why it would not work in a scene it's very reliable for me. Put log in debug + modules mode activate the scene a couple times and download log package and PM it to me and mention what device is not working.Sent from my Pixel 6 Pro using Tapatalk