Bumbershoot

Michel indicated that there could be corruption of the /etc/passwd file if the updates weren't done in a specific order (which is what using the "Upgrade Packages" button on the AC sorts out for us). I don't think this is a problem specific to FreeBSD at all (there are no new entries in the FreeBSD bugzilla site for 'passwd'), but something specific to what UDI is doing on their implementation.

My Polisy beeps a total of six times - one long, followed by five short - I suspect that means something such as everything is up to date. Some update status in the AC would be useful. The beeps are hard to hear for me as well.

In this thread just the other day: I can't help with the second part of your question.

Not that button. He means the button on the Configuration tab of the AC.

That's easy enough to understand. That'll be my new practice.

Did you have the BIOS updated to EUFI on your primary Polisy prior to the last software update (seems sensible that EUFI wouldn't have been installed on your backup machine quite yet)? I wonder if there's a issue with the newest packages from UDI and a BIOS that hasn't been upgraded... I've got my Polisy running the latest/greatest FreeBSD release from UDI, with all the packages updated, BIOS updated to EUFI and TPM running, and it's running fine. I'd think there would be hundreds of boxes down if somehow the FreeBSD updates were broken is some way. I hope someone does report the issue. Very curious about this one. Would you please update the thread with the resolution? Thanks.

Open a support ticket.

I think you’ve filled up your disk with the updates. If you get in, run ‘sudo pkg clean’ which will clear the package cache. Check your disk space with ‘df - h’ and if you only have 4gb of total space, you have an early Polisy. UDI needed to reflash the OS on the disk to make much more space available.

This sounds like all the updates filled all your disk space. My Polisy shipped with only a 4gb partition, and a few large updates filled it up, leaving the Polisy to present similar symptoms. After a few hours of letting it sit, I was able log in, and I ran the command ‘sudo pkg clean’, which solved the problem.

IoP (ISY on Polisy) is indeed software that's running on an independent OS (FreeBSD, in this case). In my limited experience, any BSD variant OS is very solid, probably about as robust an OS as you're going to get in any consumer device, though it's not necessarily built for user friendliness. PG3 (Polyglot v3) will only run on a Polisy, and the older PG2 software is depreciated. If you want to move forward with node servers into the future, then PG3 will be the way to go. So a Polisy will be required. Polyglot Cloud isn't running any longer due to security considerations. I don't know what the future for that platform is. Polisy will support all devices that the ISY will (PG2 will run concurrently with PG3 on your Polisy -- not all node servers have been ported to PG3 as of yet). Here's a list of PG2 an PG3 node servers that are available: https://polyglot.universal-devices.com All ISY software development will occur on the Polisy, not the ISY. The ISY platform itself is deprecated. The Polisy is a much more capable computing machine, and you're unlikely to run into limitations regarding the size of your installation with a Polisy. Wi-Fi works on the Polisy Pro if you need it. I don't believe that Bluetooth is utilized as of yet, though I may be wrong. UDI will soon release a much improved Z-Wave/Matter interface on the Polisy, so Z-Wave series 7 and beyond are and will be supported on the Polisy. Not so for the ISY, which will stay at Z-Wave series 5.

If the Wi-Fi interface has got the IP and MAC addresses populated, you should be able to unplug the ethernet cable. You may have to reboot the Polisy to get the Wi-Fi address to become active (I don't recall, but I had to reboot it anyway to move it around to various locations). Below is the Wi-Fi interface in PG2 prior to activating the interface. I reserved an IP address for Polisy Wi-Fi in my routers address reservation table for future use.

I used the Wi-Fi interface when I was setting up some previously installed Z-Wave devices. I didn’t want to have to dismantle door locks, etc. to get them close enough the Polisy for inclusion, so I just turned on the Wi-Fi and moved the Polisy close to the devices. The interface for turning on the Wi-Fi isn’t all that intuitive, but it works once you figure it out.

@ronlovetri, you have to go to the Security & Privacy icon within an hour after you tried to open the app by the unidentified developer. Have a look at this link: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac

Open System Preferences, and click on the Security and Privacy icon, General tab. You should be able to allow 'start.jnlp' from there.

It appears that upgrading udx to version 3.0.5 and rebooting the Polisy solved this issue for me. I see that the link to pip3 has been reestablished to point to the new version of pip (pip-3.9).

Upgrading udx to 3.0.5 and rebooting the Polisy solved this issue.

Upgrading udx to 3.0.5 and rebooting the Polisy solved this issue.

It looks like the upgrade of the udx file to version 3.0.5 and a Polisy reboot solved this issue. I also unlinked pip3, but it looks like it got relinked properly to /usr/local/bin/pip-3.9, so I imagine that the udx upgrade made that new link. Probably not necessary to unlink it at the command line...

Here's the log: 2022-06-28 14:25:57,900 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-06-28 14:26:00,594 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting... 2022-06-28 14:26:00,600 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-06-28 14:26:00,601 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_10/./lifx-poly.py", line 10, in <module> 2022-06-28 14:26:00,602 MainThread udi_interface ERROR udi_interface:write: import lifxlan 2022-06-28 14:26:00,603 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-06-28 14:26:00,604 MainThread udi_interface ERROR udi_interface:write: : 2022-06-28 14:26:00,604 MainThread udi_interface ERROR udi_interface:write: No module named 'lifxlan'

Here's the log: 2022-06-28 14:21:24,639 MainThread udi_interface ERROR udi_interface:write: No module named 'pyflume' 2022-06-28 14:24:53,846 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-06-28 14:24:56,392 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting... 2022-06-28 14:24:56,404 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-06-28 14:24:56,405 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_8/./flumewater-poly.py", line 4, in <module> 2022-06-28 14:24:56,406 MainThread udi_interface ERROR udi_interface:write: from nodes import Controller 2022-06-28 14:24:56,407 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_8/nodes/__init__.py", line 5, in <module> 2022-06-28 14:24:56,408 MainThread udi_interface ERROR udi_interface:write: from .Flume2 import Flume2Node 2022-06-28 14:24:56,409 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_8/nodes/Flume2.py", line 6, in <module> 2022-06-28 14:24:56,410 MainThread udi_interface ERROR udi_interface:write: import pyflume 2022-06-28 14:24:56,411 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-06-28 14:24:56,412 MainThread udi_interface ERROR udi_interface:write: : 2022-06-28 14:24:56,413 MainThread udi_interface ERROR udi_interface:write: No module named 'pyflume'

Here's the log: 2022-06-28 14:21:26,968 MainThread udi_interface ERROR udi_interface:write: No module named 'elkm1_lib' 2022-06-28 14:25:42,871 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-06-28 14:25:45,634 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting... 2022-06-28 14:25:45,655 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-06-28 14:25:45,656 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_15/./elk-poly.py", line 10, in <module> 2022-06-28 14:25:45,658 MainThread udi_interface ERROR udi_interface:write: from nodes import Controller 2022-06-28 14:25:45,659 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_15/nodes/__init__.py", line 4, in <module> 2022-06-28 14:25:45,660 MainThread udi_interface ERROR udi_interface:write: from .Zone import ZoneNode 2022-06-28 14:25:45,661 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_15/nodes/Zone.py", line 6, in <module> 2022-06-28 14:25:45,663 MainThread udi_interface ERROR udi_interface:write: from elkm1_lib.const import ( 2022-06-28 14:25:45,663 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-06-28 14:25:45,664 MainThread udi_interface ERROR udi_interface:write: : 2022-06-28 14:25:45,665 MainThread udi_interface ERROR udi_interface:write: No module named 'elkm1_lib'

Not here. I'm on 5.4.4 and things are fine. Maybe a reboot of the ISY software might help?

You might read through this thread:

Correct, they are. I'm using both of them (Z-Wave stick and USB PLM).

Not knowing what you're looking to do, there is some programmatic flexibility with the scene. They can be modified by the "adjust scene" functionality if necessary. Below is an example of where I adjust a scene for differing on-levels based on time (using the latest/greatest ISY firmware): West Hall On-Level - [ID 00B7][Parent 000A] If From Sunset + 1 hour To Sunrise (next day) Then In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 25% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 25% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 25% in 0.5 seconds, 1 retry Else In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 50% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 50% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 50% in 0.5 seconds, 1 retry