Jimbo.Automates

Added support in 3.1.5

Never mind, don't worry about sending a log, I found an issue. My test instance had been running great for a couple weeks with no issues so I had shut off notifications while I was on vacation so I didn't see the issue when mine failed. I see the problem and have a fix implemented and running. I'll let it run overnight and try to release tomorrow.

Do a discover again, and check the PG3 and NS Logs for errors. Might be an illegal character in the device but I thought I was removing all of them.

You'll need to send me a log file on the day it happens. You can setup a notification which monitors the Node Status and Authorization Status to see if that is causing the failure. The auth status will go to "Not Authorized" periodically, but the node server should recover, if it doesn't, please let me know. Put Log into Debug mode will help me if the problem does occur.

I currently have some Insteon devices unplugged and notice every time I startup UD Mobile that the AC throws up the "Cannot Communicate With ..." errors. Is it expected that UD Mobile queries devices to cause this?

I don't remember how it tells you the tag manager connected status, I'll have to check after vacation. The app on Android tells me when tag manager goes offline so I've never worried about it on ISY. Sent from my Pixel 6 Pro using Tapatalk

Thanks, that was my suspicion, just when you said random I wasn't sure. It should set status during nightly query, but not send DON/DOF I will fix that when I return home. Sent from my Pixel 6 Pro using Tapatalk

Can you define random? Put log in Debug and when it happens download log and PM it to me. I would test but on vacation and won't be home for another couple weeks. Sent from my Pixel 6 Pro using Tapatalk

Ok, setting to true should initiate a discovery and add them, if not try restarting the NS. Sent from my Pixel 6 Pro using Tapatalk

Yes, I'll work on a node server if possible in a couple weeks after vacation. Sent from my Pixel 6 Pro using Tapatalk

Each tag manager has a "Monitor Tags" option which is False by default. Did you set it to True? Sent from my Pixel 6 Pro using Tapatalk

/topic/34059-pg3-release-status-3062-rc2-scroll-to-bottom-for-latest-update Sent from my Pixel 6 Pro using Tapatalk

Released 3.3.1 see the Release Notes

Thanks for the offer on the Perl code, I wish node servers were in Perl, that's language I use at work a lot more than Python! But all the new kids love Python... This issue should work properly in 3.3.0.

IMPORTANT: Starting with the 3.2.0 release it uses a new feature only available with ISY On Polisy 5.4.2. It should still function on older versions, but there may be issues loading the profile on older versions which will make programs using at least the Area nodes have issues. The Polyglot Version 3 Node server for ELK Security Version 3.3.5 is released. See the Release Notes See the README for more information, including information on moving from PG2. If you have issues orvrequests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

Thanks, I'll leave it here for now and see if there are any more comments or opinions from Ecobee node server users.

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