Jimbo.Automates

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.

Yes I've seen that as well, that's an issue for@bpwwer to look at sometime. Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Node Server for Kasa TP-Link Version 3.0.14 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available.

This is fixed in 3.0.8

That's great! I think there was something strange that happened on install that it's not able to recover from. Sent from my Pixel 6 Pro using Tapatalk

I was suggesting deleting the NS and adding it back. But yes I would prefer to see if the upcoming fix resolves the issue. Sent from my Pixel 6 Pro using Tapatalk

I don't have any Hue devices. Sent from my Pixel 6 Pro using Tapatalk

If you restore from PG2 to PG3 without first deleting the NS in PG2 you will have this issue. That should be part of the instructions. The only error is that you can't manually delete it from the ISY, for that we need Michel's help Sent from my Pixel 6 Pro using Tapatalk

There was another error in the main polyglot log I gave to@bpwwer hopefully we can get it figured out. But if you are in a rush, have you tried deleting it and add it back? Sent from my Pixel 6 Pro using Tapatalk

Restarting the NS updates to the latest version. Notifications will happen in the future.

No, good question. AFAIk it only replaces the slots that were occupied on PG2, but will need to confirm that with @bpwwer

For everyone interested in display on keypad, I've added more info to the issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/13#issuecomment-1041100647

FlumeWater Nodeserver 3.0.7 released, see the Release Notes

Restoring is all or nothing, so restore later will overwrite any changes made after the first restore Sent from my Pixel 6 Pro using Tapatalk

each NS has a sub forum /forum/326-st-inventory Sent from my Pixel 6 Pro using Tapatalk

Yes, just make sure you have purchased all of them on PG3 before you restore. And remember, this is all still considered Alpha release.

1. No 2. Many mentions have been made about backup and restore, it should work unless PG3 NS author made changes causing it to not work. 3. That would require fixing all programs that reference it. 4. Unless the NS author made the node names different then all programs will still work.

Ok, then must be a PG3 Javascript error, if you are in chrome select the 3 dot menu -> More tools -> Developer tools Then try to install again and post the error, and then may need help from @bpwwer

A query on a FlumeWater Sensor calls the flume update and updates the values it returns. A query on FlumeWater Hub currently doesn't really do anything. Currently a query on the FlumeWater NodeServer Controller querys all nodes, but that will be disabled in the future, so you should query the sensor node.

Yes. Check main PG3 log for error and post that

View the main PG3 log to find the actual error, but sounds like PG3 doesn't have the right IP address for the IoP.