Techman

I was told that Smartlabs / Insteon is focusing on their Hub and their smartphone apps. They've also eliminated some devices from their product line, i.e. Wireless Thermostat and the Synchrolinc. It's still too early to tell what direction the new owner will be taking the Company in.

Query the low battery node, that should reset it.

Zwave has several options, one being the Multisensor 6

This is the hardwired model, the wireless model is nowhere to be found

They're no longer available on Amazon. I had typed in the wireless thermostat and Amazon returned the hardwired model. See my corrected post above.

A search on the Smarthome site doesn't even bring up the thermostat. They've been discontinuing some items, not sure if that's the case with 2441zth. UPDATE I just spoke with Smarthome, the 2441ZTH has been discontinued, I use several of them to monitor temperature and humidity. Guess I'll have to switch over to Zwave when they fail..

Yes, right click on "My Programs", then click on copy to clipboard. You can then paste into your word processor.

You could set your event viewer to level 3 which will display real time traffic in its window.

Mitch, Here's a few troubleshooting guides. If your send / receive leds on the ISY are always flickering then I would check both your error log and the log to see if there's any Insteon traffic you may not be aware of. https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

Did you also plug your PLM into the UPS? If so then plug it into a non filtered outlet as the UPS will filter the powerline Insteon signal. The ISY should be fine plugged into the UPS It's normal for the receive / transmit leds on the ISY to flicker when the ISY is sending or receiving data. If the bulbs you're dimming are LEDs then the bulb could be the problem. Some LED bulbs are not 100% compatible with Insteon devices and will flicker when dimmed. The UPS should be isolated from the powerline with a Filterlinc as its power supply can interfere with the Insteon signals.

Every time the temperature changes, when the temperature is less then 81, the then clause in your program will run. You could also try the following: IF Status thermostat <=80 (temperature and status Outlet is not off THEN your then statement

Here's a link to the ISY error codes. Most have definitions. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

What are your ISY firmware and UI versions? What version of the MS do you have. How old are the batteries? I would bring one of the sensors indoors close to the PLM and put it in the linking mode then try to query it. Post your results.

Chayne, Welcome to the forum Take a look at this thread https://forum.universal-devices.com/topic/2395-socket-open-failed-javanetsockettimeoutexception/?tab=comments#comment-19324 If you're still unable to resolve your issue than it's best to submit a support ticket http://www.universal-devices.com/contact-support

A possibility is that the open / close sensor somehow got its links corrupted. Try deleting the sensor from the ISY, do a factory reset on the sensor, then link it back to the ISY. Make sure that only one sensor is in the linking mode at any one time. Note: when you delete it the sensor will also be removed from any programs where it appeared so you'll have to add it back to those program lines.

Open your ISY event log and set it to level 3. That will show real time ISY activity and may help you narrow down the problem.

What is the status of the LEDs on the front of the ISY? It's possible that you may have a program running in the ISY that's in a continuous loop. When you updated you ISY firmware did you also update your UI by clearing the JAVA cache and programs and down loading the new ISY launcher? Are you using a PC or a MAC?

If the load is a separate device, i.e. not physically connected to the keypad, then you need to create a scene and add both devices into the scene as CONTROLLERS. When any device in a scene is turned on or off it also triggers all devices in that scene.

It's a common mistake. You're not the only one.

The device does not have to be in the linking mode to add it to the ISY. Only battery operated devices need to be put into linking mode prior to adding them to the ISY. Are you getting any error messages when you try to add it? Are you sure you're entering the correct address for the device? Make sure you use the Zero not the letter O if the address has one. You should also do a factory reset on the device prior to adding it to the ISY

Check to make sure your not running out of ISY resources. Do you have programs or network resources that are always running? What model PLM are you using. Is your ISY the pro version? What ISY firmware and UI are you running? Your logs should still be intact after a reboot. A factory reset will probably wipe them out. Take a look at your error log.

Can you give me a program example on comparing values.

I think that with 4.7.3 I really don't have any options. My first thought, as smokegrub suggested, was to assign either the temperature or humidity to a variable. Guess I'll have to sit it out until I move up to 5.x.x.

I have several Insteon wireless thermostats that I use to monitor temperature and humidity in outside patio areas. When the batteries fail the ISY shows the last reported temperature and humidity and it could be days before I realize that the batteries have failed. Being that the thermostat doesn't have a battery node, has anyone come up with a clever program to determine if the thermostat's battery has failed? I'm currently running 4.7.3 firmware.

UDI plans to move away from Java dependency. When that happens the ISY will be fully supported without Java.