Bumbershoot

I'm on the latest/greatest from UDI, and I've never had the duplicate issue. I upgraded to get the new API, had a problem with the Ambience white bulbs not showing up as nodes, so I did a few install/uninstall cycles as the plugin was updated. Once the issue was fixed, I had to resave the programs that referenced the bulbs, and things have been good since. The plugin has worked both on the trial and standard (paid) versions (1.0.6 and 1.0.7). Having access to the Hue motion sensor is a nice benefit of the upgrade -- the response seems fast, pretty much on par with an Insteon motion sensor. Looking at my debug log for the plugin, I'm not seeing any errors.

FWIW, I upgraded to 1.0.7 and everything appears to be good. No duplicates.

No, it's okay for my purposes, as I won't use that value in any useful way. I have a leftover WeatherFlow Air unit about fifteen feet away from this sensor that I use for home automation purposes/reporting. The motion sensor looks to be interesting. With early testing, the response to motion appears to be really fast.

I got the three new nodes, all populating. The temperature shows as Celsius, and I'm in Fahrenheit territory. Any way to change it?

Looks like that took care of it. Now nodes for all 11 bulbs have been created, are showing status and are controllable. Thanks!

Okay, it's partially working. The issue I have now is that the plugin only creates nodes for 4 bulbs, when I have 11 installed. When I toggle the bulbs with the Hue app, an entry appears in the debug log, but no node is created. This is repeatable upon several uninstall/install cycles, along with several hub button presses/restarts. Debug log attached. Hue_10-23-2025_30607_AM.zip

I think I might be running into a similar problem with the Ambience White bulbs. Attached is a zipped log file. Hue_10-22-2025_14248_PM.zip

Seems to be the case here as well. No status for devices...

Apologies for not reporting this earlier (been away), but I get a "Network Error" when I use Safari (version 26) to log into eisy-ui, but for some reason, it works with Firefox (version 142). This occurred with the previous Safari version as well. My version of eisy-ui is 0.6.0, but this happened on 0.5.9. This is on an iMac running the latest Tahoe beta, but it also happened on the last Sequoia release. The DuckDuckGo browser reports a TLS error that prevents the page from loading.

I've had the occasional restart of the ISY software, but it hasn't happened in a month. It restarts on its own. See the last entry on April 5. This log snippet if from /var/udx/logs/log. Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: no packages need upgrading ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: cleaning up old/unused files ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: deleting old log/debug files ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: generating sysconfig report ... Sat Apr 5 03:03:35 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: **** Finished Running UDX Daily Tasks **** Sat Apr 5 06:40:17 PDT 2025|/usr/local/etc/udx.d/static/udx_svc_supervisor: isy failed ... restarting now! Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: wifi.ops is not being called as a comamnd Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: **** Running UDX Daily Tasks **** Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: pkg.conf already has IGNORE_OSVERSION ... Sun Apr 6 03:55:27 PDT 2025|/usr/local/etc/periodic/daily/udx_tasks: checking for updated packages ...

If you don't want to create multiple scenes, you can do this using the "Adjust Scene" function, though it takes a program to initiate the change. You can toggle the "On Level" value between a fixed % or the value of an Integer variable. I believe that you have to adjust the "On Level" of every device in the scene in the initiating program. The program below simply sets the devices to a fixed % instead of to a variable, but the screenshot shows how to select a variable for the "On Level" in the AC. This program takes a few seconds to run as it writes/updates the three Insteon switchlincs to the proper "On Level", but the scene itself reacts instantly to the "Fast On" as you would expect. WestHallManualOverrideOn - [ID 0005][Parent 000A] If 'Devices / dirWestHall / sldWestHallEntrance' is switched Fast On Or 'Devices / dirWestHall / sldWestHallLaundry' is switched Fast On Or 'Devices / dirWestHall / sldWestHallOffice' is switched Fast On Then Set 'Scenes / scnWestHallLights' Fast On In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 100% in 0.1 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 100% in 0.1 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 100% in 0.1 seconds, 1 retry Disable Program 'WestHallOnOff' Wait 4 hours Run Program 'WestHallManualOverrideOff' (Then Path) Else - No Actions - (To add one, press 'Action')

Yes, I did.

I upgraded to 5.0.1_13 using the "Upgrade Packages" button, so the recommended upgrade path works. ************ IoX ************ isy-5.9.1_13 Name : isy Version : 5.9.1_13 Installed on : Tue Mar 11 11:53:58 2025 PDT Origin : misc/isy Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : UNKNOWN Comment : ISY Port to X (IoX)

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.