lilyoyo1

5.0 and 4.0 are different firmwares. By using a UI for 4.0 branch, there will be conflicts. While, your switch may be having other problems, the mismatch will add to the problem as well

As always, your firmware and ui has to match. Clear your Java cache and use the launcher

I completely agree

It works for us, because I don't want the lights cycling on/off and there's no delay in reporting. If it happens to get too dark, the delay is overridden

I guess we have our answer

I personally wouldn't go with a zwave thermostat. Yes local is great but in this case, I think wifi thermostats (cloud or local) are a much better option. It would definitely be better to have the ecobee be local don't get me wrong. However, the way the ecobee is by default, it works extremely well without manual intervention. Personally, I don't want to be so ISY dependent that if it fails (while I'm out of town), something major can be impacted. This is why my sprinkler, alarm, and hvac are all set up to work without the isy. The Isy extends capabilities but they are not dependent for every day use. If Venstar thermostats looked better, I would be willing to use their touchscreen as it is local along with access without the needing the isy (unlike a zwave thermostat). If my internet is down (whether isp or my router), I'm out of luck regardless of what I use. If ecobee's servers are down, that's temporary and I'd have access later. However, any isy issues screws the whole system. Nest and myq are great examples of cloud systems doing wrong. Personally, i never bought into nest due to how quickly and easily google abandons things. I simply don't trust them. With myq, they've been who they are from the start so Im not surprised about their handling of their api. When we went with new garage door openers, I went with myq. Why? Because of something happened while away, I could still use their app without the isy. The myq noderservers is wonderful and I do use it. At the same time, I've still set up pieces so that I can still do what I need locally for the times when myq fails as a back up. For me, cloud does present challenges but they also present lots of opportunity if one takes the time to plan accordingly with integrating

Did you read the Instructions on the download page prior to upgrading and follow them correctly? I'm order to go right, you must be methodical with the upgrade as well as use the launcher

It would be easier to help if you'd provide more info. A switch could be anything from any company as could whatever it's attached to and other devices. The more detail you give the better the response.

On the very first page of this subforum.

you need to create a separate scene and configure the devices to be what you want in it. Then control the scene itself not the individual device

Mine adjust when the light falls below a certain point. it doesnt trigger right away but waits about 10 minutes as it could be a passing cloud that makes temporarily dark. The same for turning off. A temporary moment of "enough light" will not trigger it to turn off.

MS's are great for a lot of things. I use zwave and Insteon sensors. Speed has never been an issue even though i use programs for everything. I have them hidden to turn the underbed lights on late night. Late night, they will turn lights on to a very dim level just enough so you can see. If you need more light, you can hit the switch which will turn them on to 50% if you need more but not full on (unless you double tap) I also use my sensors to turn lights and stuff off in rooms/areas that are unoccupied. For example, if no motion is sensed on my patio for an hr and the tv or music is on, itll automatically shut everything down. This only happens at night as we could potentially be in the yard away from the sensor during the day. My zwave MS's have lux sensors built in. I use this to adjust lighting in occupied rooms vs using only sunset +/- to trigger stuff. On a cloudy or rainy day, those options do not work well which can leave you sitting in the dark or needing to physically turn on the lights (whether its remotely or by touch). By looking at the amount of light in the room, the lights will turn on by themselves. Sometimes it

If its only the ISY changing the lights in a scene, then using multiple scenes instead of adjust makes perfect sense. If you want to change how the lights work at the switch manually, then you would want to use adjust scene. For example, my front porch and garage lights dim to 40% after 11. If motion is sensed, it'll turn full on and then go back to 40%. I just use multiple scenes for this with everything in them as responders. With my livingroom lights, I use adjust scenes. If you manually turn on the lights from any of the switches during the day/evening, they turn on 100%. Late night, they'll only turn on 50%.

Nothing's changed. What were the steps that you took?

Depends on what you mean by default. If you're just asking about it running whatever is in the "or else" then you are correct

Excellent comparison. Though I don't use Mac (wife does), I will say it's better than a PC. I don't like the limitations apple puts on users, which is funny because I feel completely opposite in this situation.

Id love if that worked. The problem is the people who could make that decision wouldn't. While they have a new owner, the daily decision makers are still the same people with the same backwards mentality. They have some great people who want to see insteon expand into the new age. I could see them doing something like this. Unfortunately, until the old guard is replaced, it'll always be limited.

From that standpoint I see your point. Luckily, there are systems that do allow others to join in and work with other stuff to accomplish those goals.

I think it's come far in the last 25 years. Especially the last 10. When I look at what I'm doing now vs the past, there's a huge difference. I remember the days of having 2 8 button keypads in all major rooms and 1 in the others. One kpl would be for the room and the other would be for the status/control of other stuff in other rooms. Then apps came along. Cancel the second kpl. Move past houselinc and on to the isy. With the syncrolinc and global cache, I could now add my audio and video to the system in regards to controlling. Still limited but beyond lights. Today it's a different world. Now, it's a single 6 button kpl (really only need 4) in the rooms and no need for an app. It'll cost you but you can achieve automation on a grander scale that's affordable. With noderservers, you can integrate harmony and sonos with your system. If I'm out on the patio with friends, as it gets late in the evening, the volume will automatically turn down on the system. That way I'm not disturbing neighbors or my wife. If I'm out there in the afternoon, and it starts getting dark, the lights will turn on. If we go inside and forget to turn stuff off, I don't have to worry about stuff being left on. Whether it's the tv, music, lights, or all, they'll turn off on their own or if I hit my goodnight button. Sometimes we'll be outside relaxing with music on in the background. We'll end up turning on the tv at which point the music volume will automatically lower. If we decide to watch a movie, the music will automatically turn off. None of this was possible years ago without multiple steps. It took a lot of time, money, and work but in the end, what's happening now is amazing especially compared to 5 years ago

There's a lot of interest...Just not a lot of desire to invest what it takes to achieve it. Smart products are growing in the homes.....full automation- is a different story

Node limit is a better term than device limit since all devices are not created equally. The 1024 pro max applies to everything whether it's from a nodeserver, insteon or zwave.

The problem with that approach is they still go towards your device limit. Depending on set-up, this can limit what he can do long term

That's zwave for you. I would remove the nodes you don't need before moving to the next device. They'll add up quick if you don't. Once done go back to zwave menu and choose freeze nodes

That's the one I'm talking about

Every environment is different so it's hard to say. I have a portal that I use to add things right next to the ISY before installation. If everything is zwave plus, turn on network wide inclusion in the zwave menu. start your installation with whatever place is closest to the Isy and work your way out