Everything posted by Jimbo.Automates
-
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.3 - OLD RELEASE POSTS
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.3 - OLD RELEASE POSTS
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
-
Clear Queued Messages
Sorry, I'm not understanding. If the message is only sent during the day or when the system is not armed then what is putting it in the queue? Sent from my Pixel 8 Pro using Tapatalk
-
Head is kinda spinning on notification server and pushover
Looks good to me. Sent from my Pixel 8 Pro using Tapatalk
-
Failed Notification Followed by Connected at Midnight
I've not received one since our last fix over a week ago, so that's the state I like. [emoji16] Sent from my Pixel 8 Pro using Tapatalk
-
Failed Notification Followed by Connected at Midnight
While that is partially true, there have been some fixes by @bmercier to reduce this from happening. I was seeing it happen to many plugins and worked with Benoit to resolve them all. Sent from my Pixel 8 Pro using Tapatalk
-
Failed Notification Followed by Connected at Midnight
It's likely coming from PG3x, are you on the latest version? Do a download log package and PM that to me.. Then do a reinstall all plugins to update their referenced libraries and see if it happens again tonight. Sent from my Pixel 8 Pro using Tapatalk
-
PG3 Kasa TP-Link Node Server 3.1.4
Ok, issue created, will try to investigate soon: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/20
-
PG3 Kasa TP-Link Node Server 3.1.4
Did it work with previous versions? Sent from my Pixel 8 Pro using Tapatalk
-
PG3 Kasa TP-Link Node Server 3.1.4
They do not need to be updated or installed anymore. Sent from my Pixel 8 Pro using Tapatalk
-
PG3 Kasa TP-Link Node Server 3.1.4
Sorry, yes I meant upgrade packages. It's not the IoX version, it's the udx version 3.5.4_2 that confirms you are up to date.
-
Totally Confused
The Configuration Instructions which are shown on the configuration page describe what to do with your API Key. For #4, can you give a little more detai what you are trying to do? What is a UBIBOT External Probe? Does that show temperatures on the IoX? If you are trying to read that probes temperature from IFTTT, that is not currently supported as mentioned in the README -> Limitations
-
'Client was stopped' error
This is an internal error in the harmony client module I use, which is not really supported anymore, but I'll try to take a look and see if there is a way I can detect and restart when this happens. It'll be difficult since it's not repeatable, and I've never seen or heard if this before. Issue created https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/issues/38
-
re-enable manual hub add process
Thanks @bigDvette I will try to pull this into production soon. Issue added: https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/issues/37
-
PG3 Kasa TP-Link Node Server 3.1.4
The Polyglot Version 3 Node Server for Kasa TP-Link 3.1.3 is released. See the Release Notes for all information. IMPORTANT: You must have the latest updates released 12/03/2023 for this to install. If you are not sure, please 'Update Modules' and reboot when complete before installing. Thanks to @Michel Kohanim for the fixes.