lilyoyo1

Not necessarily but it can potentially be cheaper. It all depends on how close your isy is to the switches (if it can talk directly). If it cannot, by the time you buy repeaters you could potentially be at the same price point. You would just get a ge enbrigthen zwave switch and add 4 ge add on switches. Other companies have similar setups as well.

Your router must support upnp and it must be enabled (upnp is normally disabled) for this to work. Note: in today's world this is not recommended. Either manually set up port forwarding or use the isy portal for remote access. Both are much more secure

It's supposed to blink. I would move it closer to the ish and do it. If it works then, it's probably communication in that area

Check your inbox

I would just follow the advice to see if that works. If it doesn't you can start doing other troubleshooting

Do both match

Firmware and UI

Everything is still the same. More stuff is out of stock due to covid

It's not supported. You may be able to flash tasmoto software to it and use the Mqtt nodeserver to control it. Note: you'll have to do most of the work yourself to get them programmed to work with the nodeserver. Your other option would be to hope that they have an open api that a developer could use to develop a nodeserver for it

I can see this being normal behavior as this is built into the device itself. By default, if a switch is already on (dimmed), insteon will turn fully on. Ditto if you dim down. I've never paid attention to what happens in the console to know how the isy handles it (never thought about it). The isy is seeing the second tap as a standard press which is why it reflects the pre-set level vs the actual level. Im not sure if this is something Udi can fix as I'm uncertain what message is sent during this time. You may have to query the device after a button press if this is needed. A variable updating after a second on command would work best

If you're talking about the insteon hub and you already have the isy, why not just add the device to the Isy instead of the hub

You're welcome. My pleasure. That's what I ended up having to do. It was a pain

There's no compatibility issues with 5.0.16. Support for the new board started in 5.0.13 i believe

I don't think its the board but something within the coding for locks. Everything else zwave works perfectly everytime. Highly responsive and accurate. This applies to tilt sensors, door sensors, motion, outlets, and occupancy switches. Options such as when it comes to how a lock is used such as locked by touch or keypad doesnt work (when it updates) so I'm assuming it's a coding issue vs board issue. These changed in 5.3 from 5.0.16 which is when issues started happening.

No. All I install are yale. Have had nothing but issues with all since 5.3

Yale has the same issues

Here's part of their dealer letter talking about their issues.

No. Smarthome.com

What you're experiencing is an issue with the isy not your devices or Plm. I'm leaning towards what DennisC suspects and that you've maxed out your isy. Try deleting a scene that you don't really use and see if you can create another then.

@Chris Jahndoes this address the issues with locks that many of us has had with 5.3+?

Did you clear your Java cache

Insteon uses RF not wifi. Your modules are Powerline only so moving your isy can potentially change things though I doubt it will as long as your phases are properly bridged. The only way to know however is to try.

Did you recently update your isy? What's the firmware and ui? Did you try admin admin