Jimbo.Automates

The android version allows you to add a widget and that goes to the favorite screen. The percentage on is a great idea, or even just a count of not off devices. Sent from my Pixel 3 XL using Tapatalk

Thanks, yes I am looking at their responses, but not all 400 responses should retry. I was testing by creating a bad formatted post just to see that my retry works, but in reality a bad formatted post should not retry. I was more just curious if you were seeing something other than a 400.

Any feedback on those issues? Also, do you are anyone have a nodeserver log showing what error happens when the message is not sent? If so, please add to the issue https://github.com/jimboca/udi-poly-notification/issues/19

I like your spreadsheet method, very cool. I'd really like to allow adding those as a custom message string, but Chris is going to allow custom notifications defined in the ISY to be parsed and passed to nodeservers someday so I'm trying to wait for that... 1. Retry send on http fail. Yes, this has been on the list for a while https://github.com/jimboca/udi-poly-notification/issues/19 2. default attributes for Custom Messages that can be over-ridden on a per use basis. Will think about this one, let me know your thoughts https://github.com/jimboca/udi-poly-notification/issues/22 3. ability to change the sound attribute, including new custom sounds. Added: https://github.com/jimboca/udi-poly-notification/issues/21 I can't say when I can get to this because the ELK nodeserver is highest priority right now and I don't have much free time for that, but I will try.

Thanks@MrBill much appreciated, I'm traveling today but will review this in detail when I get a chance. No offense taken, I can be direct in my responses which can come across offensive or defensive when not intended which I don't mean. Sent from my Pixel 3 XL using Tapatalk

I was commented because you had said: My biggest problem with all of the above tho is that neither the ISY nor the nodeserver do anything on fail, the message is just lost. So I was just saying that the nodeserver does do something, you could send a message via another method when you see there was a failure. yes, you won't know what message failed but something happened... I know it's not ideal right now, but I will try to get to it when my work calms down a little. Yes, that's details for custom short messsages, there are also Notify Nodes and I was just commenting that it's not necessary, add the node then set the defaults on the node and trigger the node. Mostly I'm trying to understand how adding a new NR is easier than using the Notification NS to eventually improve it... Someday when Chris adds the ability for nodeservers to access custom messages it will get better...

The NS does set the error status when a message fails to send, it doesn't ignore it, but as of now it has no retry on failure. Will get to that someday. Also, adding a notification to a program shouldn't be that many steps, create a custom message, restart the NS and add that new node to your program. Sent from my Pixel 3 XL using Tapatalk

You mean the Nodeserver log messages? If so, just set debug mode to warning on the controller in the AC. Sent from my Pixel 3 XL using Tapatalk

That sounds correct thanks@MrBill I don't like to let nodeservers delete nodes since it could be unintentional or missed in the API somehow... Sent from my Pixel 3 XL using Tapatalk

Faster response. But if node names are all ported over so I don't have to change all my 100s of programs then maybe not a huge deal. Sent from my Pixel 3 XL using Tapatalk

I would vote to very much keep current Insteon support with the port from ISY.

Thanks, I have had 2 of those working just fine and pretty sure one has to go thru a repeater, an old aeotec but I'll check next week when I get home. I asked model because I've been considering a new 469ZP for my lake house but one of the doors is pretty far from the ISY so likely needs a repeater. Sent from my Pixel 3 XL using Tapatalk

Great information and effort. Which Schlage lock do you have? Sent from my Pixel 3 XL using Tapatalk

Nice. @Michel Kohanim just released it this morning and I hadn't had time to test the official release. Thanks for confirming. Sent from my Pixel 3 XL using Tapatalk

Yes, counters and lighting are on the list https://github.com/jimboca/udi-poly-elk/issues

Yes, as I mentioned, there is still an issue. Hopefully a new release can be generated soon. Sent from my Pixel 3 XL using Tapatalk

Looks like there is an issue with the release, not everything got updated. I've asked @xKing to look into it.

Yes, it is. Sent from my Pixel 3 XL using Tapatalk

The latest Polyglot 2.2.11 is released for Polisy the changes are all internal. https://github.com/UniversalDevicesInc/polyglot-v2/blob/master/CHANGELOG.md We are working on getting it released for RPi as well.

There was a small update to Polyglotv2 recently and the log is still writing, just to a name that the UI doesn't see. It's fixed in an upcoming version that will hopefully be released soon. Sent from my Pixel 3 XL using Tapatalk

Yes, it works on polisy Sent from my Pixel 3 XL using Tapatalk

If it was powered then WiFi would make sense, but WiFi would significantly reduce battery life. I appreciate not having to change batteries. As soon as they open the API I'll write the nodeserver... Or will eventually give up and try the Bluetooth. Sent from my Pixel 3 XL using Tapatalk

Use a decent IP Camera and a Camect along with the Camect nodeserver you can do whatever you want. https://forum.universal-devices.com/topic/31800-polyglot-v2-camect-nodeserver Sent from my Pixel 3 XL using Tapatalk

Response from Airthings Thanks for following-up. Currently there is still no API available for our consumer products yet. However I still have you on the beta tester list if that should become available [https://ci3] Sent from my Pixel 3 XL using Tapatalk

This is what they say: I don't want to purchase the HBS products, I already have the consumer products, and regret buying them because of this...