larryllix

You talk like an electrician. They always use the name of a popular fuse company for the phrase "neutral bus" This is very common in the trade and always gives me a giggle how it developed.

I don't think I want to open the "glow in the dark balls" discussion.

After the second time it happens, just replace the PLM. I have never had an All On/Off event but ordered a new one. Then the question comes what to do. If you do not install the new one you could find out it is bad a year down the road when you need it, or worse after the warranty is over. Switch to the new one and keep my old one as a backup. They bot are tested now. In your case I would rebuild it replacing the caps, as per Brian H. Then I would switch them back after a month or two. Now you will have two tested PLM's you can rely on.

My latest two Leak sensors send Wet On or Wet Off (may have been Dry On, or both) depending on how long you hold the button.

ISY has never been aware that an All On has happened. This should mean that ISY doesn't issue the problem. The feeling is that Insteon signal get confused somewhere and get interpreted as this All On signal in the RF, PLM, or PLM interface to ISY. ISY to Elk, ISY and Elk communications have proven very reliable.

In V5 there is no "control" as the word has been removed. We will all have to start using the verbs "switched" and "status" to be compatible with pre and post v5.

I was more attempting to resolve the crossover complaint by asking questions in order to understand how it could happen in the first place and help the OP's awareness, and mine. If the mechanism is known there should be an apparent resolution to it. It sounds like it is but would sacrifice some other shared features that may be wanted.

How would commands for house get to the other house?

KPL buttons and the LEDs behind the buttons are separate Insteon devices. One is a controller and one is a responder.

No Network Module required for ISYLogger to grab variables on a regular clock schedule and log them in CSV format. http://forum.universal-devices.com/topic/7293-isylogger-latest-version-v067/

Only to link to other Insteon modules. The user manual does not address ISY linking. ISY doesn't require that technique.

There is no linking mode needed on newer LampLincs. Pressing the link button may lock it out of co-operating??

You have a PLM manufactured in the 3rd week of 2014 so it may be about the right time for the PS caps to give out. I guess I would try factory resetting the PLM and then use the PLM restore command and let it rebuild all the links. Of course make sure you have a good backup of the whole ISY before doing anything this radical. This may fix the issue (temporarily) or make it better but I think I would order a new PLM as a longer term solution making sure you get a version 2.1 or better. Then I would think about the cap replacement for the old unit as per Brian H posts. if you aren't electronics soldering savy find somebody who is and buy them a case of beer.

I have no Weather Module for ISY but can the values not be stuffed into variables? Maybe in V5? Is so then the variable values can be logged using io_guy's ISYLink to poll them and log them in a format loadable into Excel.

Yes, true. I have forgotten about those ones coming out. Unfortunately I would require a BT access point from my WiFi to access them, as a bridge/hub to work with HA. . I have an old DLink? BT access point, from years back, but since it never became popular to do things that way, and was never supported with software it became expensive garbage.

AFAIK all smart bulbs require a hub. OTOH IIRC there was a bulb that came out recently that connects Wi-Fi directly. You can overflow your protocol with more than 32 devices on a Wi-Fi network, so I have been told, where the overhead in the protocol swamps the actual data, so Wi-Fi for HA may not be a good thing. I have four Hues, require a hub and the ISY network module can talk to the hub just fine. No feedback though. Hues have a great interface but colours are lacking. Whites are colour temperature adjustable but low brilliance. RGBW are reported to be somewhat better. I have three MiLight bulbs and five MiLight RGBWW strips and the ISY network module can talk to the two hubs (4 unit addresses per hub) just fine. MiLight bulbs and RGBWW strips have really nice and rich colour, single white, a sloppy protocol interface, very cheap, and do not report status either. When you install smart bulbs how will you turn them on? How will your wife and kids turn them on? Guests? ISY can do it well mixed with Insteon modules/bulbs but you still need a piece of hardware on the wall or MSes etc.. My PLM is on a special short circuit right beside my main panel for powerline signal spread. It is the centre of your house wiring.

Which UDI model do you have?

HA systems run on the last change of status sent by devices. That is all they know. ISY will only reflect the last thing it has been told by the MS. If the device is new, or ISY has just rebooted, the field will be shown blank (as an indicator) as ISY cannot know the information. You cannot query Insteon battery operated devices without putting them into linking mode first. This is a battery saving thing. Also they do not repeat messages in the usual multiple hop style of the protocol for the same reasonl.

Some confusion here. In another thread the OP changed his dark sensitivity to about 75 and this seemed to help his seemingly defective MS. Apparently the factory settings the MS was supplied with, weren't working for him at the time. The OP has started multiple threads with various subject matters and we may have confused complaints and timing causing some confusion with attempts to help.

I only use X10 where they are close to the PLM and guaranteed operation is not critical. If I didn't have so darn many X10 modules I wouldn't use then at all. Insteon works so much better at the end of 100' of 14/2.

I always carry on! At least my two bits worth, or was that a one bit carry?

I think we got that working after some more experimenting. Too many threads going at once??

I always forget this one. IIRC you can poll a program with the REST I/f and tell if it is True or False, no variable required. I don't like doing it that way. It doesn't feel structured to me.

Just set up an ISY program to set and clear a variable(as a Boolean) based on the MS.dark sensor trigger. Now you can use the Rest interface to poll it and use it elsewhere. Another way is to use the ISY Network Interface to stuff the same program result into somewhere else with it's Rest interface or equivalent.

I used a 5/64" bit. Usually 1/8" keeps bugs out, by some defs. I consider it a fail anyway but it was worth a try. I still can't hear the noise unless I am within a few feet and listening for I, unfortunately. Maybe I should have measured the voltage at the piezo, possibly a sub'ed Sonalert type unit may be handy. It only makes a short blip but they could be handy for testing or indicators like garage door left open where the Buzzlink is too intrusive. Well mine is.