Jimbo.Automates

Yes, it's one device.

It does not scan the network, it sends out discover packets which the devices respond to. I needed this NS because I really liked their power strips and the ability control each plug on them, and then added light strips and some color bulbs. But, I would not personally have my home relying on these everywhere due to the caveat mentioned in the README: This Node server 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.

I've reported this to @bpwwer the UI shows 3.0.6 but looking at the install it's actually 3.0.7, but it's tickling another bug and fails to start. Did it actually run for you? Sent from my Pixel 6 Pro using Tapatalk

PG3 3.0.54 fixed that issue. Sent from my Pixel 6 Pro using Tapatalk

I did an install on my dev box and got the same error, so it's not just you @macjeff

Send log Package to @bpwwer Sent from my Pixel 6 Pro using Tapatalk

I upgraded to PG3 3.0.53 and all are working for me.

This is an error because PG3 is not sending the information needed by the NS. Need help from @bpwwer Sent from my Pixel 6 Pro using Tapatalk

Thanks, I've not had a chance to look into any issues, glad it's working. Sent from my Pixel 6 Pro using Tapatalk

3.0.52 is out and others are reporting that fixes these issues. Sent from my Pixel 6 Pro using Tapatalk

There are many posts about this already. We are aware and @bpwwer is looking into it. Sent from my Pixel 6 Pro using Tapatalk

This is a PG3 issue which seems to affect all NS's, will have to wait for more info from @bpwwer

This is a PG3 issue which seems to affect all NS's, will have to wait for more info from @bpwwer

This is a PG3 issue which seems to affect all NS's, will have to wait for more info from @bpwwer

Yes others are reporting issues with many node servers and the latest PG3, I've not been able to test it yet. Sent from my Pixel 6 Pro using Tapatalk

He said this was for the Kasa Node server, doesn't really mater what firmware or UI Most likely the Kasa library is not sending a power number when it's off, so the NS didn't change the value because it was missing. But should handle it properly in the Kasa NS, issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/6

PG3 3.0.48 is now released which should fix this issue.

Well that's the problem, he didn't announce this version and currently there's no way to release test versions so you'll have to wait for a fix from him Sent from my Pixel 6 Pro using Tapatalk

What version of PG3 are you guys on? @bpwwer says this may be due to 3.0.47 release which wasn't meant for everyone yet. It shouldn't be an issue with 3.0.46 Sent from my Pixel 6 Pro using Tapatalk

This seems to be caused by a change to the PG3 store, I've pinged @bpwwerfor his advice. I'm out today and tonight and traveling tomorrow.

Ok, I'll try to take a look at it later today. Sent from my Pixel 6 Pro using Tapatalk

Please download log package and send it to me. Sounds like PG3 is not sending out the auth codes. I'll also try to reinstall on the dev box to see if that happens. Sent from my Pixel 6 Pro using Tapatalk

It shouldn't matter for PG3, I thought @bpwwer added a check to not push the same value? Sent from my Pixel 6 Pro using Tapatalk

Thanks for all the details, much appreciated. 1. That's what I did, only request initial state of integers so I'll just use those when I need initial status. 2. Good point, I did that, since I rarely use it in development. 3. I had already increased mine to 5 minutes, didn't want to go much longer for fear of battery drain 4. This is possible from a couple PG2 nodes I still use. Unnecessary updates should not happen with PG3 since Bob improved it, but we can still see updates for some things more rapidly like wind speed and constant temperature changes in wireless tags. The WeatherFlow NS has a way to turn off rapid wind speed changes, but I like to know about high wind guts asap. Maybe I'll shut down the PG2 ones I still have like Blue Iris which I currently don't really use. But watching the event viewer I don't see a lot of craziness coming thru.

Using a Program as the Status Node in a Command takes a lot longer to show current status when initially opening favorites. It takes ~11 seconds to see the Armed Status node, but ~1:45 for the program status to show up... Yes I have a lot of nodes and programs, and this was when using portal as well. Using a Variable comes up after ~18seconds, so I'll use that instead.