Bumbershoot

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

It's doubtful you could modify the software legally to run on FreeBSD: According to the EULA, you are not permitted to: Edit, alter, modify, adapt, translate or otherwise change the whole or any part of the Software nor permit the whole or any part of the Software to be combined with or become incorporated in any other software, nor decompile, disassemble or reverse engineer the Software or attempt to do any such things Reproduce, copy, distribute, resell or otherwise use the Software for any commercial purpose Allow any third party to use the Software on behalf of or for the benefit of any third party Use the Software in any way which breaches any applicable local, national or international law Use the Software for any purpose that Solar Assistant Software considers is a breach of this EULA agreement

The absolute fastest way for a light to react to motion captured by an Insteon motion sensor is to use a scene. A program will always be slower, as the ISY has to receive the motion event, then run the THEN stanza in the program to send a command to the lights. With the scene, the ISY isn't involved other than being notified of the device status. I've found that the delay you're experiencing is normal when using a program instead of a scene.

There's nothing that the last commands (sudo pkg update && sudo pkg upgrade) you ran that would bork your Polisy, or everyone who's up to date would find that their Polisy is borked as well. Are your automations working? If you have the UDI Portal, does your Polisy show up as online? Is one green LED lit on the front of your Polisy? If the answer to any of these is yes, then make sure that the IP address didn't change on your network. Otherwise, unplug your Polisy, wait a minute, plug it back in and see if it comes alive normally. If it doesn't, then file a support ticket with UDI. BTW, the command: `sudo shutdown -r now` is a reboot command. No need for the additional reboots.

I've have a dimmer, and used the node "Motion Sensor 1" in the "If" stanza, and it works. I haven't tried it with the relay switch, but it has the same nodes, so I suppose it works. Office Notification - [ID 0124][Parent 000F] If From 8:00:00AM on 2022/06/13 To 5:00:00PM on 2022/06/17 And 'Devices / dirOffice / ZW 009 Office Motion Switch / ZW 009 Motion Sensor 1' Status is On Then Send Notification to 'Notify' content 'Office Light On' Else - No Actions - (To add one, press 'Action')

This doesn't look right. When I grep through my logs I see the same thing, only the "Port" value is 3000

@JTsao, I've been using the Push Node server on both PG2 and now PG3 successfully. Did you set the "disclaimer_read" option to "true" in your configuration, and restart the Node server?

@maxnorth, there's an alternative solution to getting local air quality data into your ISY via a PG3 node server that doesn't rely on a cloud based API, for what it's worth. The setup will cost you much more than the $5.00 license for the PG3 Purple Air, so it may be of no interest, but it's been working well here (actually, I bought this setup for the soil moisture sensors, and added this sensor later when I was choking on wildfire smoke). I've found that I prefer a local measurement over one from across town, or even down the block -- there's too much variability in air quality. The PG3 node server is ST-EcoWitt, and it takes two hardware devices to make it work: https://www.ecowitt.com/shop/goodsDetail/107 https://www.ecowitt.com/shop/goodsDetail/58 The sensor is solar powered, so the only times I've ever had to recharge the batteries is when it's been buried in the snow for a couple of weeks. I've found that the RF signal strength for all the EcoWitt devices to be very good (I have devices scattered all over the 1/2 acre). Attached is a screenshot of what the data looks like in the ISY:

@TriLife, one more thing about the early Polisy machines: I got one of those, and OS image that was burned to the storage media was set up with only 4GB of file storage. I had to send mine back to UDI to have another OS image flashed onto the storage media. If you're familiar with secure shell and know how to log into your Polisy using it, then run this command at the command line: df -h You should get output that looks something like this: [admin@polisy ~]$ df -h Filesystem Size Used Avail Capacity Mounted on zudi/ROOT/default 24G 2.1G 22G 8% / devfs 1.0K 1.0K 0B 100% /dev procfs 4.0K 4.0K 0B 100% /proc zudi/var/isy 10G 18M 10G 0% /var/isy zudi/var/empty 22G 24K 22G 0% /var/empty zudi/tmp 22G 29K 22G 0% /tmp zudi/var/crash 22G 24K 22G 0% /var/crash zudi/usr/home 22G 37K 22G 0% /usr/home zudi 22G 24K 22G 0% /zudi zudi/var/log 22G 507K 22G 0% /var/log zudi/var/tmp 22G 24K 22G 0% /var/tmp zudi/var/run 22G 42K 22G 0% /var/run zudi/var/db 22G 166M 22G 1% /var/db zudi/var/db/pkg 22G 11M 22G 0% /var/db/pkg zudi/var/polyglot 10G 432M 9.6G 4% /var/polyglot If you only see 4G available in 'zudi/ROOT/default', then you're going to need some assistance from UDI.

It may not be as easy to install WiFi and Bluetooth on a Polisy as it is on a typical Linux box. If you're experienced with FreeBSD, then you might get it done, but for most folks, no. I bought a Polisy Pro, simply so I could turn on WiFi, move the Polisy from it's normal location, placing it close to some installed Z-Wave devices in order to include them into my Z-Wave installation securely. Normally, my Polisy uses a wired ethernet connection. For the handful of times I've turned on the WiFi and moved the Polisy close to a Z-Wave device, it was completely worth the few extra $$ to have that capability. So far, I don't think Bluetooth on Polisy is implemented.

@jukeman, the solution is to run Polyglot on a local installation (Raspberry Pi, or better, a Polisy). Here's a list of the available node servers, and quite a few are related to Weather. Openweathermap is available on Polyglot v3 with a perpetual license for $5.00 (free on Polyglot v2). Polyglot v3 is the current, supported version of Polyglot, and it only runs on a Polisy. I have no information as to whether Polyglot Cloud will be rebuilt or not. If you're unfamiliar with Linux, running Polyglot v2 from a Raspberry Pi might be a bit daunting. I think the best solution (though not the cheapest) would be to purchase a Polisy from Universal Devices and consider migrating your installation to that platform - in the short term, you could use a Polisy to simply run Polyglot v3 while you consider your migration path from the ISY994. The ISY994 is supported still, but it isn't the current platform for Universal Devices.

Thank-you @bpwwer, I’m back in business! On a Sunday evening, no less!

I'll give you some time before I panic and make a mess of things... ?

Here are the packages that were updated: The following 4 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: node: 17.0.1_1 -> 18.2.0 [udi] npm: 8.10.0 -> 8.12.1 [udi] py38-pip: 22.1.1 -> 22.1.2 [udi] py38-setuptools: 57.0.0 -> 62.1.0 [udi] Here are the Pg3 logs after the update (this pattern continues every few seconds): 6/5/2022, 15:00:29 [pg3] info: Starting PG3 version 3.0.62 6/5/2022, 15:00:29 [pg3] info: Using Workdir /var/polyglot/pg3/ 6/5/2022, 15:00:29 [pg3] debug: Created PID file: /var/polyglot/pg3/pg3.pid 6/5/2022, 15:00:32 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: udi_interface in /var/polyglot/.local/lib/python3.8/site-packages (3.0.46) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: netifaces in /usr/local/lib/python3.8/site-packages (from udi_interface) (0.11.0) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: python-dotenv in /var/polyglot/.local/lib/python3.8/site-packages (from udi_interface) (0.20.0) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: pyisy!=2.1.5,<3.0.0,>2.0 in /var/polyglot/.local/lib/python3.8/site-packages (from udi_interface) (2.1.4) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: markdown2 in /var/polyglot/.local/lib/python3.8/site-packages (from udi_interface) (2.4.3) Requirement already satisfied: paho-mqtt in /var/polyglot/.local/lib/python3.8/site-packages (from udi_interface) (1.6.1) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: requests in /usr/local/lib/python3.8/site-packages (from pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (2.27.1) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: python-dateutil in /usr/local/lib/python3.8/site-packages (from pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (2.8.2) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.8/site-packages (from python-dateutil->pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (1.16.0) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.8/site-packages (from requests->pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (1.26.9) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.8/site-packages (from requests->pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (2022.5.18.1) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: charset_normalizer~=2.0.0 in /usr/local/lib/python3.8/site-packages (from requests->pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (2.0.12) 6/5/2022, 15:00:33 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.8/site-packages (from requests->pyisy!=2.1.5,<3.0.0,>2.0->udi_interface) (3.3) 6/5/2022, 15:00:35 [pg3] debug: NSChild: PythonInterface /usr/local/bin/pip3 install udi_interface --user: exited with cause code: 0

For the price we paid for it, that's all reasonable. I hope the node server gets updated down the line, and I'd be happy to throw a few $$ at it if it does. The response of the lights to motion is almost instantaneous, and the coordination between lights in a room reminds me of an Insteon scene, only more colorful.

Thank-you! I mis-understood what the profile was for. The name/password have been changed in both IoP and PG3 and all appears to be well.

Okay, I changed username/password on the ISY, then changed the username/password (using the Profile tab to the same values as on IoP) on PG3. PG3 logged me out and restarted. Upon restart, and re-logging in using the new username/password values, I get what you see in the screenshot. I see this in the log: 5/31/2022, 16:28:30 [pg3] error: Error: GET http://192.168.1.19:8080/rest/ns/5/nodes/n005_wh41_1/report/status/BATLVL/0/25 Failed :: 401 5/31/2022, 16:28:30 [pg3] error: Error: GET http://192.168.1.19:8080/rest/ns/5/nodes/n005_wh41_1/report/status/GV1/3.8/54 Failed :: 401 Also, strangely I can successfully log into PG3 using the old username/password, and the dashboard shows up, but values are not being updated in the IoP. Changed the IoP username/password back to the original values, restarted PG3 and data is once again being updated in the IoP.

I'll take another whack at this and report back. The password was changed to one that I used successfully in the ISY994, and the username was changed to four letters, all lower case.

Two questions about the PG3 node server: 1) is the Hue motion sensor supported/exposed as a Polyglot node currently, and if no, could it be? 2) is v2 of the Hue API currently supported, and if no, will it be? For a new project, I'm looking at using the Hue motion sensor to activate a light strip underneath a bathroom vanity. I could easily get things to work properly just by setting this up using the Hue app, but of course, I'd also like to make use of other properties of the motion sensor, such at temperature, in IoP. So far, I haven't had any luck with the node server discovering the sensor. Regarding the API question, I'm just trying to estimate the longevity of the node server. It appears that the PG2 version is built on v1 of the API.

The reason I asked above is because I ran into this issue. I changed the user/password in IoP, and PG3 became really cranky. I changed the user/password on PG3 to match, but things didn't improve. I changed the user/password in IoP and PG3 back to what they were originally, and things came back to life.

Brilliant! With the demise of Insteon, this has to be the right direction to take!

For general community information, do you have an idea of how he fixed this? Did he just change the password back to what it was previously?

In the "ISYs" tab of PG3, does your IoP or ISY show up with a ✔️ by the correct device?