Everything posted by Jimbo.Automates
-
Pushover Notify Server Question
Yes, "Send Sys Custom With Params" is the current recommended method to stick with, all others are legacy.
-
Notification Node Server startup errors
This is likely a configuration issue, but I created an issue to fix in the future: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/53
-
Send Sys Custom With Params - DeviceOrGroup: cannot send to Pushover group, only 1 device or all devices
Issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/52 Will look into it after the holidays.
-
PG3 Kasa TP-Link Node Server 3.1.4
Sorry for the delay, I am traveling for the holiday. I created an issue https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/21 But it is also have problems communicating with many of your devices: 2023-12-21 10:55:55,534 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.170 trying to connect to 10.100.100.170 2023-12-21 10:56:00,538 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.169 trying to connect to 10.100.100.169 2023-12-21 10:56:05,548 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.168 trying to connect to 10.100.100.168 2023-12-21 10:56:10,553 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.160 trying to connect to 10.100.100.160
-
PG3 HueEmulator Node Server 3.0.6
DO NOT UPDATE HueEmulater to 3.0.9, it is currently broken and will be fixed after Christmas
-
Pushover Notify Server Question
You only need the bold line, you don't need the other 3 lines to send a message.
-
Pushover Notify Server Question
This indicates and error on the PG3 side, check the PG3 UI. I'll look into it when back home after the holidays. But in reality, this method is not needed anymore and was only left there for legacy users.
-
Pushover Question
The Group's should be added to the list of DeviceOrGroup but I just looked at mine and it's not adding Groups, although you should have 'all' which sends to all devices. I'm pretty sure this used to work so I'll have to look into it when I'm back home after the holidays. Issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/52
-
Using the manual method to register harmony hubs not working
Sorry, for the delay, I'm traveling for the holiday. Not sure what happened, but I can't upload the new version while out since I only brought my work laptop, not my personal one which has all the data needed. I'll take a look when back home after Christmas.
-
Using the manual method to register harmony hubs not working
Did you "Refresh Store"? it shows up on my production system. Sent from my Pixel 8 Pro using Tapatalk
-
Nodes & Controller questions
With the new ability to use custom content there's not much need to use the REST interface. Not sure of any other reference for pushover besides their website. Sent from my Pixel 8 Pro using Tapatalk
-
'Client was stopped' error
Yes, they are rolled each day at midnight. They still exist, but can't see them in PG3 UI. Sent from my Pixel 8 Pro using Tapatalk
-
'Client was stopped' error
That's great, but odd. Anything new in the log? Sent from my Pixel 8 Pro using Tapatalk
-
Nodes & Controller questions
Q1: ISYPortal node is not necessary, that was implemented before UDM node was created. But, ISYPortal does have more functionality, which is not always needed. UDM mode was simplified. Q2: It is not necessary now that custom content is available, unless you prefer that for short simple messages. Q3: When you press the "System Custom Content" button it sets the message that will be used if you click the "Send Sys Custom" at the bottom.
-
'Client was stopped' error
That warning is fine, shouldn't matter. There is nothing else in the log? Put log in debug and restart the plugin then PM me the log package.
-
'Client was stopped' error
@skunkiechris Release 3.0.9 has an attempt to fix this, please update and let me know if you see it again.
-
Using the manual method to register harmony hubs not working
This is finally released, @bmercier gave me a workaround.
-
PG3 HarmonyHub Node Server 3.0.9
PG3 HarmonyHub Node Server 3.0.9 Released. See Release Notes
-
PG3 Kasa TP-Link Node Server 3.1.4
Fixed in 3.1.4
-
PG3 ELK Node server 3.10.15
Did you manually refresh the store? It only auto refreshes once a day. Sent from my Pixel 8 Pro using Tapatalk
-
PG3 ELK Node server 3.10.15
The PG3 Node server for ELK Security Version 3.10.6 is released. See the Release Notes
-
Elk Node Server v3.5.8 on eisy
This issue is finally fixed in 3.10.6
-
Using the manual method to register harmony hubs not working
Thanks to @bigDvette this has been fixed, but due to a PG3 bug I am not able to release this plugin. Hopefully a fix can be released soon.
-
re-enable manual hub add process
I tried, but I can't release it due to a bug in PG3 that @bmercier was looking into. Hopefully it will be fixed soon. Sent from my Pixel 8 Pro using Tapatalk
-
Moving PG3 & Plugin Notifications to pushover
Those notifications can only go to UDM, they chose not to use the notification plugin. Sent from my Pixel 8 Pro using Tapatalk