lilyoyo1

We had this discussion not to long ago. I see nothing changing with it .

I get that. However you must set the light level in the controller as well

Did you set the main button to turn on in the controller or just the scene

It's a no win situation. Have 1 level of device someone will complain they don't need everything so they are paying extra for unused stuff. Unlock features and you'll have someone complaining of a money grab. Everything is based on perspective. You can say it's shady to unlock additional features or you can say you paid a lower cost for what you needed rather than extra for something that may never get used. It's hard to say what the limit is which is why there probably isn't a warning as the limit is based on a multitude of factors. Removing a kpl will open up more nodes than a relay switch. Or using an insteon plug in module would allow more devices than a zwave plugin. It's probably difficult to ascertain the exact amount of nodes (though a warning stating it's a possibility once it stops working would be nice)

Alexa isn't that smart. Not yet anyway. The most you could do is ask Alexa for the status prior to issuing the command you want

I'd follow the advice from larryllix above. If the switch is set for 100%, I would factory reset it and then restore it in the isy

Isy portal is not a UI. Go to help about for the specific firmware and UI

It's not a bug. What's your firmware and UI? Is the switch part of a scene or program? I'd it an insteon or zwave dimmer The more details you provide the better we can assist you

That's not the proper way to contact Michel. If you want proper support from him or udi, You must submit a support ticket. If trying to draw his attention to a post you should include @ before his name. Being that yesterday was a holiday and this happened over the weekend he may not have been on here. I also answered your question in my last post about 4 posts ago.

There are no more firmware upgrades to the 99. The 3.3.10 was the last. You would need the 994. Personally I'd go with the zwave version but if you don't foresee needing zwave at all, you can add it later.

I just realized that you're using a 99i. I wonder if it's having problems due to not being updated in so long. Hopefully @Michel KohanimKohanim can chime in to confirm if a new Plm would work with it.

None again

None if you go through the portal

What's your UI and firmware?

I'm not understanding what you're saying. They link to scenes and individuals devices exactly the same (a remote button and single light would be a scene)

Button groupings turns off a button when either button is pressed. It's not recommended to use this as a scene correctly built will accomplish the same thing and works better long term. When using button groupings, status is not properly tracked which can impact programs and syncing when using external controls such as apps since those are not carried over when using button groupings.

The motion sensor and Alert module are the "new" insteon devices that are not part of the 4.0 branch.

Sounds like you have too many devices. The pro version would allow more nodes to be installed.

Good luck with that. If you find a way, let the world know. They're terrible

Or we can rename this thread since the original question was answered the first time. Lol

There comes a point where too much irrelevant information is provided. People don't even read whats available now but time should be spent on more information that no one will look at. Why waste time? Especially for something that rarely gets upgraded if ever.

You're assuming there are updates when there are none. You're looking at old information that no longer applies. There are 2 zwave dongle. The old 300 series which is what you have and the new 500 series. You're reading information that applies to the 500 series as it's firmware is different than the 300 series. There's no table because there has not been any updates for the dongle that you have. None for the new dongle that's out either.

I agree with you on that. My hope is that UDI will "buy" the rights to high value nodeservers such as Hue, Sonos, Lifx, and Harmony from the developers. They develop a nodeserver and work out the bugs. If it's a high demand NS, udi then purchases it. At least that way the Isy always has it and someone else can work with udi to keep it going should it be abandoned. The developer can still charge for the NS should they continue to develop and update it.

Anyone that has setup the ISY using the 4.0 branch has setup scenes the exact same way for it to be bug now. Most likely there is something within your setup itself. I would delete the whole scene, add each device as a controller (if done correctly, there is no responders in this scene. ALL should be controllers as a controller set up this way is also a responder). One way you will know its correct is if each switch is RED in the scene. Once you verify that each one is a controller, click on each switch within the scene itself and configure all devices under each controller individually.

Copy and paste the scene grouping itself from the device list. Make sure that each one of those switches are set in each controller