Jimbo.Automates

I'm not sure it's possible, I'd have to look. As mentioned in the documentation, there is no official API for Kasa devices, a bunch of smart people have reverse engineered the communication and released a library that I reference. The communication can change at any time and break that library, and in fact new devices use different methods, so they have been releasing changes to their library to try and keep up. I plan to update the plugin to the new version of this library now that it seems to have stabilized. Sent from my Pixel 8 Pro using Tapatalk

Sorry, Kasa scenes are not supported at this time. Sent from my Pixel 8 Pro using Tapatalk

Sorry, I never said it supported the smart hose timer. Please set plugin log mode to debug, then restart and let it run for a couple minutes and 'Download Log Package" and PM it to me.

Likely just a temporary Internet connection issue, or their service is flooded and not responding. If it happens frequently please report to their mailing list or create a support ticket. Lately they have become horrible at responding to support tickets, but did respond to the mailing list. Sent from my Pixel 8 Pro using Tapatalk

Sorry, haven't had a chance to look yet, just to confirm there was an event on the day you did the download log package? The log is rolled over at midnight so it needs to have happened that day. Sent from my Pixel 8 Pro using Tapatalk

Please download log package and PM or email it to me. Sent from my Pixel 8 Pro using Tapatalk

PG3 Airthings Consumer Plugin 1.2.6. released, see OP - 1.2.4: 08/11/2024

Should be fixed in 1.2.6

Important! If you are running a 5.0.x version please upgrade to 5.0.4.

Important! If you are running a 5.0.x version please upgrade to 5.0.4.

Did you change it in the PG3 UI? If so, the Plugin has no idea that you changed it until you restart. I asked @bmercier if this could be added so hopefully it can be. Change it in the AC of UDM. Sent from my Pixel 8 Pro using Tapatalk

I have 2 wired and one wireless pet immune motion sensors, not sure the model... They are configured as "Burglar Interior" "Normally Closed" and I see their status change in UDMobile when they are activated they show "OPEN" and when not they show "SHORT". The "Send On" & "Send Off" do not matter for "Status", that only configures when to send a DON/DOFF if you want to add them to a scene. If nobody else has any ideas, then put the Plugin log in Debug+Modules mode, then activate a motion sensor, let it timeout then "Download Log Package" and email that to me.

This was a known issue with older versions of PG3. Are you running: PG3x Version 3.2.27 ? If not please do a "Upgrade Packages" from Admin Console -> Configuration -> System Tab.

PG3 Airthings Consumer Plugin 1.2.4. released, see OP - 1.2.4: 08/11/2024 - Restore "Auto Short Poll" and "Short Poll" values as saved in PG3 DB

Version 1.2.4 should fix this until PG3X is fixed: - 1.2.4: 08/11/2024 - Restore "Auto Short Poll" and "Short Poll" values as saved in PG3 DB

The 1.2.3 version issue is fixed. But there are 2 issues with PG3 that I've notified @bmercier about. 1. On upgrade install PG3 is resetting shortpoll back to default. 2. If you change Controller -> "Auto Set Short Poll" = True, then on restart it will put it back to False I created programs to set mine back to desired value to get around this issue until we can resolve.

I said I would take a look, I never said it was fixed. I'll try to look tonight after work if I have time. On update, or on all restarts?

1. Did you turn off auto set shortpoll? That was added in previous release which should set the proper minimum poll based on how many devices you have. 2. I'll take a look Sent from my Pixel 8 Pro using Tapatalk

Fixed in 5.0.3

Thanks, I'm not surprised. Very little of the control abilities have been tested. Was concentrating on the webhooks. I'll try to test tonight. Sent from my Pixel 8 Pro using Tapatalk

@MGustin Please check your longPoll value on the config page, I left it as the default 60 for initial version of 5.x but you need to increase it to at least 600 to avoid hitting the Rachio API Rate limit. I'm going to add a driver to watch the rate limit in a future release.

Awesome. Since you are the first running 5.x please leave the Log in Debug mode in case you come across another issue.

Got to Plugin Store and click Refresh Store.

@MGustin, Also please make sure to set Log to Debug in the Plugin Log Page, received logs were still in Info mode.

Sorry, was busy implementing another fix which hopefully will fix your issue. It was not properly reconfiguring the webhooks on the Rachio servers. It should now. Try 5.0.2 and let me know. I'll review your logs now to see if there is another issue.