Jimbo.Automates

Nothing happening in the logs, Benoit has stated it's not a plugin issue. Sent from my Pixel 8 Pro using Tapatalk

As I said in my email to you: I have one nagging issue with the beta that I can't resolve with one of my plugs, but if it's working for you then I can promote beta to production. Personally I do not use Kasa plugs or switches for anything that needs to be controlled by IoX, only light strips and power strips. But in the end I would hope that connecting the new Kasa devices to IoX via Matter will be the best solution. But I've not dived into the Matter world at all yet..

Yes I responded before posting my info. Please set to warning and see if you still get the error Sent from my Pixel 8 Pro using Tapatalk

Anyone seeing the "Error processing message from client ... due to high volume", Please check the Kasa plugin log mode. Let me know what your current setting is, and change it to Warning and see if it shows up again.

Okay, I'm traveling today but will try to review this week. Sent from my Pixel 8 Pro using Tapatalk

I've released beta 3.2.5 please update, if it still isn't discovered please enable Logging "Debug + Modules" then restart the plugin, wait a while for the log to stop, then download log package and PM that to me if you still don't see the new device. This change did not solve an issue for one of my plugs which I've been unable to resolve as of yet, but hopefully it helps for your issue.

IF this happens, please run the download log package for this plugin and pm it to me.

PG3 Camect node server 3.1.0 released. - IMPORTANT: Check all your "Vehicle" references in programs, ISY driver numbers were wrong in profile. - Added Camect Plugin Documentation - USPS and other deliery vehicles fixed, Camect added 'truck', 'pickup', and 'car' to each of them which broke triggers. Now any of the delivery vehicle just triggers the real name, for example "Amazon truck" just triggers "Amazon" - Added Human's for all deliver people, Amazon, FedEx, ... - Update camect-py library to 0.2.1 - Remove websockets from requirements since it's included in camect now - Added all Driver names so the show up in PG3 UI. - Add GPV driver to all Detected Object Nodes for the Object Name detected. Useful for Notifications. You must reboot your IoX after restarting the node server for it to show up properly in notifications. - Add ERR driver on controller to track issues. Errors are shown in the PG3x UI. Currently only flags unsupported detected objects.

Sorry, work and home life are crazy. I actually thought I replied to you but I see now that I didn't. I've been waiting for a fix from the kasa library I reference which has been updated but didn't resolve my issue. I'll release a new beta soon and see if it helps your issue. Sent from my Pixel 8 Pro using Tapatalk

The Load Profile button should be on the plugin page in the PG3x UI.

Sorry, been too busy, will try to look at it this week.

That's very odd, nothing has changed with this plugin in a long time. I'll try to look into it this week.

I've updated the beta again, and testing this week. Hopefully it's all working now and I'll move to production.

Yes it's been crazy with the holiday, preparing my current home to sell, buying a new home in another state and random family visits... But my family left today so I've made some fixes and released it to beta so I can test on my production system. Sent from my Pixel 8 Pro using Tapatalk

Please restart the plugin run discover, wait a couple minutes then go to the log page of the plugin and download log package. Then PM that file to me and I'll try to review it next week.

Please try the beta in a new slot. I'll try to release it soon. Been too busy buying a new home and trying to prepare and sell our current home and move to a different state. Sent from my Pixel 8 Pro using Tapatalk

Sorry I get it now. Didn't notice this was the hue emulator forum. The hue emulator requires you to add it as a spoken in the isy console, not the portal. See Setup in https://github.com/UniversalDevicesInc-PG3/udi-poly-hue-emu/blob/master/README.md Sent from my Pixel 8 Pro using Tapatalk

So you created new activities on the harmony? If so, restarting the plugin or running discover should see them. The plugin does nothing related to spoken in the portal, that's what is confusing me. Sent from my Pixel 8 Pro using Tapatalk

The harmony can't detect power state of a device. Sent from my Pixel 8 Pro using Tapatalk

Question for all Camect Plugin Users, In my opinion I don't really see a need to have USPS car, truck, & pickup as their own drivers? Same for Amazon, UPS, DHL, ... Just have one that does them all? We could still have separate status's for each... But that being said, the simplest option to get the fix out sooner would be to just change USPS to 'USPS truck' and add 'USPS pickup' and 'USPS car'. I will probably do that later since it's easier and I don't have a lot of spare time right now. - Jim

Sorry for the delay, very busy week. I was able to look at this and see that Camect has changed "USPS" triggering which shows up as an error in the log: 2025-03-29 11:08:04.495 Thread-25 (run_until_complete) udi_interface ERROR Camera:detected_obj: Unsupported detected object 'USPS truck' Previously there was only 'USPS'. I'll try to get an update out soon, I'll add 'USPS truck', 'USPS car' and 'USPS pickup'. Ill try to keep 'USPS' being triggered for any of them, but might be easier to change it to 'USPS truck' and add car & pickup.

Jeff already posted https://groups.google.com/d/msgid/wireless-sensor-tags/2e515b6e-c11f-4e31-a398-66093fc5650fn%40googlegroups.com?utm_medium=email&utm_source=footer Sent from my Pixel 8 Pro using Tapatalk

Yes, this happens occasionally when their service is rebooting or they are doing maintenance. I was going to report to their user group but it didn't last long. Sent from my Pixel 8 Pro using Tapatalk Oh wait, it's still happening... I'll email the support group. Sent from my Pixel 8 Pro using Tapatalk

I've not heard anyone else report the ""Error processing....due to high volume" issue. Please enable debug mode, restart the node server and if you see that error then "download log package" and PM that to me. Sorry you are so bothered by kasa user or email, your kasa login user is your email so use that. Yes, for new devices it requires authentication, that's part of the issue mentioned in the first paragraph of the README "This nodeserver 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." For the beta, as mentioned in the beta thread Kasa Devices to support Please install Kasa plugin beta trial 3.2.2 in a new slot and test. I've only done minimal testing so let me know if you have any issues.