Jimbo.Automates

Added issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-ecobee/issues/2 Yes, that portion of the code was never really hashed out on how it should work. The ecobee doesn't have an API command for setpoint up/down and the node server was written so you could do a DIM/BRT just like you do on a light, so it tried to guess what you wanted. I think most of that code existed before I took over the node server. I'm not sure how useful that is in reality. Looking at the code, When in auto or heat the BRT/DIM affects the heat setpoint, otherwise it affects the cool setpoint. But that doesn't match what @tmorse305 stated. You think there should be a seperate cool and heat setpoint up/down commands? So 4 commands instead of the current 2.

This is actually an ISY issue, I have no control over what is displayed in that list, and for some reason I can not tag Chris Jahn to let him know...

That was my assumption. Thanks for the great explanation. Sent from my Pixel 6 Pro using Tapatalk

The ELK NS doesn't support tasks yet, it's on my (long) list of things to add https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues I'm busy the next few weeks and on vacation but hopefully will get on it soon after returning. I'm curious what you do with tasks? I'm still a relative newbie on fully utilizing the ELK. Sent from my Pixel 6 Pro using Tapatalk

I assumed people would be doing that, so I'll make it an option and default to off.

To All ELK Node Server Users, PG3 now has the ability to rename nodes when running the latest ISY On Polisy. So my question is should it always rename ISY nodes to match the what is on the ELK, or should it be an option in the PG3 UI which defaults to off and user can turn it on? Or it could also be a command on the Controller node that you could execute from the Admin Console. Personally I always want the node names to match and what is on the ELK is my source, but others may like to rename them in the ISY and keep them? I really wish the ELK API would allow me to grab the Spoken name since that is almost always a longer more meaningful name.

If it's not showing in UD Mobile then hit the load profile button (or whatever it's called) in the PG3 UI for that Node server, then restart ISY again and re-sync UD Mobile to see if that fixes it. Although it's strange that it shows properly in AC...

Do they show correctly in the admin console and UD Mobile? Sent from my Pixel 6 Pro using Tapatalk

That issue usually means the ISY needs to be restarted, but you said Polisy was rebooted, so I'm not sure what the problem is...

I got a lot on my plate and not a lot of spare time to even make requested enhancements and fixes to my current node servers, but I'll think about it. Sent from my Pixel 6 Pro using Tapatalk

That's odd, it should be restored to the same value it was by PG3. Can you download log package and PM it to me and I'll try to review when I am back home. Sent from my Pixel 6 Pro using Tapatalk

I'm on the same versions and it works for me. Sent from my Pixel 6 Pro using Tapatalk

Port must be something else besides 8080, and 80 is reserved so use something like 8081. Sent from my Pixel 6 Pro using Tapatalk

Great, glad you figured it out, I was just coming here to review your log.

Thanks! That helped find what I needed. By default Nova only shows Sesame shortcuta in long press menu, so turning off that option now I see favorites for UD Mobile. Sent from my Pixel 6 Pro using Tapatalk

Any idea how this would be accomplished in other launchers like Nova? I can't see it? There used to be a widget. Sent from my Pixel 6 Pro using Tapatalk

I found the issue. Anyone using IFTT-Webhooks Node server restart and you should now get version 3.0.3, there was no real change from 3.0.3 except for issues with new installs, but for a while it had the old 3.0.0 version in the PG3 database.

@Javi Is the latest UD Mobile released with the fixes for sys short? Sent from my Pixel 6 Pro using Tapatalk

Thanks, there have been changes to PG3 that are causing this, I'll look into it when I get back home next week. Glad it's not fatal. https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/56

>> When using the UD Mobile app when I inspect the ELK Controller the ELK M1EXP Connected shows True, yet the Node server Online shows Disconnected. Is this expected? This is a bug in PG3, it is fixed in a test version that will be released at some point. If you run a query on the controller node it should fix the status. >> When I inspect n003_area_1 (Area Node) it throws and error UOM Suffix is null. How do I fix this issue? This is fixed in the latest release of the node server. Please re-sync UD Mobile which should fix it. >> Finally, understand arm/disarm is currently broken in the app but when it was working where would I find the button to push to arm or disarm. Just want to be on the lookout for the option when available. This is working in the latest beta of UD Mobile, not sure if it has been released to production yet, will have to ask Javier, but for some reason I can not tag him using chrome on my work computer... It's not a button, it's a selector to set Armed Status. I created a couple 'Command' items in UD Mobile which gives me a push button for arming and disarming the 2 modes I use most, Stay & Away. For other modes I select the Area node and set 'Armed Status'.

That's odd because 3.0.3 only change was to fix an issue with new installs. Not sure why PG3 won't show the correct version, I thought that bug was fixed a while back. Please restart and PM me a log package. Sent from my Pixel 6 Pro using Tapatalk

Thank you! I've been pushing IFTTT to add an API call that would allow me to just download a list of all the users configured Webhooks and automatically create a node for each one. But so far they don't seem open to the idea. Although I do like the ability to have a different Webhook for on and off, but could probably still do that if a naming convention was followed. I'll keep pushing them. Sent from my Pixel 6 Pro using Tapatalk

Also check the authorized state on the controller. @stevehoyt and I have been working on making the node server more robust at handling network issues with the flume servers, but it's still known to fail. I released a new version last night that is better but still has issues, but hopefully won't crash. If you see one please report here https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6 Sent from my Pixel 6 Pro using Tapatalk

Easy fix @GSORS400 Version 3.0.3 is released. Go to the store and refresh, then restart the node server.

@GSORS400 Thanks. It looks like PG3 is sending something unexpected, I'll look into it.