Broyd

Hi Techman, I link the device using add new Insteon device. My PLM V 1.B adds the device with the device's version number correctly. The V 1.5 PLM however, does not, using the same linking method. I posted this just in case it showed up with the above mentioned PLMs.

I have a v1.5 PLM and with that unit, the versions of all linked insteon modules was always v.00. Something to be aware of?

Just for the record, on my panel, an older GE my breakers ( half height ) follow this pattern A A A A B B B B A A A A B B B B etc.

Hi Techman, These are new leak sensors that I got from Costco - a 4 pack. I triggered the sensors by tapping the contacts on my toungue and immediately dried them off with a paper towel ... And then I waited to see what happened, looking in the event viewer and then the log. Once triggered, these sensors send out 12 signals. The sensor sends out 9 WET (switched ON) signals, each of which is spaced at approximately 16.5 seconds apart over a period of 2 minutes and 11 seconds. Then it sends out a single signal at 9 minutes following the last signal; then another at 21 minutes 30 seconds; then another at 21 minutes and 39 seconds. I have waited an additional day and I get a total of 12 signals. As already posted, you must press the set button on the sensor to clear the wet condition. LeeG answered my question.

Hi Jon. That wasn't my question. I was wanting to know why I did not see all 12 'switched on' events in the log. ( I know you can only reset the wet condition by pressing the set button ).

Hi there. I received 4 links sensors having this info: Leak Sensors (2852-222) Sticker says: 1015 REV 2.3: Admin Console says (2852-222) v.43. These sensors send out a total of 12 WET signals over a span of about an hour when the sensor gets wet. I dry it instantly but as previously noted, the WET signals continue. I count them when using a program that adds 1 to a counter with this statement IF Control '37.82.3E-Wet' is switched On My question is: In the log, I only see the first occurrence of the sensor getting wet. None of the other 'switched on' signals are recorded, even though they show up in the event viewer. Is this normal behavior for the log?

If you aren't fussy or squeamish, touching the two contacts on your tongue works fine. The current is so low that you don't feel any electrical effects.

Thanks LeeG! Appreciated.

Thanks LeeG. Is there any collected documentation on understanding the messages in the event logs or is that scattered helter skelter here and there? And on a different note, the ISY is obviously measuring time on a much finer scale when manually setting the brightness using the dimmer paddle. Has anyone suggested it would be a great addition to have the time in the logs and events show to 1/10 or 1/100 of a second?

Yes thanks. I noticed that exact behavior. I wasn't sure if the device was sending a value or the ISY was estimating a value. So this means that the dimmer never sends out it's current state? All we see is an estimate by the ISY? Thank you very much for taking the time to explain this stuff!

Thanks again LeeG, it's interesting that when you press and hold the paddle to brighten or dim the device, the status seems to be reported to the ISY correctly - not always but mostly (BMAN SMAN). Brightening to full on gives a status of 255, 0 for full off. Seems like a deficiency in the dimmer software ... A DON or DOF should always include the status (0-255) ...

Thanks LeeG, What generates these two messages? The dimmer or the ISY ( based on the On Level set in the ISY)? Tue 02/02/2016 10:21:51 AM : [D2D EVENT ] Event [3C 75 CD 1] [sT] [127] uom=0 prec=-1 Tue 02/02/2016 10:21:51 AM : [ 3C 75 CD 1] ST 127 Thanks!

Is this a possible problem? (running firmware 4.4.2) I have dimmer switches for example (2477D) Dual Band SwitchLinc Dimmer v.45 and other dimmers that behave the same way. In the admin console, I set the device to 50% On Level [Applied Locally]. If I tap the switch once (locally), it will ramp up to 50% AND THEN if I tap the switch once more sometime later, it will ramp up to 100%. Now here is the possible problem. In the ADMIN COLSOLE when looking at the dimmer, when I tap the switch once, the "Current State" reads 50%. But then when I tap the switch once again, the "Current State" STILL reads 50%, NOT the 100% that the dimmer is actually now working at. Could this be a problem? Level 3 diagnostic messages: Tue 02/02/2016 10:21:51 AM : [iNST-SRX ] 02 50 3C.75.CD 00.00.01 CB 11 00 LTONRR (00) Tue 02/02/2016 10:21:51 AM : [std-Group ] 3C.75.CD-->Group=1, Max Hops=3, Hops Left=2 Tue 02/02/2016 10:21:51 AM : [D2D EVENT ] Event [3C 75 CD 1] [DON] [0] uom=0 prec=-1 Tue 02/02/2016 10:21:51 AM : [ 3C 75 CD 1] DON 0 Tue 02/02/2016 10:21:51 AM : [D2D EVENT ] Event [3C 75 CD 1] [sT] [127] uom=0 prec=-1 Tue 02/02/2016 10:21:51 AM : [ 3C 75 CD 1] ST 127 Tue 02/02/2016 10:21:51 AM : [iNST-SRX ] 02 50 3C.75.CD 19.6E.0A 40 11 01 LTONRR (01) Tue 02/02/2016 10:21:51 AM : [std-Cleanup ] 3C.75.CD-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Tue 02/02/2016 10:21:51 AM : [iNST-DUP ] Previous message ignored. Tue 02/02/2016 10:21:51 AM : [iNST-SRX ] 02 50 3C.75.CD 11.01.01 CB 06 00 (00) Tue 02/02/2016 10:21:51 AM : [std-Group ] 3C.75.CD-->11.01.01, Max Hops=3, Hops Left=2 Tue 02/02/2016 10:21:51 AM : [iNST-INFO ] Previous message ignored. Tue 02/02/2016 10:22:13 AM : [iNST-SRX ] 02 50 3C.75.CD 00.00.01 CB 11 00 LTONRR (00) Tue 02/02/2016 10:22:13 AM : [std-Group ] 3C.75.CD-->Group=1, Max Hops=3, Hops Left=2 Tue 02/02/2016 10:22:13 AM : [D2D EVENT ] Event [3C 75 CD 1] [DON] [0] uom=0 prec=-1 Tue 02/02/2016 10:22:13 AM : [ 3C 75 CD 1] DON 0 Tue 02/02/2016 10:22:13 AM : [iNST-SRX ] 02 50 3C.75.CD 19.6E.0A 40 11 01 LTONRR (01) Tue 02/02/2016 10:22:13 AM : [std-Cleanup ] 3C.75.CD-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Tue 02/02/2016 10:22:13 AM : [iNST-DUP ] Previous message ignored. Tue 02/02/2016 10:22:13 AM : [iNST-SRX ] 02 50 3C.75.CD 11.01.01 CB 06 00 (00) Tue 02/02/2016 10:22:13 AM : [std-Group ] 3C.75.CD-->11.01.01, Max Hops=3, Hops Left=2 Tue 02/02/2016 10:22:13 AM : [iNST-INFO ] Previous message ignored.

Hi larryllix, Nope, I'm not en electrician. I was borrowing from the lexicon. I only have a B.Sc in chemistry with a lot of computer science. ... doesn't mean I haven't had any experience doing electrical work though BTW I'm from Nancy Greene and Kerrin Anne Lee-Gartner country.

Hi stusviews, Thanks for the info on the possible XPCR interaction with Insteon signals. But I am surprised that by moving the 994 and the I/OLinc to the same side of the split that all of the communication problems have cleared up. I would still expect to see something. However, I am now alerted to any other peculiarities I might see. So far, so good! On the breaker interchange ... The two breakers I have interchanged are half-height and the circuits they control are completely separate from one another. The branch circuits they each control have no common connections - period. The neutral wire from each of these circuits connects to the common neutral buss in the breaker panel along with the 25 or so other neutral wires from the remaining branch circuits served by the breaker panel. When the house was originally wired, those two branch circuits could have just as easily been installed next to one another on the same buss feed as I have now configured them . Both circuits are lightly loaded and so interchanging them makes no or very little difference to the load balancing on the two legs of the split phase. I am trying to make sense of your comments regarding the current carried in the neutral wire; the two circuits I have interchanged are completely separate so interchanging them does not affect the current in the neutral wire of either circuit in any way. In order to be taking about a current in the neutral line that can interact in some way, it seem to me that you are telling me about a situation where the neutral line is shared between the two legs of the split phase such as you find when a 14-3 cable is connected to the panel by a double pole breaker that then feeds the outlets on a kitchen counter. In this situation the upper and lower hot contacts of a duplex receptacle are fed by the the two splits of the single phase feeding the house. Measuring the voltage between these two hot contacts gives you 240 volts. This setup allows you to plug in two heavy duty appliances ( a microwave oven and an electric toaster ) into the same duplex receptacle without blowing the breaker. But in this instance, it is ONLY the difference in the current loads between the two appliances that is carried by the neutral wire. If two 15 amp appliances are plugged in, the neutral carries NO current. If a 10 and a 5 amp appliance are plugged in, one leg carries 10 amps, the other leg carries 5 amps and the neutral carries the difference, 5 amps. I can't visualize a 'ordinary' situation where a neutral wire would be forced to carry any more current than the controlling breaker could supply. You could certainly setup a situation like that; feed a single 10 gauge wire through a 30 amp breaker and return the current though a 14 gauge wire in a completely different cable but that is not what I would call 'ordinary'.

Well, so far I have not experienced any Insteon or X-10 communication failures, both on sending or receiving. I did have a difficult time establishing clean communication with an I/OLinc until I realized the PLM and I/OLinc were on opposite legs of the split phase. RF bridging using a pair of the new light dimmer modules on opposite sides of the split and positioned near the I/OLinc did not improve the situation very much. My final solution was to rearrange two circuit breakers in my electrical panel such that they were on the same side of the split and immediately adjacent to one another; the electrical circuit path between the two breakers in my panel is 3/4 of an inch and the Insteon 131.65 KHz power line signal did not have to travel back to the main buss to establish the communication link. This solved that communication problem perfectly.

Thanks for clarifying stusviews. I am the guessing that the XPCR would damage an Insteon signal in such a way as to make the communication fail? Or cause communication errors - slowdowns? Can you suggest an example of what might happen thus giving me an idea of what I might watch for? Thanks much!

Thanks stusviews and Brian H for the heads up on the XPCR. I will be alert for any unexpected or unusual X-10 behavior. I am hoping the XPCR will fit my needs as the XTB-IIR is a lot more expensive (but obviously a much better device). I still use X-10 for some control ... I have some modules that have been running reliably for more than 15 years.

Hi Michel, I like the format you have set up for handling the Time Zone selections and DST. Well done! The rule I use is "North America-Canada". Should this not say "United States-Canada"? I think Mexico is part of North America ... but United States is not all of North America ... One other item. I am using a 1280X1024 pixel screen and use the default font size of 12. When I press the Change Location button, only the Latitude (Lat) is displayed. The width of the Change Location panel appears to be 780 pixels; to display the Longitude (Long) on that panel as well, that panel width needs to be increased to at least 785 pixels. Also the red X in the upper right corner of that panel does not work; you have to press the 'Cancel' or 'OK' button to close the panel.

I got one of these devices off of eBay (about 60 bucks). Fixed up all of my weak X-10 signals including those generated by the ISY - PLM and phase coupled my X-10 signals everywhere in the house! It is also Insteon frendly. It does not appear to interfere with Insteon signals. X10 PRO XPCR Signal Coupler Repeater Booster http://www.ebay.com/itm/X10-PRO-XPCR-Signal-Coupler-Repeater-Booster-Factory-Fresh-/161014133300?hash=item257d30b234:g:jRUAAOSwRLZUFFY1 There are MUCH better units out there but they cost 3 times as much.

On further investigation of how my electrical panel is constructed, if A and B represent the two legs of the split phase supply, then single width breakers are connected as A A B B A A B B etc. starting at the top of both the left and right sides of breakers in the panel and moving towards the bottom of the panel. The power connection between an A A or B B pair of breakers is very short, about 3/4 of an inch. I relocated the circuit breakers again so the the ISY-994i and the I/OLinc are on an adjacent B B pair. The bi direction communication between these two devices has been completely cleaned up; the insteon powerline signal does not even have to travel back to the main circuit panel buss. I am not sure why bridging the split phase with the new lamp link dimmers wasn't as successful. Thanks Teken for the information on the beacon test. I tested this and I now have a much better understanding of how this works.

Hi Michel, You are correct. Creston remains on Mountain Standard Time all year long. They DO NOT observe Daylight Savings time. So how would you set this up for Creston on the admin panel page? I haven't loaded that new beta yet so I haven't seen how that page works . Do you have the ability to select a specific time zone by picking a city (Calgary, Alberta) AND then select NONE for DST, AND then still enter a longitude and latitude so that your sunrise and sunset times are accurate? Thanks! This was one of the reasons I haven't switched to the new beta. I live in the center of The Pacific Time Zone almost directly north of Spokane Washington. I would pick Vancouver BC to set the timezone but then my sunrise and sunset times would be off by about half an hour each. So if I can pick Vancouver and then set the longitude and latitude, I would be very happy with that setup.

Hi Michel, I have a question about how a persons DST rule and his physical location (sunrise/sunset) interact. I am guessing that you use a close by city to determine what DST rule is used for that area AND that you then allow the user to set the appropriate longitude and latitude, which is then used to calculate the sunrise and sunset times. Is this thinking correct? A weird exception ... ? The South East corner of British Columbia, Canada includes the city of Creston. I live about 100 miles from that city. They use a special time zone rule. They MOVE the time zone boundary about 60 miles east and west of Creston twice each year such that the time the residents experience never changes as the rest of British Columbia and Alberta switch back and forth between standard time and daylight savings time. Is it possible to automatically accommodate this situation?

The beacon test results seem confusing to me. The LEDs flash but even with all dimmers starting in the off state, I see both red and green led flashes from these devices. I will do more testing to try and figure out what the beacon test is telling me. As I have already mentioned, I know exactly which breaker feeds every individual light, outlet, or device. The test I made was a100% positive one. I measured the voltage at each circuit breaker in the electrical panel; if I am on the same leg of the split phase, I see 0 volts; across the split and I see 242 volts. I will make a concerted effort to capture the diagnostic level 3 info. Hopefully if I post these diagnostics someone can explain the listing to me.

Thanks stusviews for the heads up. I carefully checked the two 120 volt circuits for which I interchanged the breakers before I exchanged them. The circuits are not tied in any way. And the loads on the two circuits are very similar and very light. The neutrals of each circuit both go back to the neutral buss and are not related in any other way. There was no other way I could get the 994 and the 2450 on the same leg of the split phase. I have very carefully mapped out every lamp and outlet and other devices (stove, hot water tank etc.) in my house and know exactly which breakers control each one. There was no problem making this exchange and it did cure the 'could not write to device' messages that I was previously getting. I did install two dual band devices across the phase split before I exchanged the breakers and the problem was still there; that's what lead me to do the breaker exchange. Edited for spelling.