Jimbo.Automates

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?

Sounds like PG3 didn't properly kill the NS that was already running before it shut down. Log onto Polsy and run: ps -uaxww | grep python See if there are more than one notification listed. Or just reboot Polisy

Should be fixed in latest version 3.0.14 and beyond.

You should see a node named the same as your Tag Manager, select that and you will see the "Monitor Tags" option.

Haha, yes I bolded and underlined after you missed it [emoji16] thanks, I'll fix the link Sent from my Pixel 6 Pro using Tapatalk

Great, I implemented a fix but couldn't test it. Can you do a "Download Log Package" and send me that in a PM so I can see what it looks like? There shouldn't be a delay for NS polling, the OOR is pushed from the tag manager directly with no polling.

Did you miss this sentence? Please confirm you are on the latest version of PG3 which is 3.0.40 right now. The KeyError about 'pg3Version' happens when PG3 version is to old.

Didn't intend to lock this topic, just unlocked it. and released 3.0.15

Sorry, I missed this post somehow, just released a slew of fixes with version 3.0.14. 1) UNIX Epoch time. Hopefully someday Admin Console can show the actual date. 2) Yes, it seems to be. You can set logging mode to debug, then query a tag and when the tag responds you will see it 'txpwr': 159. But, this will have the same issue as signaldBm, it is only updated on a query, it will not update as it changes. Create an issue here if you can and you still want it https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues 3) Sorry, I don't have a probe so I can't check, but if you do a Download Log Package and PM that to me I'll take a look. I created an issue to track https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/48

New version released:

The Polyglot Version 3 Nodeserver for CAO Wireless Tags version 3.0.15 is released. 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.

Well I'm baffled, I tried with tinfoil and it stopped reporting but I never get out of range. Tried with it armed and disarmed. Sent from my Pixel 6 Pro using Tapatalk

Did you move to a new PLM? Sent from my Pixel 6 Pro using Tapatalk

Mine have all been working fine on IoP, just got a missed heartbeat for one yesterday. Sent from my Pixel 6 Pro using Tapatalk

For the signaldBm I created a new issue, nothing I can do about that for now: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/45

ok, will try that, but how does it know the difference of out-of-rang or if the battery is removed/dead?

Hey @garybixler, I've been working on this, check the issue link above. I've not been able to get a tag to report as out-of-range yet. I've configured the notifications and reporting time as instructed here https://wirelesstag.net/webapp.html#step4 in the logging section, then removed the battery and waited, but no report. Is there another trick?

The Wireless Tag's nodeserver is next up on my list to clean up all know issues. All users please let me know if there is an issue or request that is not covered on this list, or just add it to the list yourself. https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues Notice each issue is tag with a milestone, all those showing 3.0.14 will be in the next release for bug fixes, then I will make the 2 bigger enhancements in 3.1.0 and 3.2.0 Also, I would appreciate everyone's opinion on this one: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/24 Please comment there if you can, otherwise comment below. If you are wondering why this one is chosen to be next on my list? It's the #2 best seller off all mine so far, and the #1 best seller, Kasa, has all issues fixed. The ELK is a high priority, but I wanted to give some time to others a well.