Bumbershoot

My PXGx version is 3.3.18. This host FreeBSD version that IoX runs on should be as below: [admin@eisy ~]$ uname -a FreeBSD eisy 14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 #4 releng/14.1-n267727-74b6c983723c-dirty: Fri Nov 15 12:13:25 PST 2024 root@bsdev14.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64

In my experience, that's unusual. Given the proximity of the UDI office to the fires in LA, UDI staff might have an awful lot to cope with.

For LiFX: Likely you need to install the development packages (on the Configuration tab in the AC, click on the button labeled "Install Dev. Packages"). After that completes (it should take a while), you will likely have to uninstall the LiFX node server and reinstall it using the same slot it was uninstalled from. Use the search term "lifxlan" and you'll find several threads on this issue. I know nothing about Roomba, but maybe it's a similar issue.

If memory serves me correctly, the original 300 Series Board had a green LED on the board, which was eliminated on the 500 Series Board. I believe the LED was visible when the board was installed as well. Here's a photo of the 500 Series Board.

@Guy Lavoie, @BobM99, @Techman, @Pmool, @joepoway, @Geddy, @TheA2Z, et al -- Michel responded to my ticket last night (at roughly 10:00 pm Pacific), and the fix worked, so I'm back in business. According to the log, it appears that there was an update to the ISY 5.8.4_1 software. Please reboot using the following method: 1. Press/hold power button -> red 2. Click again -> blue

Same here. I'm on 5.8.4_1 after updating yesterday afternoon. Same symptoms as yourself, @joepoway and @BobM99.

@CJVann and @rg65, I just came across this post. It appears that this switch operates the same as the earlier HS-WD200 series switches. If you're still looking to perform the last two operations on the list above, then have a look at this old thread on the 200 series dimmers. You'll have to write programs that set various parameters, and it gets complex fairly quickly with all the LED blink and color possibilities, but it's a fun project if you like this sort of thing.

Sorry I didn't see this earlier, but I had exactly the same issue. Easily resolved.

This issue is resolved. For whatever reason, the install wasn't pointed at the latest repositories. A simple file edit, reboot of the eisy and a reinstallation of the plugins resolved it.

I'm on eisy, and it appears that I must have a missing Python repo or something, as I have a bunch of messages in the log such as these: Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'py311-pip' have been found in the repositories Fri Jun 28 16:03:41 PDT 2024|/usr/local/etc/udx.d/static/udx_startup.sh: Installing pkg py311-pycryptodome Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'py311-pycryptodome' have been found in the repositories Fri Jun 28 16:03:44 PDT 2024|/usr/local/etc/udx.d/static/udx_startup.sh: Installing pkg py311-yaml Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'py311-yaml' have been found in the repositories Fri Jun 28 16:03:47 PDT 2024|/usr/local/etc/udx.d/static/udx_startup.sh: Installing pkg py311-dateparser Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'py311-dateparser' have been found in the repositories EDIT: This issue is resolved. The problem was related to file repositories that were out of date. The RainMachine plugin is now running as intended.

FWIW, all of my Python based plugins aren’t running after the upgrade, including RainMachine.

Rebooted, with no change. Oddly, all the plugins reinstall with every reboot.

I did wait, yes. I think I’ll give another reboot and see what happens.

Something janky happened with my plug-ins post upgrade — only two of twelve will restart — Ecowitt and ST-Sonos. I’ve tried reinstalling all of them to no avail. No doubt Python related?

@kzboray, I'm not currently using this plugin so I can't verify, but is this issue still relevant if you're making a static IP reservation?

It runs fine on Sonoma with an M1 chip.

You have to have a hub. Yolink uses LoRa, which isn't included in the Z-Matter dongle, so you have to have a hub.

Nope, I used their Garage Door Controllers with Garage Door Sensors. My garage door openers are original with the house, which was built in 1999. They've worked perfectly.

+1 on Yolink. I scrapped my Z-Wave garage door openers for Yolink, and I'm very pleased with them. I've recommended them to others as well, and I've had no negative feedback at all.

Yes it is, and it works (though not as elegantly as an Insteon scene). Here's a good thread describing how to set this up:

Venstar ColorTouch 5200 WiFi Yes, there's a plugin, and it works well $10.95 perpetual license Open API, so no cloud connection necessary. There is a Venter app available along with a free cloud account with Venstar if you wish to control the thermostat remotely without using your UDI Mobile app. You can set up a geofence in the Venstar app should you like. The thermostat works very well, it supports remote temp sensors, and I've had zero issues with it. The GUI isn't terribly responsive, but I almost never use it. It's attractive enough so that the Mrs. doesn't ever mention it.

After a remodel and upgrades from i994 > Polisy > eISY, I had this issue crop up as well. I don't know what caused this, but these *.REC files were related to Insteon devices that somehow had lost their attributes/data in the ISY software (these files were 0 byte files). The devices still operated normally, but I could not backup the ISY software, etc. In my case, the devices associated with these files -- example: file 57722B0.REC will be associated with the Insteon device 57.72.B0 -- had files to be be deleted from the ISY, the devices factory reset then re-added in the ISY. After that, I had to recreate the scenes these devices belonged to, but I recall the programs still worked. Now, my ISY software operates as intended. This is a hack, and I have no idea if this is what UDI would do to resolve this issue. If your'e not comfortable with UNIX shell commands, then I'd open a ticket with UDI and let them have a go at fixing this.

I bought three Ring outdoor stickup cameras at Costco years ago, and they work very much like the Ring doorbell regarding motion detection. The Ring Polyglot plugin works just fine, though there was a time when it wasn't functional. I hope those days are past...

From the unsuccessful discovery: 2023-12-26 12:41:52,890 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-12-26 12:41:52,892 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Attempting manual discovery... 2023-12-26 12:41:53,032 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-26 12:41:53,150 Thread-6 udi_interface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2023-12-26 12:41:53,170 Thread-6 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-26 12:41:53,170 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-1 Mini 519C71(d073d5599c71) And from the successful discovery: It appears to me that the unsuccessful discovery is missing a few MQTT entries in the log just after discovery begins (they do occur at the end of the log snippet), and it finishes much faster. It's almost as if the discovery process continues before some MQTT process is completed. I hope this is an issue that's fixable...

These directories were created by UDI with some restrictive permissions, so try this command (substituting your directory names): [admin@eisy /var/polyglot/pg3/ns]$ sudo ls -altF 0021b9026016_8/ Results below: [admin@eisy /var/polyglot/pg3/ns]$ sudo ls -altF 0021b9026016_8/ total 89 -rw-r--r-- 1 root polyglot 5 Dec 26 05:22 test.txt drwxrwx--- 8 0021b9026016_8 polyglot 27 Dec 26 05:17 ./ drwxr-xr-x 2 0021b9026016_8 polyglot 17 Dec 26 03:02 logs/ -rw------- 1 0021b9026016_8 polyglot 5 Dec 21 08:59 0021b9026016_8.pid -rw------- 1 0021b9026016_8 polyglot 5 Dec 21 08:59 0021b9026016_8_daemon.pid drwxr-xr-x 14 polyglot polyglot 14 Dec 17 11:27 ../ -rw-r--r-- 1 0021b9026016_8 polyglot 10 Oct 22 05:12 .installed -rw-r--r-- 1 0021b9026016_8 polyglot 6157 Oct 22 05:12 pip.log -rw-r--r-- 1 0021b9026016_8 polyglot 8961 Oct 22 05:12 install.log drwxr-xr-x 8 0021b9026016_8 polyglot 14 Oct 22 05:11 .git/ -rw-r--r-- 1 0021b9026016_8 polyglot 173 Oct 22 05:11 git.log -rwxrwx--- 1 0021b9026016_8 polyglot 1245 Oct 22 05:11 0021b9026016_8.cert* -rwxrwx--- 1 0021b9026016_8 polyglot 1679 Oct 22 05:11 0021b9026016_8.key* drwxr-xr-x 4 0021b9026016_8 polyglot 4 Feb 21 2023 .local/ drwxr-xr-x 3 0021b9026016_8 polyglot 3 Feb 21 2023 .cache/ -rwxr-xr-x 1 0021b9026016_8 polyglot 67 Feb 21 2023 zipprofile* -rw-r--r-- 1 0021b9026016_8 polyglot 777 Feb 21 2023 server.json -rw-r--r-- 1 0021b9026016_8 polyglot 82 Feb 21 2023 requirements.txt drwxr-xr-x 5 0021b9026016_8 polyglot 6 Feb 21 2023 profile/ -rwxr-xr-x 1 0021b9026016_8 polyglot 58868 Feb 21 2023 lifx-poly.py* -rwxr-xr-x 1 0021b9026016_8 polyglot 60 Feb 21 2023 install.sh* -rw-r--r-- 1 0021b9026016_8 polyglot 279 Feb 21 2023 README.md -rw-r--r-- 1 0021b9026016_8 polyglot 661 Feb 21 2023 POLYGLOT_CONFIG.md -rw-r--r-- 1 0021b9026016_8 polyglot 1068 Feb 21 2023 LICENSE -rw-r--r-- 1 0021b9026016_8 polyglot 913 Feb 21 2023 .gitignore drwxr-xr-x 3 0021b9026016_8 polyglot 3 Feb 21 2023 .github/ -rw-r--r-- 1 0021b9026016_8 polyglot 12 Feb 21 2023 .gitattributes [admin@eisy /var/polyglot/pg3/ns]$ sudo ls -altF 0021b9026016_8/ This is my LiFX directory (it's in slot 8). The very first file listed is 'test.txt', which is the file I created, and edited with the 'nano' text editor. You won't be able to 'cd' into the specific node server directories, so you'll have to stay in '/var/polyglot/pg3/ns' to do your work. Tip: in UNIX shells, you have a nifty feature called file name completion. It saves lots of time/typing complicated directory and file names. It's activated in the shell using the tab key. Try this command (using my example directory above}: sudo ls -altF /var/polyglot/pg3/ns/[tab key]8/ I don't have to type out '0021b9026016_' every time I want to use that directory name, as file name completion will automatically insert it into the command line, stopping at the first character that all those directories don't have in common, with is the character immediately following the '_'. Saves loads of typing, but it'll take a bit of practice to get familiar with it.