Jump to content

Bumbershoot

Members
  • Posts

    2407
  • Joined

  • Last visited

Profile Information

  • Location
    Bend, Oregon USA
  • Occupation
    Retired - former systems manager

Recent Profile Visitors

2717 profile views

Bumbershoot's Achievements

Advanced

Advanced (5/6)

914

Reputation

16

Community Answers

  1. 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.
  2. 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.
  3. @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
  4. Same here. I'm on 5.8.4_1 after updating yesterday afternoon. Same symptoms as yourself, @joepoway and @BobM99.
  5. @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.
  6. Sorry I didn't see this earlier, but I had exactly the same issue. Easily resolved.
  7. 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.
  8. 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.
  9. FWIW, all of my Python based plugins aren’t running after the upgrade, including RainMachine.
  10. Rebooted, with no change. Oddly, all the plugins reinstall with every reboot.
  11. I did wait, yes. I think I’ll give another reboot and see what happens.
  12. 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?
  13. @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?
  14. It runs fine on Sonoma with an M1 chip.
  15. 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.
×
×
  • Create New...