Jimbo.Automates

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.

I think it works in PG3 now, but not home to confirm. Either way you can delete the node in PG3 UI then run discover. Sent from my Pixel 6 Pro using Tapatalk

Thanks for the log, I'll check it out. I see it's a GitHub issue now as well, thanks. Sent from my Pixel 6 Pro using Tapatalk

@bpwwer Looks like backup restore must have deleted slot 12? Sent from my Pixel 6 Pro using Tapatalk

The HarmonyHub NS is meant to control Harmony devices with the ISY. The HueEmulator NS is used to control ISY devices with the Harmony Hub Remotes. The Harmony API does not expose the Home Control buttons, you must use the HueEmulator NS.

Log into your polisy and see if the directory is really gone: ls -l /var/polyglot/pg3/ns But, as Bob said, if you did ever run 3.0.39 the database may have been corrupted. But we can give you commands to fix that if you did.

Oh that's bad... Not sure how the NS directory would get removed. We will need help from @bpwwer on this.

I think you have to restart ISY then resync UDMobile Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 node server for Camect 3.0.9 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available. If you have issues are requests please check Camect PG3 GitHub Issues to see it has already been listed. Please confirm you are on the latest version of PG3 which is 3.0.40 right now.

You can not have multiple copies of the NS running, no matter if it's V2 or V3, you can only have one for that very reason.

Yes, I intended to create a new Oauth App for using PG3, but forgot to do that, so PG2 and PG3 are using the same one, which really doesn't matter. Not sure why you had to revoke access, any should work. I have multiple copies running with different auth keys. I could still add a new OAuth App for PG3, but then everyone will have to re-auth. Or I could just change the name of the App...

Great! Sent from my Pixel 6 Pro using Tapatalk

Great, thank you for testing so quickly.

Release 3.1.1 with a couple fixes see Release Notes

I fixed the NAME issue, will be in the next release. And you did close and open the AC after the install was complete?

Ok, do a do download log package and PM that to me.

The GV12 is the "Wet State", value 1=Dry. Does that now show up in the AC? Make sure to close an open the AC after updating to 3.1.0

I mean adding adding support for setting managing spokens for Google Home, like was just added for Alexa. But a nice web UI would be good.

That looks correct to me, the key 1866 with value of local. The key "Station ID" is not needed, that's what is causing the ERROR.

The Polyglot Version 3 Node server for CAO Wireless Tags version 3.1.7 is released. This just adds support for Quad Leak Sensor, hopefully someone running PG3 has one and can confirm it all works. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available. Please confirm you are on the latest version of PG3 which is 3.0.40 right now.

Hopefully Google Home support is next? [emoji16] Sent from my Pixel 6 Pro using Tapatalk

Released version 3.0.9 with profile fixes, if you are on 3.0.8 you must upgrade. Thanks to @TJF1960 for pointing out the issues.

Thanks, fixed

I think they are all fixed?