lilyoyo1

You're probably right since the 500 board isn't compatible with 4.0. I think support came around 5.0.13 or somewhere around there

The double tap is built into the protocol so that will happen regardless. With it needing to be purposeful, I wouldn't worry about it as much. The pro is the system will work without the isy should something happen. You also don't have to worry about slow downs should the isy be processing other events at that moment. I'd operate mine that way if it weren't for me being able to use the double tap feature to turn on the light and fan together with it

Whatever happened to him? Lol

Being that I've had the opportunity to work with the designers many times I'll go off what they say. What you say makes absolutely no sense. For insteon to be smart it's designers would have to be smart since they designed it. Insteon was designed first to be independent of a controller which is why things hops and so forth are built into the protocol itself. Because the RF is tied to the power line, it's more important to let insteon manage the hops because it knows a lot better than you what it sees and will manage the hops on its own. You trying to do so would only mean constantly trying to change things to improve when changes are dynamic when insteon does it on its own. As with retries, too many hops will cause more issues than it solves which is why they limit it. A controller constantly retrying things wouldn't help as it would simply cause unnecessary communication which probably wouldn't help. As most people on here say, a clean system is the best system regardless.

That's the firmware version. The bootloader is 0.00

Theres always going to be differences of opinion in the best way to maximize one's system. Lessening hops could lead to system instability and long term problems while lessening retries improves things. As I stated earlier, the white papers explains it all so I wont go into details here. The problem starts when we think we know more about whats going on than the system that was designed to operate a certain way. Insteon devices are smart enough to know what it needs to ensure proper communication (this is why they do not need a controller for communcication). It;'s this intelligence that allows you to look at the event viewer and see how many hops you have left. The system KNOWS when to send more or less. Trying to outsmart it by saying send only 1 hop means only 1 hop gets sent....What if you need more at any given moment? Retries on the other hand is redundant. If it doesnt work the first time, the likelihood of it working the 2nd, 3rd, 4th, or 100th time goes down each time. If something is stopping the signal its going to keep stopping it.

Anytime you upgrade, you must clear Java cache so that your UI and firmware matches

Hops is less of a worry with insteon due to how it works. Their white papers explains it in much better detail. The retries is the bigger issue. To cut down on communication slowing down/distrupting your network, they allow you to lessen the amount of retries that you need. For some things, a single retry may work while others may need 3. If you need 3 retries, you have comm issues that should be investigated and fixed (if possible). If you have a single retry and it works then your great.

There is no upgrade to the zwave firmware. It's been posted a few times on this forum that he'll has been removed and replaced with update neighbors

Nice write up. I do mine differently in that I leave my buttons in toggle mode and do not use a separate off button for the fans since turning the button (speed used) off will achieve the same thing. Opens up an extra button for something else. I also have an all off button which will turn off anything that's on in the room so it's redundant. I also don't make my devices controllers in the scenes itself. Everything is configured as responders. I use programs to trigger the fan speeds based off the button presses. This allows me to have a single press trigger the fan and a double press to trigger the fan and lights at the same time. The scenes themselves are still configured the same otherwise which allows app or voice control to sync and operate properly

I'd plan for the worse just in case. While your use case today is 1 thing, once set up, you may think of alot more that you may want to do with them over time.

Did you factory reset the unit before hooking it up? Being from eBay you don't know what's wrong with it. After the factory reset, if recalibrate it to make sure the temp is correct

Gzahar is correct. You'll need the 5.0 branch software to save previous states along with programs to set everything the way you want to. The kpl button cannot be part of the scene. If you Google isy cookbook there may be examples in that

No. You're better off getting the 2477s. Using a dinner for a fan can damage either or both devices over time even with the two rate set to as low as it can go

You aren't missing much with 700 right now. There's a lot of devices going through certification but they aren't on the market yet. Besides, you'll need a 700 series controller to take advantage of that. Most likely you won't see much of a difference in your hard wired devices if you have a strong network already. I question the longevity of a company when the prices are extremely low. Of course we all want low prices but those in the race to the bottom will always lose to the cheaper person.This limits their growth overall as consumers jump to the "next big thing (in this case the cheapest)". At some point they'll go out of business due to consumers fleeing, wanting more than they can provide, or running up on the limitations and blaming "the cheap devices". I think many people here forget they aren't the avg consumer when it comes to electronics and technology. We'll do what it takes to make sure our networks run smoothly and can handle what we thrown at it. The avg person simply uses the router the cable company provides which isn't designed for a house full of wifi devices. If they do get their own router, they'll generally get something on the lower end which puts them in the same place. Ditto for configuration. You're right about routers and APs advancing over time. They already have.....Tremendously! However, routers and access points are like smartphone batteries. Regardless of how much they improve or grow larger, the technology they are used with also progresses at the same time using those newfound resources. The more they add, the more everyone else is going to pull from it. The 1 constant....people looking for cheap/free and being willing to settle for good enough. Look at streaming 5 years ago compared to now. Imagine 8k with HDR and Dolby Atmos streaming in the next 5 and whatever lies beyond....

Your ON level is set to be OFF which is why it turns off with on and on with the double tap

Where it says remove a zwave device

Wiki!!!! Who reads that? ?

You must exclude first as with all zwave devices

See very first post at the top of this page

I can see this being the main reasons why UDI would want to stay as far away as possible with official support. Is it really worth the cost for a 8 dollar device from a company that will probably be gone a year from now.

I don't think people are against wifi plugs on a small scale. Most are considering the avg consumer using standard routers at scale. Most of us that frequent this forum aren't the avg person with avg things in our home. We understand the risks and how to mitigate it to a certain degree. The avg person however doesn't. Then, when they have issues, it becomes at&t, Cox, or Spectrum's fault. I use 1 Belkin for the same reason as you and it serves it's purpose.

Firmware and UI must match. Clear your Java cache

I'm with you on that one. That's a large part of why I can't fully invest in zwave outside of specific use cases