Jimbo.Automates

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.

FlumeWater Nodeserver 3.0.8 released, see the Release Notes

Personally I just use Tasker to set Home/Away for each person based on connection to the WiFi, there has to be a small wait time on disconnect since phones occasionally loose connection for short periods of time. Using geofences had to many false triggers and this wifi method has been very robust for me for a long time. Anyone on Android can grab my Tasker share if they are interested JimboISY Tasker Share @Javi I would prefer UD Mobile implement this method as an option. I already tell it what my WiFi networks are, so it could set a variable or define toggle a node based on that

PG3 HarmonyHub Node Server 3.0.5 Released. See Release Notes

Currently PG3 doesn't give you any visual indication that an upgrade is available, that's coming in the future. (remember this is Alpha) Just cross reference your version with the one shown on the store page for now. To upgrade you just have to restart the nodeserver.

Essentially that's what I use controller for. Send DON/DOF for heartbeat. I didn't want the extra overhead of yet another node just for heartbeat, but we could if that's what we agree to. Or we had a special command like HBT that would probably be better?

I was wrong, this NS does give status while the discover is running with the "Profile Status" on the HarmonyHub Controller node.

Fixed in 3.1.2 Sent from my Pixel 6 Pro using Tapatalk

Released 3.1.2 which fixes a bug where EventState was not being reported.

Strange that it comes back with the old name, the code tries to remember things because Harmony likes to change ID's associated with activities and devices so I have to account for that. Could be a bug, or a feature The purge is documented: https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/blob/master/README.md#purge Purge Check just does the check to see what it will do, and Purge Execute actually does it. You have to watch the log to see what it's doing, and watch the log to see what discover is doing and when it's done. I could add a status on the controller to say what discover is doing, which I do in some, but not in this one. Yes, discover from the Controller and PG3 do the same thing.

Please try latest PG3 3.0.41 and see if that fixes the issue.