Bumbershoot

@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?

I assume you've done the following two things: 1) pressed the round button on the Hue Bridge 2) restarted the Hue Node server within 30 seconds of when you pressed the button Additional nodes should start appearing in the PG3. You may need to try this more than once (I believe it took several tries in my case). You might have to specify an IP address for the Hue Bridge (I just set a static IP reservation for it in my WiFi).

I find this to be a remarkable statement. To me, this represents a fairly quick turnaround from the initial direction UDI was taking with Z-Wave on Polisy (Zooz 700 dongle with migrated ISY994 code/functionality), to a new dongle with all the advanced Z-Wave 700 features and Matter included to boot... I don't follow developments in the Z-Wave/Matter world at all, but it makes me wonder if there aren't libraries of code for Z-Wave/Matter now available that meet UDI's licensing/pricing requirements -- after all, they chose FreeBSD for Polisy, no doubt at least somewhat due to it's license/price. Either that, or UDI has been very busy rewriting... If the new code is proprietary, then good for UDI for getting this done! If it's somehow in the public domain or otherwise available, then good for the industry as a whole! Either way, I'm excited and relieved.

I don't know if folk on this thread have seen this comment:

Have a look at this thread:

That’s true, for now.

It's on Polyglot Cloud, which is shut down currently due to security problems. I don't know if Polyglot Cloud is being rebuilt, or if the node servers that only run on it, like Ring, will be ported to PG3.

Connection refused? The device at this address is a Sonos Playbar. There was a firmware update applied yesterday (5/24), but the playbar has been in use and has been operating normally after the update. This error occurred what another set of speakers was activated using Alexa. Things are back to normal with the Node server after a restart. 2022-05-24 08:57:05 error: NS: uncaughtException REPORT THIS!: Error: connect ECONNREFUSED 192.168.1.4:1400 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) 2022-05-24 08:57:05 error: POLY: uncaughtException: connect ECONNREFUSED 192.168.1.4:1400 Error: connect ECONNREFUSED 192.168.1.4:1400 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) 2022-05-24 08:57:05 error: NS: uncaughtException: connect ECONNREFUSED 192.168.1.4:1400 Error: connect ECONNREFUSED 192.168.1.4:1400 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)

I've got EUFI which supports TPM boot, whereas BIOS does not. I'll bet if my Polisy was still had BIOS then the 'Upgrade BIOS' button would be active and the "Enable TPM" button would be greyed out. There was a new UDX file that came with this release. Maybe the dependence on MongoDB is gone?

Looks to me like UDI is getting rid of the dependence on PG2 for Polisy maintenance with this release: