Jimbo.Automates

Please open a support ticket and send this in along with the uuid of your polisy Sent from my Pixel 8 Pro using Tapatalk

Yes, issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/24 Sent from my Pixel 8 Pro using Tapatalk

But that was the last notification it sent at 1:04pm in the log file you sent which correlates with your screenshot. Here are all the successful sends before you hit the limit, then the attempted sends which resulted in the error message being sent: 2025-01-30 11:23:19.438 Thread-15 (send) udi_interface INFO UDMobile:send: Message Sent: {'system': True, 'title': 'eisy 00:21:b9:02:60:68 Notification Node Server Free Edition Startup.', 'body': 'Please upgrade to Standard version to get all features'} 2025-01-30 11:29:28.712 Thread-23 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 11:29:27 Event '6249 Southridge greens' Status set to 3876.55 Watts"} 2025-01-30 11:35:28.453 Thread-31 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 11:35:27 Event '6249 Southridge greens' Status set to 4357.345 Watts"} 2025-01-30 11:40:28.289 Thread-37 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 11:40:27 Event '6249 Southridge greens' Status set to 4511.804 Watts"} 2025-01-30 11:51:28.403 Thread-50 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 11:51:27 Event '6249 Southridge greens' Status set to 2437.53 Watts"} 2025-01-30 11:56:28.141 Thread-57 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 11:56:27 Event '6249 Southridge greens' Status set to 2337.535 Watts"} 2025-01-30 12:04:28.319 Thread-67 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 12:04:27 Event '6249 Southridge greens' Status set to 1329.026 Watts"} 2025-01-30 12:09:28.301 Thread-73 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 12:09:27 Event '6249 Southridge greens' Status set to 3542.016 Watts"} 2025-01-30 12:14:28.609 Thread-80 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': '6249 Southridge greens', 'body': "2025/01/30 12:14:27 Event '6249 Southridge greens' Status set to 4174.399 Watts"} 2025-01-30 12:19:27.805 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:19:27 Event '6249 Southridge greens' Status set to 5469.98 Watts"} 2025-01-30 12:19:28.681 Thread-86 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:24:27.309 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:24:27 Event '6249 Southridge greens' Status set to 5591.087 Watts"} 2025-01-30 12:24:28.020 Thread-93 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:29:27.904 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:29:27 Event '6249 Southridge greens' Status set to 5645.919 Watts"} 2025-01-30 12:29:28.680 Thread-99 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:34:27.294 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:34:27 Event '6249 Southridge greens' Status set to 5800.846 Watts"} 2025-01-30 12:34:28.281 Thread-106 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:39:27.754 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:39:27 Event '6249 Southridge greens' Status set to 5803.815 Watts"} 2025-01-30 12:39:28.489 Thread-112 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:44:27.403 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:44:27 Event '6249 Southridge greens' Status set to 5850.703 Watts"} 2025-01-30 12:44:28.284 Thread-119 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:49:27.859 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:49:27 Event '6249 Southridge greens' Status set to 6020.411 Watts"} 2025-01-30 12:49:28.565 Thread-125 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:54:27.863 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:54:27 Event '6249 Southridge greens' Status set to 6063.592 Watts"} 2025-01-30 12:54:29.025 Thread-132 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 12:59:27.942 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 12:59:27 Event '6249 Southridge greens' Status set to 6090.358 Watts"} 2025-01-30 12:59:28.596 Thread-138 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '} 2025-01-30 13:04:27.825 Command udi_interface INFO UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 13:04:27 Event '6249 Southridge greens' Status set to 6161.4 Watts"} 2025-01-30 13:04:28.604 Thread-145 (send) udi_interface INFO UDMobile:send: Message Sent: {'title': 'Reached max daily message count, please upgrde to Standard Edition', 'body': ' '}

It's trying to send message: UDMobile:do_send: params={'title': '6249 Southridge greens', 'body': "2025/01/30 13:04:27 Event '6249 Southridge greens' Status set to 6161.4 Watts"}

I couldn't make it happen on my development machine. Please enable it again and download log package after it starts nagging you, and PM that file to me. Sent from my Pixel 8 Pro using Tapatalk

Thanks I'll try to look at it today, in the meantime you can stop the plugin. Sent from my Pixel 8 Pro using Tapatalk

Yes, odd. You don't have any programs sending messages? Sorry I didn't have time to review the code today. Sent from my Pixel 8 Pro using Tapatalk

The short poll value always comes from the controller, not the PG UI. This is so it can be changed on the fly by IoX programs. Also disable auto set if you want to manually control it. https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/CONFIG.md Sent from my Pixel 8 Pro using Tapatalk

I don't think there's any timer in the plugin to send that notification, it only sends it if you have passed the limit and try to send a message, but I'll check the code and confirm. You can download log package from the plugin log page and PM that to me and I'll review. Sent from my Pixel 8 Pro using Tapatalk

Discovery does not use ping, it sends UDP packets, which do not cross subnet boundaries. There is a discussion about this on the python-kasa issues https://github.com/python-kasa/python-kasa/issues/1431 I'll look into that error. Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/23

Two separate issues 1. Control all backlighting brightness: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/105 2. Enable turn on/off function keys https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/110 I don't think #1 is possible, if someone knows this is possible please comment on the issue.

The original post Is asking for the ability to control the function key lights, which I originally misunderstood. See my latest post there. In my misunderstating I created this issue which I have updated with the latest information. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/110

Sorry all, I totally misunderstood the request. For some reason I thought it was to brighten/dim the entire keypad. But of course now that I read it again you just want to turn function keys on/off. There are of course API calls in the Elk to control the function key lights, I will look into adding this feature. Proper issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/110

Glad you got it working, and thanks for following up. That's interesting, I guess the discovery packets were not making it to the device when WiFi was weak. But, I'm not sure why it wouldn't work when you manually put in the device IP address. The devices are not "grouped" by name, for Kasa devices that only have one thing to control the plugin sets their "parent" to the Controller. But devices that have multiple, like a powerstrip can not have their "parent" be the controller, because IoX doesn't allow multiple levels of hierarchy, so the powerstrip has no parent, and each plug sets its parent to the powerstrip. You can right click on the Controller and select "Ungroup" and then move them into folders if you desire. I could prefix the name with Kasa and once you restart the AC it will show up near the Controller. I'll think about it.

Fixed in notification plugin 3.6.16.

But you are correct, after reviewing the code I see that changing a group name is ignored. I'll work on a fix.

Restarting the plugin should update the profile, then close/open AC and you should see the new names. But the error above indicates it had issues communicating with the portal. Were there mare WARNING lines before that?

Interesting, can you enable debug log, run discover, download log package and PM it to me? Sent from my Pixel 8 Pro using Tapatalk

I'll order an eisy so I can test this myself in the future, but try entering your real network address in the config and see if that helps. The configuration help explains it. Extra Disovery Networks By default the node server runs a discover on the default network of the machine running PG3. If the machine has multiple networks, or you have other networks on your LAN you can run discover on those networks e.g. 192.162.4.255.

@dbwarner5 just reminded me in another post that if your eisy has WiFi enabled this plugin will not work because the WiFi creates its own network. It may be fixable by entering your real network in the config but I can't be sure since my development box is a polisy. Sent from my Pixel 8 Pro using Tapatalk

Oh yes, I forgot that as well! Thanks for the reminder. Sent from my Pixel 8 Pro using Tapatalk

The controller node "discover" should see your device. If it doesn't then something is blocking it or weak WiFi to the device. Sent from my Pixel 8 Pro using Tapatalk

The HS300 is one of my test devices and works perfectly with the latest production and beta releases of the plugin. Something on your network is stopping the eisy from seeing that device. Also, as I mentioned you should not have to manually enter any IP addresses for devices if they are all on the same network and you have no network rules in your router stopping them and decent WiFi coverage to the HS300. The "Can't find db_getNodeDrivers" is a result of failure to communicate with the IP address you entered. See the earlier errors. 2024-12-27 16:30:20.160 Thread-11 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 192.168.1.189 trying to connect to 192.168.1.189 2024-12-27 16:30:21.018 Thread-11 (run_forever) udi_interface WARNING SmartDeviceNode:connect_a: SmartStrip 5091E3A14343: Device 192.168.1.189 responding again 2024-12-27 16:30:21.018 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:set_connected: SmartStrip 5091E3A14343: failed: You need to await update() to access the data 2024-12-27 16:30:21.019 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:connect_a: SmartStrip 5091E3A14343: Unable to connect to device 192.168.1.189 will try again later: You need to await update() to access the data 2024-12-27 16:30:23.236 Thread-515 (handler_poll) udi_interface WARNING SmartDeviceNode:handler_poll: SmartStrip 5091E3A14343: Node not ready to poll, must be disconnected or slow to respond? 2024-12-27 16:30:23.723 Thread-11 (run_forever) udi_interface ERROR SmartDeviceNode:update_a: SmartStrip 5091E3A14343: failed: Unable to query the device 192.168.1.189:9999: [Errno 54] Connection reset by peer

Awesome! Glad its finally working. The new library has the ability to query features supported by the device so I need to do some rework on how I create the node so it properly shows the features it supports, like voltage and current.

Please try 3.2.4