MWareman

Just getting to try this now - and I am not seeing the UDI Mobile (geofence) app. I'm on a Pixel 6 Pro - so very up to date API version. Did the functionality get merged into the main app. and if so how do we pair the app with the Occupancy 2.0 service? I can get the PIN, but cannot find where to use the pin to pair my phone. Michael.

It's OK @Michel Kohanim - I was able to adjust the code to remove the dependency and the Poly is functioning fine. It was a free poly - so no refund necessary. Truthfully - all that need to occur is removing line 15. Not sure who can do that in the github repo though if not the author.

I don't have the board installed (yet) and still have the dongle connected. The most recent upgrade went to 5.4.5 and the name changed from IoP to IoX: I don't see the zwave version selector yet - I assume this is not available with the dongle but is with the ZMatter board: Biggest question is should I leave the usb dongle connected after installing the board - or disconnect it before booting after installation? I assume a backup taken prior to install will simply be restored. I have a question on the backup though since that's throwing an error (documented in another thread in the IoP part of the forum). I know I should have patience for the new documentation.... I just find that difficult with the new toy in hand!

IoP appears to now be IoX - mine upgraded seemingly fine. However, the backup is throwing an error (I documented in another thread)

Running a backup thru IoP - I am getting this: Clicking 'OK' in the otherwise blank popup, I get this: After clicking 'OK' to this error - the backup terminates. I am not sure if the backup is complete - or if it terminated early due to the error. Here are my versions: Any idea? Michael.

My question is this. I have the 700 USB zwave dongle - and (of course) want to migrate my network. Can I install the zmatter board and button up my POLISY while awaiting the migration instructions - or should I do NOTHING until the instructions arrive?

I posted in this part of the forum (UnifiPresence) to try to contact the developer. Is it @automationgeekby chance? https://github.com/UniversalDevicesInc-PG3/udi-presenceUnifi-Node server/blob/main/README.md Edit: You can see the erroneous import on line 15 here; https://github.com/UniversalDevicesInc-PG3/udi-presenceUnifi-Node server/blob/main/unifi_poly.py

Unifi Presence has very different functionality. This is not for notifying - it's about detecting the presence of devices connected to my Unifi network. I don't know why this poly even has the Pushover library imported at all - I've seen no functional impact to just commenting it out and cannot see it referenced in the code anywhere. I do use your Notification poly for other reasons - but it does not do what this poly is about. Thanks! Michael.

That is how node servers managed by PG3 show in the PG2 console. Are you sure these are not PG3 node servers?

Request sent! Thank you.

This has let me down a rabbithole now.. I have been having trouble witht he BIOS update - it just seemed to fail from the GUI. Of course - I noticed the 'update.bios' command in the script.. [admin@polisy ~]$ sudo /usr/local/etc/udx.d/static/udxops.sh update.bios executing from /usr/local/etc/udx.d/static Sun Oct 2 18:28:03 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: starting bios update Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios mfr: Universal Devices Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios product: Polisy Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios ver: 1.0.0 Sun Oct 2 18:28:04 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios version 100 is old and needs to be upgraded flashrom on FreeBSD 13.1-RELEASE-p2 (amd64) flashrom is free software, get the source code at https://flashrom.org Using default programmer "internal" with arguments "". Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns). coreboot table found at 0xcfec5000. Found chipset "AMD FCH". Enabling flash write... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Using regions: "RW_SECTION_A", "RW_SECTION_B", "PSPDIR". Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x00030fff: 0xd d2 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x00037fff: 0x7c92 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00030000! Expected=0xff, Found=0x24, failed byte count from 0x00030000-0x0003ffff: 0xf708 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x2f, failed byte count from 0x00000000-0x007fffff: 0x555677 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x2f, failed byte count from 0x00000000-0x007fffff: 0x555677 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Looking for another erase function. Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom@flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Sun Oct 2 18:29:37 CDT 2022|/usr/local/etc/udx.d/static/udxops.sh: bios update ... rebooting POLISY then rebooted - and (fortunately) it came back. Seems the BIOS update process is failing on my POLISY and thru the CLI there is at least some detail as to why. How would I go about addressing this? Thank you!

Thank you!

I edited the unifi_poly.py to comment out the line (line 15) - and the poly then started fine. I'm not sure if the library is used anywhere - but it seems it may not even be needed at first glance.

I guess one question is - why is the pushover module needed for this poly? Seems unnecessary for the purpose. I did try installing the module: pip install pushover-python I get the same error - even though the install appears to have been successful.

I know this poly was working in thee past - but in one of the upgrades something obviously occurred. I have tried restarting, but every time I get this error (and it stops). 2022-10-01 14:10:35,429 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-10-01 14:10:38,326 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.47 Starting... 2022-10-01 14:10:38,331 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-10-01 14:10:38,332 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/{UUDID}_15/./unifi_poly.py", line 15, in <module> 2022-10-01 14:10:38,334 MainThread udi_interface ERROR udi_interface:write: from pushover import init, Client 2022-10-01 14:10:38,335 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-10-01 14:10:38,336 MainThread udi_interface ERROR udi_interface:write: : 2022-10-01 14:10:38,337 MainThread udi_interface ERROR udi_interface:write: No module named 'pushover'

I appreciate the detail. You were spot on. Even though this Node server was installed months ago - many reboots have occurred since. A new reboot (and a restart of the poly afterwards) fixed the issue. I really have no idea why the issue occurred to be honest. Either way - thank you for the detail and the assist.

That makes sense now. It was odd at the time because 'pkg update' updated something that had a dependancy on a newer library that had not yet been updated. Is there a cli way of (for instance) going from 13.0 to 13.1 safely?

@bpwwer Been loving this node - thank you. Started integrating alerts - and it appears alerts are coming in as integers values rather than mapped to their meanings. In the admin UI - they show correctly: However - in UDI Mobile they show as integers: I am noticing that when using NR substitutions, it's the integers that come thru. For instance, this pushover payload: priority=-1&retry=30&expire=3600&sound=none&message=${sys.node.#.GV21:url}+(${sys.node.#.GV23:url})+severity+${sys.node.#.GV25:url}+and+urgency+${sys.node.#.GV26:url}+and+certaincy+${sys.node.#.GV27:url}) This morning resulted in: Is it possible to take a look and fix the mappings in the poly? Thank you! Michael.

Good to know - thank you!

Update: *MUCH* better. Polys all started. Problem looks solved. Still don't know why the admin console update did things beyond the pkg package manager. Thank you @bpwwerfor the solution!

Interesting. I had not been doing this - rather 'pkg update && pkg upgrade' at the cli. Opening the admin console - I hit this button and immediately the admin console (and finder) closed. As if it crashed. Thru SSH - I was watching /var/log/messages and nothing. After a few mins - I started the admin console again - and all of a sudden I see events like this in /var/log/messages: Sep 25 13:38:04 polisy pkg[4779]: FreeBSD-runtime-13.0p11 deinstalled Sep 25 13:38:08 polisy pkg[4779]: FreeBSD-utilities-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libbsdxml-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libregex-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libregex-dev-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-utilities-dev-13.0p11 deinstalled Sep 25 13:38:09 polisy pkg[4779]: FreeBSD-libbsdxml-dev-13.0p11 deinstalled Sep 25 13:38:14 polisy pkg[4779]: FreeBSD-runtime-13.1p2 installed Sep 25 13:38:14 polisy pkg[4779]: FreeBSD-libmagic-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-runtime-dev-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-rc-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-liblzma-13.0p11 deinstalled Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libthread_db upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libbsm upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libsmb upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libbsdstat upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:15 polisy pkg[4779]: FreeBSD-libucl upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-bluetooth upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libvgl upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libcuse upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:16 polisy pkg[4779]: FreeBSD-libarchive upgraded: 13.0p11 -> 13.1p2 Sep 25 13:38:19 polisy pkg[4779]: FreeBSD-openssl-13.1p2 installed Sep 25 13:38:19 polisy pkg[4779]: FreeBSD-libmagic-13.1p2 installed ..... I suspect these are the dependencies being spoke of (at some point I did earlier see a 'running kernel mismatch' error). At the end of the upgrades - Polisy auto-rebooted: Sep 25 13:40:02 polisy reboot[5956]: rebooted by admin

No updates yet: Should I be expecting to see something thru the 'pkg update && pkg upgrade' process?

During the last 'pkg upgrade' - the following got updated: Sep 23 20:33:05 polisy pkg[2395]: python39 upgraded: 3.9.13 -> 3.9.14 Since then, I see this error when most PG3 Polys start (as well as having similar issues identified in this thread - high latency on zwave devices for example): 9/25/2022, 11:06:13 [pg3] error: [LiFX(6)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found I have a feeling that a missing Python dependency like this might affect a lot more than just polys running. libpython3.9.so.1.0 was updated from the UDI package server - but libc.so.7 should likely have also been updated to be conformant is it does not appear this was the case from the logs.

More from the log - during a reboot: 9/25/2022, 11:06:13 [pg3] error: [Sonos(14)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] debug: [Sonos(14)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] info: startNs:: Sonos starting polls 9/25/2022, 11:06:13 [pg3] info: Starting Node server Info timer 0 9/25/2022, 11:06:13 [pg3] error: [Timedata(9)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [ELK(10)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [LiFX(6)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Sun(11)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Ping(8)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [Plex-WebHook(12)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [WirelessTag(4)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [NOAA(5)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [UnifiPresence(15)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [MQTT(13)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] error: [WeatherFlow(7)] :: STDERR: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found 9/25/2022, 11:06:13 [pg3] debug: [Timedata(9)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [ELK(10)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [LiFX(6)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Sun(11)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Ping(8)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [Plex-WebHook(12)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [WirelessTag(4)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:13 [pg3] debug: [NOAA(5)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [UnifiPresence(15)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [MQTT(13)] :: Exit cause code: 1 - signal: null 9/25/2022, 11:06:14 [pg3] debug: [WeatherFlow(7)] :: Exit cause code: 1 - signal: null Looking at everything that updated a couple of days ago: I tried reverting pg3 and udx - but this did not resolve the issue at all. I have a feeling there is a missing dependency in the updated python39.

Maybe a bug in FreeBSD? Or the update process? https://forums.freebsd.org/threads/version-fbsd_1-7-required-by-usr-local-lib-libpython3-9-so-1-0.86449/ Not sure if Polisy is using jails - so don't want to 'try' the workaround without guidance.