Jimbo.Automates

Released 3.3.5 see the Release Notes

3.3.5 released with a fix.

Version 3.1.6 released to fix this issue.

Yes, this is a bug introduced in the latest version that only happens on new installs. I'm not home until Tuesday but will try to get a fix out soon. Issue created: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/58

Sorry, been out out of town and busy, I got your PM and I will review.

Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/76

Sorry for the late reply, been out of town. This looks like a bug handling Counters. Please set log level to Debug + Modules and restart the node server, then wait a few minutes and download log package and send that to me in a PM.

Sorry, was a result of restructuring the code to fix the other issue. Fixed in 3.0.15.

Released 3.3.4 see the Release Notes

Yes, PG3 only automatically refresh once or twice a day I think.

Sorry, my bad, we are required to update the version in 2 places and I missed one. New zip file uploaded but will only fix it for new upgrades. But don't worry, you have the latest release.

Thanks guys, I tested the best a could by faking out a invalid_token failure and it seems to work so I have released 3.0.14.

Fixed in 3.3.3

Released 3.3.3 see the Release Notes

No authorization issues overnight for me, so I can either release it and if you can upgrade which will risk complete failure since I haven't seen the issue yet, or I can wait to see a failure. @stevehoyt have you seen any issues with the current release?

PG3 Node server for CAO Wireless Tags version 3.1.5 is released, see the Release Notes.

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