Jimbo.Automates

Thanks, I've had the programming issues with using scenes figured out for a while. But if switching to z-wave I'm not sure there is a speed advantage over programs so may no longer be an issue, insteon in scenes are so fast...

I had purchased a Zooz ZSE11 a while back and liked it a lot, but what I didn't like is if you put the motion in a scene to turn on the scene, then when it timed out it would turn off the scene and there was no way I could find to ignore it. So you are stuck with using programs to turn on scenes. Support told me this, and I could find a way to do this with the ISY. Do you know if it's possible with the ZSE40? What kind of battery life are you getting? I tried one of these as well and the accuracy of the battery level reporting. That's an amazing claim of 5 years battery life! Do they work in scene's and have the ability to ignore the off? I still love the speed of the old Insteon MS's but they are a little ugly, and having to make educated guess when battery will die is annoying, or hoping the low battery gets sent out and received...

The NS is dependent on both. If it detects an error when trying to send it sets an error condition on the node and for most errors it will retry. So, IMO, it is much more reliable than using email or NR from ISY. But, you can check that error status and send a notification another way if you like. I've considered trying to send an email when there is an error that looks to be an issue with the pushover service, but that won't happen for a while. Sent from my Pixel 6 Pro using Tapatalk

Currently you can only have one copy of the NS running on the same machine because it uses a hardcoded port number. I think I have an issue filed to fix this. Sent from my Pixel 6 Pro using Tapatalk

Yeah, the disappearing configuration info is a PG3 bug, hopefully will be fixed soon. Sent from my Pixel 6 Pro using Tapatalk

The order doesn't matter, only on or off must be last. Sent from my Pixel 6 Pro using Tapatalk

Set log to debug in PG3 UI, restart NS, open AC and if problem still exists download log package and PM that to me. Sent from my Pixel 6 Pro using Tapatalk

Did you close and reopen the AC? Sent from my Pixel 6 Pro using Tapatalk

That's weird. Please download log package and PM it to me Sent from my Pixel 6 Pro using Tapatalk

No, just need patience Wasn't able to check until just now, and re-uploaded and confirmed it is there.

Need more time in the day not luck, day job kept me slammed today. Just uploaded again and confirmed it took.

Ok, sounds like my upload of the new version didn't go through completely. I'll check later. Sent from my Pixel 6 Pro using Tapatalk

Thanks for the logs! This was caused by a change to PG3. New version released.

PG3 Ecobee 3.0.1 NS released see the Release Notes

PG3 IFTTT Maker Webooks version 3.0.1 is released, see the Release Notes

Oops, guess I broke it and didn't re-test before releasing. I'll fix it tonight, but you can move it to the On event.

If it encounters an error the node status will show change. But IFTTT doesn't error out for things like misspelled trigger. Check the Nodeserver log and you should see it send the request to IFTTT? Sent from my Pixel 6 Pro using Tapatalk

That all looks good, yes the nodeaddress is what you want the node address to be in the ISY, the Node name is what you really se in the ISY so something like "Spotify Pause" would make sense. So each node it creates can have an "On" trigger and "Off" trigger, this is useful if it's something where on and off make sense. But you don't have to enter both. I would put your "Spotoff" in the On event name, then when you turn on the "Spotify Pause" node it will pause spotify.

Hey nice to see it may be useful for someone else! On the configuration page where you added your API Key should see these instructions: https://github.com/UniversalDevicesInc-PG3/udi-poly-IFTTT-Webhooks/blob/master/CONFIGURATION.md Although there is bug in bug in PG3 where sometimes doesn't show the configuration documentation. Hopefully those instructions clear it up?

This release brings a big change that makes using the REST option for the Notification Nodeserver much easer: The addition of: - Network resources malformed when using URL encoding. Follow these instructions${sys.node.#.name:url} - URL encodes the resulting string${sys.node.#.name:std} - Does standard formatting (as done currently)${sys.node.#.name} – Does default formatting (currently same as using “:std”) Now allows to create a Notification where the subject contains any node or program name, so you can use this in the path: /send?node=po_dev&monospace=1&device=2&Subject=node:${sys.node.#.name:url}+program:${sys.program.#.name:url} Even when the program contains spaces or other characters that would cause problems. Now one network resource can be used for multiple notifications with different subjects - Jim

The other issue being discussed is that a query of a nodeserver node doesn't always send back the status to the ISY if it thinks there is no change. If you restart ISY and have Query on Restart enabled then all current node status should come back to ISY, but currently it does not.

The Polyglot Version 3 Node server for IFTTT Maker Webooks https://ifttt.com/maker_webhooks version 3.0.3 is released. See the README for more information. The Release Notes are also available.

Yes, I understand your hesitancy, but for me it has been extremely robust with some simple bounce detection, and I'd really like it to be integrated into UD Mobile. My trials with using geofencing were horrible, many false exits for me, but of course I haven't tried it in a couple years, and still the battery drain from a simple wifi check must be better than geofencing I don't use if for anything security related, just changing HVAC settings, sending notificaitons if doors/windows are open, if everyone is gone let us know we didn't arm the alarm, ...

Thanks, looks like Leak Sensors report lux and light state, I can add that. 2022-02-26 16:51:37,791 Command udi_interface ERROR Tag:set_lux: 5:34:ca8f9c951a6968:Leak Sensor 5: does not have lux but was sent 3.388070821762085 2022-02-26 16:51:37,803 Command udi_interface ERROR Tag:set_list: 5:34:ca8f9c951a6968:Leak Sensor 5: Is not configured for light state, let the author know it is needed value=0 Added issue: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/51

PG3 Nodeserver for CAO Wireless Tags version 3.1.3 is released, see the Release Notes.