Michel Kohanim

@xlurkr , The repos are locked for polisy. So, next time you need to upgrade, just repeat the same command and use prod. Again, this only temporarily unlocks the repo (till next boot). No other side effects.

Please do sudo repo.util and switch to staging. With kind regards, Michel

They probably don't report energy cluster. You can use Zigbee menu | Capture Log | Start and remove/add them again. You should see energy cluster reported if they support it. With kind regards, Michel

I don't know what to say. Are these thirdreality switches? I have one right here: Yes in the code but LR requires UI changes that didn't make the cut due to not being fully tested. Same as i3 keypad load button assignment. We should have another build shortly that includes both LR as well as i3 keypad load button assignment. With kind regards, Michel

@Guy Lavoie , did you remove and then add it back? With kind regards, Michel

@Guy Lavoie , ah, wrong wording. It will work with all supported Zigbee dongles including ZMatter USB. With kind regards, Michel

@Guy Lavoie , yes energy monitoring cluster was added. @Techman , yes, as long as the dongle is from our [ supported list ]. With kind regards, Michel

@JimTurner , Yes. https://isy.universal-devices.com/start.jnlp With kind regards, Michel

@mldoyle , Thank you very much for the update! Yes/No, both Z-Wave/Zigbee libraries went through a redesign so inclusions/interviews will be a little faster. Regarding responding to events, yes, but it should not be noticeable. If it's noticeable to you, then I am quite pleasantly surprised! With kind regards, Michel

@Guy Lavoie , yes only 800 series dongles. We literally had to take a few dongles, register them with our ud port manager so that we can figure out what type of device we're dealing with. With kind regards, Michel

@Guy Lavoie , That's the beauty!!! Upgrade is done on the clone - not on the live system. So, if the upgrade is really screwed up, there are two cases: Upgrade fails in which case you never reboot into the clone (you stay on the live system). And even if you reboot, you will stay on whatever you started with Upgrade somehow succeeds (unlikely), you reboot into the clone, and you cannot access eisy-ui, then you will use: sudo ud_pkg_mgr toggle_boot_env --> which allows you to toggle to the other env With kind regards, Michel

@Guy Lavoie , Yes, you can remove the inactive one , and it's really best if you do If you don't, future upgrades use the inactive one as the clone and make your active one inactive With kind regards, Michel

@dbwarner5 , No! You literally have two disk partitions one of which is called "storage". Boot Environments are not disk partitions. They are ZFS boot environments on the same disk partition. With kind regards, Michel

@Guy Lavoie , thank you for the update, and your continued support. Not only I believe you regarding cost, but we experience the same since memory/storage costs quadrupled since early 2025. If polisy is working fine, eisy | lite is definitely a better option, as it has a much faster CPU and fully tested with everything especially the plugins. On another topic which does require 6.1.1 for dynamic profiles, @SteveL has been busy using ChatGPT to make FULL plugins without any coding whatsoever. He literally speaks to ChatGPT, says what plugin he wants, and boom! [ link ] With kind regards, Michel

@dbwarner5 , You seem to have two partitions. One for storage and one for OS. Regardless, the way ZFS works is a little different. So, Disk Usage in the Active environment also includes the one in the inactive. So, if you want accurate information, it's best to remove the inactive boot environment. With king regards, Michel