Bumbershoot

You set this value in the node server configuration page. In the Custom Configuration Parameters section, set Rapid Wind to true or false. FWIW, I wrote a program identical to yours quoted above, and the variable updates as expected. Maybe there's something specific with your installation of the node server.

You have to have a IS Portal account for the voice commands to work, so the migration is easy. Log into your ISY Portal account, then go to the "Select Tool" button, then go to the "Maintenance | Migrate to" menu options, select the ISY you're migrating to, and things will migrate automatically. I did this and didn't loose any voice commands at all. Quick and painless, in my case.

I thought about this for a second. If you're able to successfully install Z-Wave switches/dimmers, then you have all the skills you need to install the board. Decent motor controls in your hands and decent eyesight are all that's likely to be required, and an ability to follow directions. I have no doubt that this will NOT be a perilous operation. You'll probably need a small philips screwdriver, a table, and 15 minutes of your time. These little computers are not made of eggshells, and you won't need a soldering iron or a sledgehammer.

If you have the "Upgrade Packages" button in the System Configuration tab on your ISY software, then you likely don't have to worry about it. Clicking on the button should upgrade your Polisy to the latest/greatest and you're good to go. Otherwise, if you log into your Polisy with PuTTY, then the command 'uname -a' should get you the information you seek. [admin@polisy ~]$ uname -a FreeBSD polisy 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 releng/13.1-n250158-752f813d6ccc POLISY amd64

Personally, I would just wait for the eisy. It apparently is nearing readiness, and the ISY software shipping with it will have all new Z-Wave code/hardware that UDI licensed from a 3rd party. Michel has stated that both the Polisy and the eisy will use FreeBSD as the host OS, so the functionality of both should be identical or close to it. You’ll have the latest/greatest with only one migration step.

I'm doing this from memory as I'm not at home, so I might get this a little bit wrong. Open System Preferences, click on the Privacy & Security tab, and select "App store and unidentified developers", and start.jnlp will run.

You shouldn’t need an API key, which is one of the great things about a local API. I’d make a static reservation for these lights in your routing table, and search for “devlist.yaml” in this forum. Sorry I can’t help you more, but I’m traveling out of the country for a while.

I’ve never seen that. Something is in an odd state. I’ll be surprised if you get a satisfying answer to your question. First thing I would do is to take out the batteries, wait a few heartbeats, then put them back in, and hope for the best. Reboot it. Kinda like running Windows 98.

I assume the clock on your Polisy is beginning to drift... Since your Polisy runs FreeBSD, the ntpd service should be running by default (it is on mine). ntpd is both a client and server, so you could just edit /etc/ntp.conf to have it point to a server location that's not blocked by your firewall. Also, commercial network switches provide NTP services, so if you've got one of those you can get to (your internet provider, for example), you should be able to use it. I don't know how UDI would respond to a support ticket for something like this. If you can find a local NTP server that you that you can ping, then UDI might help you edit ntp.conf. This might become an ongoing support issue for them, as local NTP servers can come and go. Also, UDI might take a dim view of users trying to edit system files... It's your property, but they provide support. I'd ask them in a ticket: support@universal-devices.com

You can certainly append the values to a file in the web space on your ISY. I put them in comma delimited format, making a file that can be imported into a spreadsheet and graphed from there. https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic/Custom_Page_Creation

There's been various discussion about this on this forum, but it's my understanding that if the device isn't used in the path back to the controller (and as a battery device, it isn't a repeater), there should be no effect. I have a similar situation with a 300 series device (which isn't in to path of any other device), and it doesn't seem to interfere with later Z-Wave enhancements, such as network wide inclusion.

Presumably, once the Polisy/eisy have Matter on board (also presuming border router functionality), then one can easily imagine the Polisy/eisy providing the glue between native Matter devices and any devices in the UD universe (legacy Insteon/Z-Wave/Node server devices). Performance might be a question mark, but there's no reason to think it would be much slower than any other node servers.

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.