gweempose

This is the auto-lock program I was running at my old house: If I am unable to get the status updates from the lock to work, is there any way I can tweak this program so that it will still work reliably on the eisy?

I just set up a brand new eisy configuration from scratch in a new home. It is running the latest version of the firmware (5.7.0). Everything seems to be working great, including my two Z-Wave locks. The problem, however, is that the eisy is not receiving status updates from the locks. If I initiate a lock or unlock command from the eisy, the status will update, but if I lock or unlock the deadbolt manually, the status does not change. This is a problem because I have an auto-lock program that requires real-time status updates from the lock in order to function properly. I tried doing a network heal as well as a synchronize with interview. Neither of these things fixed the problem. At my old house, I was running a 994 with a 300 Z-Wave board and it worked perfectly with these same Schlage locks. Is there anything I can do to fix this issue? Here's a photo of my setup:

Thanks for the link! Since I'm starting from scratch and am not transferring any devices or nodes to the eisy, I'm assuming the only thing I need to migrate is my Portal license?

Today is the day! I'm ready to install my eisy and start programming it. Since I'm in a new home, I'll be completely starting over from scratch. I'm a little confused about the exact order to do things. For example, at what stage do I remove my 994 from my portal account and add my eisy to it?

I just ordered an eisy, as well as a serial kit to connect it to my PLM. I will be setting up a brand new installation at my new home. The PLM was previously paired with a 994 at my old home. What do I need to do to prepare the PLM for the new installation? Do I need to perform some type of factory reset?

Thanks for responses! I think I'm just going to bite the bullet and upgrade to the eisy. At least that way I know everything will be fully supported for the foreseeable future. I noticed on the eisy page on the UD store that it says, "Want a discount? Become a member!". What exactly does this mean? How much is the discount, and how do you become a member?

It's a 300, unfortunately.

I recently moved and would like to set up the 994 in my new home. I moved many of my Insteon and Z-Wave devices from my old house to my new one, plus, I installed some new devices. I was running 4.9 at my old house, but I'm thinking this may be a good opportunity to upgrade to 5.x. Before I do something rash, I have a few questions: 1) How do I factory reset the 994 so that I can start from scratch with a fresh install and re-add all my devices? 2) If I upgrade to 5.x, will I lose the ability to control my Z-Wave devices? I thought I read somewhere that this may be the case. 3) Since my 994 and PLM are both working perfectly, is there any compelling reason to upgrade to an eisy? I'd really hate to spend a lot of money if I don't have to. Thanks!

My friend texted me last night that his Insteon HUB just suddenly stopped working. A quick Google search led me here. I had tried to get my friend to go the ISY route when he first set everything up, but he didn't want to spend the additional money at the time. Now I'm trying to figure out what his options are going forward. Unfortunately, I have never used an Insteon HUB, so I'm not really familiar with how it is integrated. Here are some questions: 1 - Can the Insteon HUB be controlled locally, or does it require the no longer available cloud servers? 2 - What are his options going forward? If he switches to an ISY, will he need to purchase a PLM, or can he use the built-in PLM in his Insteon HUB? What about if he goes with a Polisy? Are PLMs even still available now that Smarthome is out of business? 3 - Are there any other controllers on the market that will play nicely with his Insteon devices? He doesn't have a very extensive setup. He's just looking for a way to control his existing switches and dimmers from his phone / Amazon Echo.

One thing I don't like about this is that it will throw the deadbolt even if the door is open. To get around this, I created a program that monitors the state of the door and only runs the autolock timer once the door has been closed.

My experience was the exact opposite. I had lots of communication issues with my Ventstar thermostats, but my 2441's have actually worked quite well.

Just checked, and it's working for me.

That's super cool. Thanks for the link!

Just a heads-up. The Echo is on sale for $100 today.

There are actually quite a few commands that will work which do not require a program. For example, you can turn the thermostat off by saying "Turn off (thermostat name)". It will turn back on again if you issue a temperature command such as, "Set (thermostat name) to 70 degrees". If the temperature you requested is higher than the ambient temperature, it will turn on the heat. If it is lower than the ambient temperature, it will turn on the AC. You can query the ambient temperature at the thermostat by asking, "What is the (thermostat name) temperature?" or "What is the temperature in the (thermostat name)?" You are not crazy. I believe the command is "Increase/decrease (thermostat name) x degrees". It is important to note, however, that this command will not change the mode. So if the thermostat is set to cool, it will not switch to heat no matter how many degrees you increase the setting. In order to switch modes, you must first turn off the thermostat using the command I mentioned above.

Just a reminder that today is Amazon Prime Day. The Echo is $90, and the Dot is $35.

Thanks, guys! In my case, I think doing the programming in the thermostat itself makes the most sense. I'm not looking to do anything complicated, and this will give the best reliability. I can always override it from the ISY if I choose to.

I've now upgraded all three of my thermostats to Insteon ones. They are working great, and I'm enjoying controlling them from the ISY, Echo, Agave, etc ... I do, however, have a question about programming them. Does it make more sense to create the programs in the thermostat itself, or to let the ISY handle all the programming? What would be the advantages/disadvantages of one method vs. the other?

If you have Android, I'd highly recommend Agave in conjunction with the ISY Portal. The app is great and is being actively developed, and the Portal will eliminate the need to open up ports in your firewall.

I will second the recommendation for the Philips warm glow LED bulbs. I have them all over my house and couldn't be happier.

Dumb question, but how do I check the firmware version on my Echos and Dots?

I'm still discovering myself how to fully use the Echo to control the thermostat. I'm not sure if there is a way to have the Echo turn on a specific mode from the Smart Home skill. I think if you tell it to set a specific temperature, it will turn on either the heat or the AC based on the current temperature in the room. You can definitely do what you want using programs, though.

Thanks for the info! I don't know why I forgot about this. I already have programs that I've been controlling this way for a while ...

Cool, which brings me to my next question. How do I control programs from the Echo? I've never done this. Can I control them directly, or do I have to use scenes?

I just installed a 2441 thermostat yesterday. It's working great, and I'm able to control it with my voice, but I'm trying to figure out what exactly can and can't be done via the Echo. Does anyone have a list of all the voice commands that can be used to control this thermostat? I'm hoping there is a way to change the fan from "auto" to "always on" using the Echo. If this function is not directly supported, I assume I will have to set up some sort of program and trigger it indirectly from a scene.