-
Posts
5104 -
Joined
-
Last visited
Everything posted by Techman
-
Scenes not listed for conditional when creating a program
Techman replied to timekiller's topic in ISY994
The ISY has no way to know the state of a scene. The scenes don't report their status back to the ISY. The scenes reside in the PLM which also allows them to function even if the ISY is offline. -
All devices should be linked using the ISY. Linking devices outside of the ISY prevents the ISY from knowing their state, etc.
-
Being that the 2441ZTH thermostat doesn't have a low battery or heartbeat node I use a simple program to monitor communications. This assumes that the humidity will change at least once within a 6 hour period which then restarts the 6 hour timer loop. Program Thermostat monitor IF Status 'wireless thermostat' >5% (Humidity) Then Wait 6 hours Send notification to 'your email' content 'Wireless thermostat Communication failure' Run Program 'Thermostat monitor' (IF) Else no action
-
Issues with status updates on 2441ZTH Thermostat
Techman replied to MustangChris04's topic in ISY994
The power supply should be between 5 and 5 1/2 volts. Higher voltages will cause erratic behavior. Some power supplies are noisy and can interfere with the operation of the stat. If the thermostat is connected to a power supply then try running it on batteries to see if that improves communication, but give it a while to stabilize, it won't report immediately. -
Issues with status updates on 2441ZTH Thermostat
Techman replied to MustangChris04's topic in ISY994
You probably have poor communications between the thermostat and the ISY. try placing a dual band device such as a range extender near the thermostat. The wireless thermostat reports changes about every two degrees. -
If you're factory resetting all the devices, then it probably wouldn't hurt to do a factory reset on the PLM. No need to reset the ISY. Then do a restore PLM - DO NOT do a delete PLM. Were all your devices installed using ISY linking?
-
Another option is to use the windows snipping tool which captures your screen and saves it in a .jpg file
-
Scenes reside in the PLM, restoring the PLM rebuilt your scenes.
-
When you installed the keypads did you install them one at a time using the ISY link new devices? If so, then try pulling the air gap to remove power from the device, wait a few seconds then push it back in. That sometimes will clear up problems within the keypads.
-
Welcome to the forum. If you want the Keypad button to control the scene then delete it from the scene and then add it back to the scene as a controller. Then the button will control the scene and will stay lit when the scene is on. The device that you're controlling should also be in the same scene as the Keypad button.
-
Is it the scenes which are not working?, Which ISY firmware and UI do you have?
-
It's rare for a failed module to cause powerline problems. I would suggest doing a factory reset on the module, then a restore device from the ISY. Another possibility is the load it's controlling has an issue, especially if it's a CFL.
-
Naptown Take a look at this troubleshooting link, hopefully this will point you in the right direction http://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors
-
You've got a communications issue. It's not RF as the IOLinc is power line only. You have two options, either eliminate the power line noise if in fact that's causing your problem or add some dual band devices on the circuit close to the garage IOLinc, assuming that you have other dual band devices installed. This will improve the reliability of your Insteon mesh network. Keep in mind that if your communication to the garage IOLinc is marginal your garage door could experience unwanted activity.
-
I've never had to reinstall the admin console after a java update, but you do need to delete all the items and applications in the java storage area when you update the admin console.
-
Thank you. I don't recall those options being there the last time I looked, which was quite a while ago. . The page indicates it was updated in March. Either I missed it or it was added.
-
You most likely have a communications issue or powerline noise. The IOLinc is not a dual band device. Try either moving the device to a different location or add a dual band device, such as a range extender, on/off module, or lamp linc close to the IOLinc then try to re-link it. Do you have any CFL or fluorescent bulbs close to the IOLinc?
-
I just ran a email notification test and it works on the wireless thermostat ${sys.node.xx xx xx 1.CLIHUM} It's frustrating that the humidity option isn't documented.
-
That's the code I've been using for the Insteon wireless thermostat but it only displays temperature.
-
What thermostats are you using? What's the line of code that works?
-
Make sure you're actually doing a factory reset. For the IOLinc, remove it, hold down the set button then plug it back in. After a few seconds it will start to buzz, continue to hold down the set button until the buzzing stops. I would also do a factory reset on the front door switch. It sounds like you may have cross linked your devices.
-
Have you had any luck adding humidity to your notifications? The humidity node for an Insteon thermostat doesn't show up in the ISY so it may not be a workable option.
-
Here's what you need. http://www.smarthome.com/seco-larm-sm-226l-3-magnetic-garage-door-contact-switch.html
-
What apps are you using? The ISY dashboard is a pretty simple straight forward interface. See attached example.
-
Hi Jeff, Welcome to the Forum. You can rename your device nodes to your choosing. Just right click on the node in the device tree the click on rename. The current state value cannot be changed.