lilyoyo1

I didn't see that in their documentation except for the tube lights (which will have issues with insteon as well). They say do not use in switched outlets but that's for all of them as you cannot control what gets plugged into a switched outlet. Generally (insteon as well) as long as it's directly controlling something within it's specs, you'll be fine.

Probably best if you Google it since are so many manufacturers. You'll have to check their specs. With that said, where did you read that at about zooz?

This has already been discussed as well as proven that Polisy supports the 2413s via the DB9 port as well as the 2413u and 2448a7 USB stick. Not only has Michel stated that it works, there are many here (including myself with 2) using Polisy with the 2413s

Make sure you clear your Java cache and the firmware and UI matches. Did you try saving your program again? Simply click on a line, hit update and save. Also run the "then" section to see if that work.

I Googled how to remove a device in the isy and found it in the wiki. It's under remove a device. https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:ZWave:User_Guide

I'm not sure what your variable is set to do but as i read it, once it turns 1 (i assume it's dark), the light should come on. If you only want it to happen when you turn the switch on, shouldn't you add "and switch is turned on" to the if statement?

It doesn't really matter. The strength and ability to use either comes from having a strong network via multiple devices vs 1 singular device. If/when you build out your network properly, you'll see a difference

The very first post of this sub forum also has a link

Yes which is why I provided the information above as well as the information in the tips and tricks

It's supported. NWI isn't a catch all. Your network starting point is poor which may be part of the issue. As you build your network out, things will get better. The idea is to start closest and move your way out. You're already starting waaay out.

They'll end up with a check for 25cents after preordering 200 dollars worth of product.

All this Matter talk takes me back to when homekit came out and that was all the rage.

Did you close the admin console and reopen it?

This is why I prefer setting different scenes for each speed vs 1 scene for all speeds. If the speeds are separate scenes, you'd be be able to accomplish what you want to do

You can try ipcam viewer

The final nail was when insteon shut down....no more products

If you are certain that you set the ramp rate for the devices outside of the scene at .5 and within the scene itself for each controller, I would make sure that your firmware and UI matches to ensure there is nothing funky there preventing the system from working properly

Just the Isy as far as I know.

This is what Michel said once. Sudo pkg delete isy Sudo pkg install isy

It's impossible to future proof yourself as new standards are always being developed. 800 was recently announced and at some point 900 will be announced followed by 1000 series and so forth. The best way to semi future proof yourself would be to buy the latest series devices available and use them with your particular controller. Ditto when upgrading your controller. Should 800 series controller be available a few years from now when you decide to upgrade them you would get that so it's ready for whatever 800 series devices you may add later. All series work together. You just don't get the benefits of the higher series such as longer range of using a lower series controller. If you Google benefits of whatever series, you'll see the only talk about specific zwave capabilities not device specific features. This is because each series change improves zwave communication in itself, not necessarily the individual device features. With that said, once youve established a strong mesh in your home, most of the benefits of a higher series becomes moot since you would have reached network density. Newer devices are faster in generally due to newer processors and other improvements but ultimately the gains in speed isn't enough to warrant ripping everything out and starting over every time a new series comes out. If i had a house full of older 300 series from 10 years ago, I'd probably be willing to do that but not from 500 to 700 series. Zwave is like smartphones. They come out with something new often but the gains are incremental with the times. Will you notice a difference between a galaxy s21 vs a 22. Probably. But is it enough to drop 1k on that new one? Probably not!

Zwave doesn't really have a classification for keypads (that I'm aware of) which means it'll be on the mfg. to design around that limitation. Since it's a race to the bottom in regards to pricing, most probably do not attempt since that means it'll cost them to make it happen for a device that will be limited to a few devices that support it (along with the support calls that'll follow). Keep in mind, most of these devices are geared towards small (less than 10) installations vs whole home automation. While we might be a passionate community that's being left out of in their minds, we are a small minority vs the greater community

It's possible....Apple did win a billion dollar case against Samsung for having a rectangular phone with rounded corners (later overturned)

Are you using polisy? What firmware are you using for that and pg3? You probably should create a separate post for this since the op that started this post meant it as a guide for new users and not necessarily for trpubleshooting

The hub is not compatible with polisy not the isy

I agree with you in regards to installer and prosumer diy homes. Your sentiments are part of the many reasons why I can't fully get on board with zwave. When you talk about basic systems such as smart things and qolsys alarm panels, people are generally looking for basic control of their devices. What we do here with the Isy and other automation controllers do expose the shortcomings of zwave that other basic systems do not. In that regards, zwave works perfect.