Techman

Thank you. What's interesting is that the heartbeat node signal doesn't always show up in the ISY log. I have a handful of devices that send out heartbeats but for some unknown reason they're not recorded. I was looking through the log when I tried to trouble shoot the open/close sensor. It appears that the sensor is working correctly. I had been searching for the off signal which is no longer sent in the current firmware release and assumed it was a bug.

I just spoke with Smarthome. Beginning with hardware revision 1.B the heartbeat signal was changed from alternating between sending and ON and an OFF to just sending an ON. The status of the sensor contacts should have no effect on the heartbeat signal. Strangely, there's no mention a heartbeat signal in the manual for this release. I'll monitor this sensor for a few days to see if the ON signals show up. Should the ISY have a log entry for each ON heartbeat signal sent or only if the state of the heartbeat signal changes?.

In order for a program to work the heartbeat need to seen both an on and an off, I never get an off signal. I have other devices that send heartbeats which I monitors with programs and they work flawlessly. I'm going to try to speak with someone at Smarthome today to see if I can narrow down the issue.

LeeG With V1.9 I only get an "ON" heartbeat signal, never an "OFF", which shows up in the heartbeat node on the ISY, so once the "on" is sent there is no way to further monitor its status. When do you think you'll have the product? If you look at Michel previous post he stated that the heartbeat was removed from the current release, however that doesn't seem to be 100% correct as I'm getting 1/2 of the heartbeat signal.

Seems Smarthome is going in the wrong direction. So now there's no way to monitor the battery / communication status of the device with the current firmware release, or did I miss something?

I had previously tried that and got the same results

Hi LeeG The manual for V1.B has no mention of a heartbeat node, but it does mention a multi scene mode which doesn't show up as an option in the ISY. I think there may be an issue with the ISY firmware as it gives you the option to install both the triggerlinc and the open/close module but only installs as a triggerlinc. The ISY doesn't seem to support the multi scene mode or properly display the heartbeat status. In my case the heartbeat always shows "ON" so there's no way to tell if a signal is sent.

I recently added a 2843-222 open/close sensor, Rev 1.B. When I added the sensor I selected the 2843-222 Open/Close sensor option from the drop down menu but the device installed as a 2421 Triggerlinc (there's also an option to install a 2421 Triggerlinc in the drop down menu which wasn't selected) The heartbeat is only showing an ON state in the ISY. I checked the log after a few days and found only "ON" heartbeat entries, no "OFF" entries. I have good communication with the device so I know that's not an issue. The ISY also is displaying a "CLOSED" node which never populates. The "OPEN" node is working as it should. The ISY firmware is 4.3.1. Not sure I have a defective device or if it's a ISY firmware bug.

Xathros, Just got a reply from Smarthome. Not sure what there is to monitor. If they can be added to the Hub then why not to the ISY? Thank you for contacting Smarthome. The range extenders have Insteon addresses so that you may add them to your Insteon Hub and monitor it from your mobile device.

To disable the keypad right click on the device then click disable. This removes it from the ISY. You can reverse this action by right clicking on the device and then click on enable.

It's possible that you have a loop in one of your programs that's using up the resources or a communication problem with the KPL. I would try disabling the Keypad in the ISY to see if the problem goes away. Did you add or change any programs just before the problem cropped up?

As of 5/25/15 the current shipping version of the open/close sensor(2843-222) is Rev 1.B, V.43. There is a manual specifically for the 1.B release that shows the absence of the jumper. However there's no mention of the Heartbeat node. The ISY still shows this as a TriggerLinc model 2421. I haven't found a way to access the 3rd "closed" node

I tried to add it to the ISY just to see what would happen and it came up as an unknown device

That makes sense. It's too bad they don't show up in the ISY so we could note their locations.

Any idea why the Range Extender (2992-222 R3.7) has an Insteon ID address?

In addition to what LeeG suggested you might want to look at the possibility of electrical interference. Have you added any devices on the garage circuit that could interfere with the Insteon signal? The IOLinc in not a dual band device so all signals travel over the wiring. The addition and or failure of a device on the same circuit could create noise which would interfere with the signal to and from the IOLinc.

Here's a screen shot for heartbeat notify The program it calls up sends the email

They may be operating on the edge of the envelope. I would assume that the RF range would be reduced if the switches aren't getting the needed voltage which is why they don't sometimes show up as available

The 2 wire dimmers do not support LED bulbs, only incandescent so it's possible that the switches are not getting the required voltage to operate properly.

Check to see if "trigger reverse" is checked under the IOLinc options. If so then you're probably using a N/O contact and should switch to a N/C contacts and uncheck trigger reverse. The 3:00 am query is resetting the IOLinc thus triggering your alert.

It's using the default setting. Did you click on "save" at the bottom after you filled out the from data

How old is the PLM? It sounds like the PLM power supply is failing.

If the led on the PLM fails to light then either you don't have voltage to the receptacle that the PLM is plugged into or the PLM died. It's most likely a coincidence that it failed when you installed the module.

Do you have "trigger reverse" checked under your IOLinc options, if so uncheck it as the query is changing its status. You'll also need to change your program to " Status 'The Gate Status' is ON

Can you plug the TV into a Filterlinc, that should solve your problem. http://www.smarthome.com/filterlinc-10-amp-plug-in-noise-filter.html