fasttimes

I replaced a couple of switches and want to swap the links out with the admin tool. But now my windows won’t launch internet explorer. How am I supposed to run jnlp downloads?

As an Insteon user, this limit sounds really low. It sounds odd you can’t group more than 5 switches together. Do you know if you can “chain” devices? If you have two groups: ABCX XYZ And you press Z, will that fire off ABC?

Does anyone know if there is a protocol defined limit to the number of devices in a group? I hear it’s 5, but I haven’t found any documentation on this.

Home Assistant is superior to the ISY in most facets. I rarely use the ISY admin or Portal anymore. The one thing the ISY excels at is working with Insteon devices. Programming them, creating scenes, and replacing dead switches. But for “home automation”, HA is just so much easier to work with.

I’m really frustrated about this too. I’ve spent thousands of dollars and many hours on Insteon devices and all I want is a reasonable price for buying in quantity.

My dad lost his password to login to his ISY locally (via browser/ip address). However his ISY is on the portal. Is there a way he can reset his username/password with the portal instead of using Telnet and the MAC address method?

Could you point me to any documentation on this?

With lock management and scheduling?

With lock management and scheduling?

They implemented Zwave lock support?

Have you by any chance ever used Home Assistant? Set it up up a small Zwave Network and you can do things with the Schlage lock you couldn’t imagine were possible. With the following integration installed, you can setup up to 30 users, such as your family, housekeeping, pet sitters, etc. All using date/time access schemes and programmable from a web UI. You will never have to use the Schlage programming scheme again. Keymaster Integration

I just logged into my folks ISY, and there are only a couple of sensors showing. Is there a way to "load" the existing network from the current insteon devices?

@Michel Kohanim Is it your intention that the ISY will be eventually replaced by Polisy? Would that not require adding PLM support? I can only imagine the hell it must be to produce a hardware product. Is there something special about this new product that couldn’t be replicated on an existing hardware platform? With container systems like docker, it would be fairly easy to have your code run on many platforms. Licensing shouldn’t be a problem either. In fact, I’d rather UD spend their time on developing kick *** software instead of hardware. I tell people they buy an ISY not for the box, but for what goes in the box. I don’t even really need the ISY Portal anymore, but I keep renewing just as a “thank you” for the constant software updates.

This sensor looks like it does a lot of stuff. Unfortunately I can’t figure out how to do something really simple. I just want the sensor to report ON after motion is detected and report OFF after no more motion is detected for 300 seconds. In in other words the sensor reports ON and stays on while any motion occurs, and there must be 300 seconds of no motion for it to turn off. Does anyone know how to make this happen? Is a higher number for sensitivity more or less sensitive?

This is just a placeholder thread for trying to debug the poor performance of the ISY Component for Home Assistant. Note, this is not code developed by UDI, despite the name. Hopefully @Michel Kohanim will be able to provide some guidance. The Home Assistant platform has many different components that lets you “add” and control devices from Home Assistant. For example, the MyQ Cover component lets you include garage doors associated with your MyQ account so that you can view and control them directly with Home Assistant. In the Home Assistant configuration file you would add something like the following: cover: - platform: myq username: YOUR_USERNAME password: YOUR_PASSWORD type: chamberlain And any devices that are associated to the username specified would get sucked in to Home Assistant. You can then control them, monitor their states and write automations. Likewise, there is also an ISY Component which sucks in and controls lights ISY devices. # Example configuration.yaml entry isy994: host: ISY_ADDRESS username: ISY_USERNAME password: ISY_PASSWORD Mostly I want to control ISY lights (usually representing a single Insteon dimmer) or an ISY scene (an actual ISY scene, compromised of several Insteon dimmers with different load levels and ramp rates). As I have mentioned in other threads, if I expose ISY devices or scenes with the ISY Portal, I can control those with Alexa or Google Assistant. They respond quickly. However, controlling devices found with the ISY Component is anything *but* fast. I’m going to see if I can figure out how to write my own custom component in order to find out where things might be slowing down.