Bumbershoot

It appears that Thread supports Multicast, which makes me believe that a command can be sent to multiple devices at once. Isn't that at least a step along the path to eliminating the popcorn effect?

If it’s Polyglot Cloud you’re referring to, then see this post:

Okay, that would be weird, and not so useful as I'd hoped. Thanks for looking into it.

Thanks for going through all of that, and I'm happy to see that Zooz is continuing to upgrade their firmware. I've got a few of these dimmers still in the box. I'm not running HA, so I'm going to wait for the upcoming Z-Wave/Matter board from UDI before I even think about jumping through those hoops... Then, hopefully, we'll be able to update the firmware from our Polisy.

That's what I did after I tried the portal. Thought I'd take a pass at the portal method, though. @Geddy, I'm pretty sure there were no bad effects. The failure occurred instantly, and the ISY software didn't restart. Upgrading from the Help | About menu in the AC seemed to work normally.

@Michel Kohanim, I'm finally getting around to updating this Polisy. I gave the Firmware Update button on the portal a try (upgrading from 5.4.3 to 5.4.4), and it didn't succeed. The error is in the screenshot.

FWIW, the value is populated and is changing daily in my installation. Version 3.0.21.

For starters, I'd love to see the motion sensor exposed (motion | temperature). Adding these would allow me to get rid of a couple of Insteon MS II's. EDIT: I'm not expecting the performance of a Hue motion sensor to match the speed of a linked Insteon sensor - that's not how I'm using them. I've got them for ambient lighting purposes, but they're attractive and very well built.

This is the place. Since you've managed to purchase the node server on Polyglot, you're just about there. Click on the "Polisy Dashboard" button at the top of the page, which should take you to the Dashboard, and there you should find an entry for your new Rainmachine. You'll need to click on the "Details" button below that entry. That will take you to a new screen where you can control/configure your Rainmachine node server. Click the "Configuration" button, and follow the on-screen instructions for configuration. Save your changes and restart the node server, and the nodes (zones, programs, restrictions, precipitation) should populate in your ISY software on your Polisy. You may need to restart the Admin Console on your Polisy before the nodes appear.

No, I haven't heard of any progress. I hope to see someone take it on, as I'd support it financially as well. In reading through some the developer docs, it certainly appears that the API is licensed in a developer friendly fashion, and the documentation appears to be very professionally done.

I suspect that the node server will need to be updated to incorporate version 2 of the API whenever it's finished. I think that there are also numerous devices in the API that the current node server doesn't support. The Hue API - referred to as CLIP API ('Connected Lighting Interface Protocol') - will move to version 2, which is a breaking change over version 1. Version 2 is still a RESTful JSON HTTP API, but the structure has been redefined to make some improvements and allow for new use-cases. Both APIs will exist in parallel to give developers time to upgrade, however any new features (such as dynamic scenes) will only be available on V2, and in the long term the V1 API will eventually be removed. The V2 API is currently in early access and not yet feature complete, but it is already available on production bridges and in use by Signify developed applications. For features that are available on both versions, we recommend to start using V2. Just make sure to check that the bridge version is at least 1948086000.

Yep, that's another method. The user doesn't have a remote PC that runs Java (the Polisy is in an unoccupied vacation home), so I was hoping we could do it from the Portal. There's not real urgency for me to do this, as there aren't any specific features on 5.4.4 that this installation depends on, so it's probably fine to leave it until these questions get resolved. No, there isn't. I'll open a ticket eventually, but again, no urgency.

I have a relative who's on Polisy with ISY software at version 5.4.3. That ISY version does not have the "Upgrade Packages" button on the Configuration tab. I'm curious if anyone knows if it safe to use the Portal | Select Tool | Maintenance | Upgrade Firmware button to upgrade the ISY software on the Polisy, if for no other reason than to get the "Upgrade Packages" functionality in the current version of ISY software? I don't see any information on the Wiki related to this question.

You can use the portal. Select Tool | Information | ISY Information | URL to ISY Copy the URL to ISY value and past it into a new entry in the ISY Launcher and you're good to go.

Keep in mind that your Polisy is running FreeBSD. With TPM enabled and strong passwords, your Polisy/ISY will likely be the least of your worries on your IoT VLAN.

Michel indicated that there could be corruption of the /etc/passwd file if the updates weren't done in a specific order (which is what using the "Upgrade Packages" button on the AC sorts out for us). I don't think this is a problem specific to FreeBSD at all (there are no new entries in the FreeBSD bugzilla site for 'passwd'), but something specific to what UDI is doing on their implementation.

My Polisy beeps a total of six times - one long, followed by five short - I suspect that means something such as everything is up to date. Some update status in the AC would be useful. The beeps are hard to hear for me as well.

In this thread just the other day: I can't help with the second part of your question.

Not that button. He means the button on the Configuration tab of the AC.

The Insteon Blog has some updates (as of June 30th): https://www.insteon.com/blog/2022/6/30/updates-from-ken Product Replenishing inventory - We are working with the factories, and we expect to have our first order placed tomorrow. On-hand inventory - We now have access to the existing product inventory. We had hoped to uncover a secret stash of products to start tapping into, but unfortunately, we have a very narrow list of products. We are working on the logistics to be able to take orders. Hubs - We will be offering a refurbishment program for hubs that’ve stopped working. The process will entail bringing the units to current manufacturing specifications by upgrading several internal components. There will be a charge of $24.95 for this refurbishment service – we know that you’re already paying a subscription fee, so it was important for us to offer this service at cost. Also, we are looking to re-work existing hub inventory to supply refurbished hubs for new orders. We’ll give you updates as soon as they become available.

That's easy enough to understand. That'll be my new practice.

Did you have the BIOS updated to EUFI on your primary Polisy prior to the last software update (seems sensible that EUFI wouldn't have been installed on your backup machine quite yet)? I wonder if there's a issue with the newest packages from UDI and a BIOS that hasn't been upgraded... I've got my Polisy running the latest/greatest FreeBSD release from UDI, with all the packages updated, BIOS updated to EUFI and TPM running, and it's running fine. I'd think there would be hundreds of boxes down if somehow the FreeBSD updates were broken is some way. I hope someone does report the issue. Very curious about this one. Would you please update the thread with the resolution? Thanks.

Open a support ticket.

I think you’ve filled up your disk with the updates. If you get in, run ‘sudo pkg clean’ which will clear the package cache. Check your disk space with ‘df - h’ and if you only have 4gb of total space, you have an early Polisy. UDI needed to reflash the OS on the disk to make much more space available.

This sounds like all the updates filled all your disk space. My Polisy shipped with only a 4gb partition, and a few large updates filled it up, leaving the Polisy to present similar symptoms. After a few hours of letting it sit, I was able log in, and I ran the command ‘sudo pkg clean’, which solved the problem.