Teken

You can create a program to monitor the heart beat interval. Once that heart beat is seen the (THEN) clause can be selected to do a remote write to the device. Keeping in mind this has no relations to (IF) you disabled the battery write option. Meaning if you selected the 1011 icon at the top you need to disable it so the system *will* be able to complete the task.

Means battery device is set to write delay.

I don't own any Z-Wave but a quick glance in the forums indicate a few members are able to monitor energy readings and also include them in programs using the various Z-Wave plugin modules. Obviously if you don't have the hardware you will need to upgrade the controller so you can take advantage of the various brands that support energy monitoring. As I don't suspect Smartlabs is interested in this area any longer given they haven't updated any of these devices or introduced further hardware that supports energy monitoring. [emoji35] Quite sad really, considering they could have easily lead the market but instead squandered that role to others. [emoji58][emoji37] UDI has no intentions to spend any resources on either product. As Michel had indicated in another thread that supposedly both products are end of life. [emoji17] ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

This device has been abandoned for quite sometime by Smartlabs and third party vendors. You can set up a program in the controller to update the Watts & KWH. As you noted there isn't a method to reset any of the values in the controller via programs. You will also notice there isn't a easy method to assign a variable to the iMeter in hopes of doing something with the data. As you also noted information from the Energy Display also can not be polled even though its available specifically the temperature even though the E-DOCS clearly state the data is available. At this time your only recourse (IF) you wish to continue to use cheap plugin power meters is to use the various Z-Wave devices that support energy monitoring. If this energy monitoring / energy management is more than a casual fad than you need to invest in a Brultech Green Eye Monitor (GEM).

Random (unsubstantiated) talk in various forums indicates Smartlabs i3CS is supposed to offer more features. Whether or not they even consider increasing the prefix has already been seen by some newer devices. I think you may be more familiar with this than I in this regard as many new devices generate new values when a level 3 error log is invoked. Features already seen in the wild are send clean up messages, smart hops, blink on error, and the ability to turn RF / Power Line on-off. They have also increased their RF output on at least four products now shipping: HUB II 250 feet, HUB Pro 250 feet, Dual Outlet 250 feet, Range Extender 200 feet from the standard line of sight 150 feet. The three items I believe they need to focus upon is better security whether it comes in the form of encryption. Better error correction, and moving the antenna for all hardwired devices to the front of the device. If we assume they continue to increase the power output while staying with in the FCC guidelines it will give Z-Wave a shot to the body. Besides the most obvious con's about Insteon is zero support from third party hardware makers. No 3rd party lock support that offers real time feed back of lock / unlock. Zero support and feed back to the community and other vendors offering Insteon as a product line . . . All of these items supersede a what (IF) scenario of getting a Insteon device having the same MAC address. You have a higher likely hood of getting struck by a drunk driver than receiving a duplicate hardware.

Glad it all worked out and the swap went smoothly. For the benefit of others can you offer a little more insight to the hardware revision, production date on the white sticker on the bad unit. If you could also indicate what the ISY firmware was in the Admin Console and offer insight as to what exactly was wrong with the unit on hand being *flaky*?

I've thought about this issue way back in the day when I thought Insteon would take over the entire Home Automation (HA) space. That was back in 2007 - 2009 period when HA was still very much a hobby. Now, given the massive adoption of Z-Wave / ZigBee, BLE, WiFi, the odds of the 16 million codes being used up is less of a concern. As you noted (IF) that was to be an issue a return of the product would be the only solution moving forward. But its safe to say if you ever received a duplicate MAC address for a Insteon device you better consider buying a lottery ticket!

Also, one thing that needs to be called out in case it wasn't made clear anywhere in the forums. Do not name the new device the same (literal) name! Doing so will cause the controller to *attempt* to swap the two and at some point it will get confused and than declare a fault. You don't want to end up there because it will screw up any programs, scenes, links, that were there before. You can certainly call it dog2 for example if dog was the existing switch . . . Once the swap has been completed you can rename it back to the old name say dog.

Add in the new switch and name it what ever then go to the (old) existing switch and right mouse click and select replace with. Follow the prompts that show up and the ISY will reboot. The new switch will *assume* the name and all the attributes of the old . . .

On a quick tangent was solar not an option for those battery powered shades? [emoji53]

Harold, Please take one of the spare KPL's and wire it to a extension cord you can sacrifice and plug it into the same outlet as the PLM. This will tell you more than anything at this point. ========================= To bestow knowledge is power - But only if it promotes positive results in others. The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

I believe its best to update the firmware to 4.3.26 on the remote system and just carry on. Keeping in mind you're using Admin Console on the Mac which is also using 4.3.26 which kinda makes sense as to why the Help -> About says: UI 4.3.26 Clear as mud?

Post up a screen capture of both systems blocking out the UUID of course for privacy reasons.

Can you provide a screen shot of both for us to review? Also, I was actually expecting you to say the UI was different and not the firmware. Since you haven't even upgraded the local controller I am not sure how 4.2.30 would appear on the remote system. Are you sure the Admin Console you're using is in fact 4.3.26? Also, if you clear the Java Cache on this local computer let us know if you see the same thing when you remote back into the other controller when you select help -> about.

If you watch the Admin Console for just one I/O Linc does the status change from on to off when you press the black set button? If you do the very same for the other does it reflect the true status. This must be true before you can even consider the programming aspect.

I am going to (Assume) it used to work at some time if it did. Then, you have a comm issue where the signal isn't making it back to the controller. If you press on the I/O Linc does the status change in the Admin Console?

The only way the firmware would show up at 4.2.30 is (IF) it was updated.

Almost anything is possible when speaking about Smartlabs these days. But, I do not for see them removing support for legacy products from the PLM. Its more likely you have a communication issue, poor coupling, or defective items.

Hello Harold, You've endured quite the journey so I will leave you with a quick thought. Normally if the KPL makes a noise it indicates improper wiring, incompatible load, or there is indeed a fault in the device. As painful as it might be seeing that you have done pretty much what can be done. May I humbly suggest you take one problem KPL out and wire it to a spare extension cord you can sacrifice and wire the device to it. This will allow you to bring that KPL to the PLM. Since the device is already having issues you can take a staggered approach which is hard reset the KPL. Once done use the restore device and see if the KPL operates as expected. If it doesn't delete the device from the ISY and add it back once its in the system recreate the scenes and report back if it operates as expected. NOTE: If doing all of the above using the extension method and hard resetting and adding back the KPL does not yield positive results it may very well be damaged. If under the 2 year warranty period engage Smarthome and they will get you squared away.

1. Are you sure you added the KPL correctly? Can you let us know how you added the device? 2. Can you offer a screen shot of the KPL in the device tree?

Did you *right click mouse* and select group?

You also can't enable two node support until such time as UDI / Smartlabs offers it via software.

It also doesn't matter right now because UDI and Smartlabs hasn't provided the support via software to enable this feature! I've only been asking for this support for over a year now . . .

As far as I am aware the client has been going strong for about 11 months now. I personally would not go to that distance but than again it wasn't my call at the time. I just so happen to be the grunt on site at the time so did what they asked. The only obvious visual I saw while on site was it took about 30-45 seconds longer to bring up the Admin Console. After the Admin Console was fully loaded everything operated just fine . . . I suspect if there were lots of programs running in the back ground perhaps some latency would be seen. Then again I didn't stick around to find out (IF) he did! Ha . . .

The (approx 75') distance is from the ISY to 2413S PLM . . . This in my mind exceeds what is the norm and practicality but the client had a need at that time. So the only recourse was to use the highest quality cabling and wire both from that distance. I don't believe this scenario would have ever come up if the IR requirement wasn't the pressing issue at the time. The client didn't want yet another box to relay the IR commands which of course would have required more cost and complexity to the final install. My feed back was simply to offer this has been done with the caveats listed above. With anything I am sure YMMV as my personal home install I saw issues at 40 feet. Then again I wasn't using CAT 7 but CAT 6 cable and it wasn't shield cable either. Since my mini reno has been completed its down to a more reasonable 15 feet using CAT 7 cable.