Jimbo.Automates

DO NOT UPDATE HueEmulater to 3.0.9, it is currently broken and will be fixed after Christmas

You only need the bold line, you don't need the other 3 lines to send a message.

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.

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

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.

Did you "Refresh Store"? it shows up on my production system. Sent from my Pixel 8 Pro using Tapatalk

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

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

That's great, but odd. Anything new in the log? Sent from my Pixel 8 Pro using Tapatalk

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.

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.

@skunkiechris Release 3.0.9 has an attempt to fix this, please update and let me know if you see it again.

This is finally released, @bmercier gave me a workaround.

PG3 HarmonyHub Node Server 3.0.9 Released. See Release Notes

Fixed in 3.1.4

Did you manually refresh the store? It only auto refreshes once a day. Sent from my Pixel 8 Pro using Tapatalk

The PG3 Node server for ELK Security Version 3.10.6 is released. See the Release Notes

This issue is finally fixed in 3.10.6

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.

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

Those notifications can only go to UDM, they chose not to use the notification plugin. Sent from my Pixel 8 Pro using Tapatalk

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

Looks good to me. Sent from my Pixel 8 Pro using Tapatalk

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

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