Jimbo.Automates

Did this just show up or always been happening? What changed? Sent from my Pixel 6 Pro using Tapatalk

I created this issue a while back, will try to look into it. https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/52 Sent from my Pixel 6 Pro using Tapatalk

No, that's it. Glad they found and fixed the issue. Sent from my Pixel 6 Pro using Tapatalk

Those messages are on the controller node since they will apply to all service nodes. Sent from my Pixel 6 Pro using Tapatalk

Support finally got back to me and said: I found the issue. The signal and transmit power were not supplied if the "buffer multiple data point" option is enabled. It is all fixed now, please try again. Sent from my Pixel 6 Pro using Tapatalk

Ok, then I'm not sure what is going on since this way works with my tag type 12 and supposedly this was a server side update so everyone should see it... Can you try rebooting your tag manager, then restart the Node server and see if it goes away?

Well, I did, but looks like it upgraded last time succesfully? Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 17:27:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Tue Mar 8 17:27:48 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios update ... rebooting Tue Mar 8 17:29:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 17:29:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 17:29:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Tue Mar 8 17:29:06 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version

That's odd, looks like a tag type 12 which is working fine for me. Does it show like this in the admin console?

Yes of course I realize that. I just don't want to get stuck in a boot loop like @simplextech since I have 3 very early versions as well. What can be done to prevent that with the original ones was my question. Sent from my Pixel 6 Pro using Tapatalk

So what is the fix? Something we can do before installing to not have the same problem?

What tag type is that? I'll try to find time when I return home to exclude the new options from it. Sent from my Pixel 6 Pro using Tapatalk

Thanks, yes, I need to remove the poll options, they don't work with PG3 currently. I thought users might want to change the values in a program, not sure if anyone actually does that.

@wmcneil Thanks for confirming. Sent from my Pixel 6 Pro using Tapatalk

Those are new values they added recently, obviously they didn't add it to all tags. It's actually causing errors with leak sensors, I've asked their support to fix it. If I don't hear back I will remove it when I return home after this weekend. Sent from my Pixel 6 Pro using Tapatalk

Sure, I can look into that sometime, but doesn't Kasa have an Alexa method already? Why use it through the ISY? Sent from my Pixel 6 Pro using Tapatalk

Thanks @bpwwer for fixing that! I have uploaded 3.1.4 now.

That does make a little sense, if you have moved to IoP. When you reboot Polisy then when ISY On Polisy starts up and Query All on restart option is enabled, it spends a lot of time querying all nodes on PG3 so it's very busy. Waiting for the initial Query All to complete is best before messing with anything on PG3 like adding or deleting NS's.

I didn't see your update In the future post a new comment so it's more obvious. But yes, the PG3 python library was not updated, so deleting and re-installing forced it to update. Future versions of PG3 should force an update of that library when it's updated.

No worries. I've not heard back yet from support, and I'm heading out of town for a few days in the morning, so probably won't have time to put in a fix for this tonight. In the meantime you'll have to edit that URL and remove the singnaldBm and txpwr from the url manually, or turn it off.

If you are seeing multiple copies running after a fresh reboot of Polisy, that mans PG3 is crashing. @bpwwer and @Michel Kohanim are working with another user to debug that issue. Yes, there are new versions of almost all my NS's which improve how they shutdown when PG3 asks them to. But, there is currently a bug in PG3 that it's seeing the new verisons, but not downloading them. @bpwwer is aware and working in a fix.

I upgraded my dev box and I don't see this issue. Can you set Log to Debug and restart the NS, and if it happens again download log package and PM that to me?

The HueEmulator PG3 Node Server 3.0.5 is released. See the README for more information, including information along with the Release Notes But, the current PG3 3.0.44 is broken, so it won't be downloaded until the next PG3 version is out.

Yes, the new version is there, but the store is having issues while he is working on getting production, non-production, and local stores all working properly. That's the struggle with using Alpha versions Hopefully will get straightened out today.

Sometimes they don't respond to support tickets for a few days, so I'll have to generate a new release that exclude those setting for the leak sensor, will try to do that tonight.

That's bizarre, they just added the signaldBm and txpwr to their servers for us last week. The upgrade is not due to PG3, it's because when PG3 was restarted it checks and updates all NS's to the latest, and that change was released to the WT NS about 9 days ago. So it looks like they didn't add those settings for the Quad Leak Sensor, I will ping them on the support ticket.