larryllix

Some observations: If you have three panels and only three SignaLincs you can only cover one phase of each panel, assuming your panels have both phases of your 120/240 vac system in each panel. If you have that many dual band devices the SignaLincs seem redundant. That and pony panels are usually very close to the main panel so one SignaLinc (or dual band device), on each phase, close to the main panel would be a good central star point for the whole house. A passive signal coupler can be a detriment to an Insteon system as the Insteon signal when passed to the other phase of your service will be out of phase with your active dual band units on that phase and therefore the Insteon signal should be out of phase (in synchro with that 120v phase) and possibly cause subtraction of the signal magnitude. Further study of that theory is in order. Insteon devices have some collision detection, built in, and may avoid that out-of-phase signal situation from happening. That could also be true provided the out of phase Insteon signal is strong enough to trigger the collision detection algorithms in the transmitters. I would check your hop counts in your event log while you activate each device from ISY. Then remove all SignaLincs to see what the effects are and determine whether one, two or three should go back in. Running out of receptacles?

How did you determine the program did not run? Your switch may not be properly linked to the ISY. Did you factory reset the switch before usage?

"An expansion slot which could be utilized to install and support other protocols such as a Zigbee" My bad.

Does this mean that Zigbee is simply a protocol on top of the Zwave frequency?

...and the "is not" will only run the "else" section, containing no program code. But it will terminate any then section running. If ( Control is switched on or Control is switched fast on or Control is switched fade up or Control is switched fade down ) and Control is not switched off

What turns the rear yard light manually? Try this idea on Program 1 -------------- If MS is switched ON Then Set spotlight On Wait xx minutes Set spotlight Off Else -- Program 2 -------------- If MS is switched ON Then Set RearYardLights ON Wait xx minutes Set RearYardLights Off Else -- Program 3 -------------- If ManualSwitch is switched On '*( runs Then) and ManualSwitch is NOT switched Off '* (runs else) Then disable Program 2 Set RearYardLights On Wait 6 hours '* (just in case) run Program 3 (Else) Else Set RearYardLights Off enable Program 2

How far away from the ISY is the MS? If you view the event log in level 3 you can see how many hops the signal has to do. More indicates more devices have to retransmit the signal to get there. My MS to lamps takes from about 1/2 second to 2 seconds (rarely) at times for an X10 MS and an Insteon responder device. Faster for Insteon to Insteon. If I link the two devices together the delay is not noticeable at all but then I cannot interfere with the light response with an ISY program condition. eg. time of day. If you have lot of electrical interference on your system it can take some retries to get there. Does the signal not work at all sometimes? If you post the Event Log on level 3 somebody can analyse it and probably tell you what is taking the delay so you may be able to alleviate that.

You might try uninstalling all remnants of Java and old versions. Reboot the PC and reinstall a fresh d/l version of Java. I believe the Oracle website has cleaners to do this so they may have previously encountered many complaints for the same thing.

We like them a little stiffer Used from the bottom there should be less chance to wander out the side of the drywall cavity. Make sure the attachment points are very secure. They can be really hard to retrieve inside a joist cavity covered in drywall. (closet hole time!) When the Irwin Speedbore gets stuck and you pull back it can come loose easily. http://www.homedepot.com/p/Milwaukee-24-in-Bit-Extension-for-Selfeed-Bits-Auger-Bits-and-Hole-Saws-DISCONTINUED-48-28-4016/100007181 The other way is to get a snap in aftermarket 2x3 electrical box. Cut your hole and drill through your invisible 2x4 from there, using a long extension bit to get the steep angle. Drill your hole up through the bottom 2x4 plate and floor sheeting and then use the "weight on a string" method to dance a weight through both holes from the top. After you get the cable pulled up thread on the receptacle box (tie a knot) and mount it into the drywall hole. Mount your thermostat on the 2x3 box. Some adapter plate may be needed but probably not. You may want to stuff the box with insulation to avoid inside wall draughts affecting the operation.

I assume you have rebooted your computer at some point in there too. I find Java has been acting very strange for the last few months and sometimes that help clear up some of the quirks. Java seems to act up particularly after my computer sleeps. The Admin Console hardly ever works after being left alone for more than 15 minutes. I believe this is mostly some sloppy behaviour introduced in Java in the last 6-8 months. The Java 8 on my Win7 x64 machine seems to behave better most of the time.

You have different ISY firmware for sure. The Java cache and applets needs to be flushed out and the fresh versions of the Admin Console reloaded to match the ISY994i firmware. See the thread on the new firmware announcements (I would link to it but using a new browser and I don't know how to use multiple tabs) In Windows goto the control panel and then select Java and you should see a tab to delete your files and applets, Edit: http://forum.universal-devices.com/topic/14136-release-4215-rc5-is-now-available/ There are links there to install new applets etc.

On the 2444ZTH unit (I have two but no wired units) the humidity reading updates on a clock basis. On batteries it updates every 5 minutes and on PS it updates every 1 minute. Silly to pick a secondary humidity value to do that but it acts like a heartbeat to indicate life. The temperature only updates by exception (on changes outside of the set bandwidth allowance from the last value sent). Temprature is NOT queriable unless the 244ZTH is in linking mode. My older firmware unit can be set from the ISY but the newer firmware unit cannot be set from ISY. Yes Insteon has been having problems or they wouldn't keep getting more 10 year olds to change their firmware. Again my experience only applies to the wireless 2441ZTH units. YMMV

No, Network Module not required. The whole thing is set up inside the WC8 board admin console. The instructions are so poorly written in Chinlish that some of them are just wrong and may be completely opposite of what you need to do. Put your ISY IP in the IP address (first column) (no "http://") Put your ISY rest command and variable access address in the get URL (second column) eg. "/rest/vars/set/2/6/" Put your ISY admin console user name and password encrypted with Hash64 method found online. Silly method but it just works that way. When you encrypt this makes sure the format is exactly as shown. "Joe:MyPassword" Now in your PLC code when you do a "WEBSET URL1 RAM5" the ISY variable will suddenly update to whatever is in RAM5. Keep in mind this WC8 board does not support 1wire devices well. If you use longer cables the board may stall PLC code for chunks of time and sometimes reboot. This means you really can't have an initialisation setup if you mind it being run at random intervals. From what I can gather the WC8 shares memory between the 1wire bit-banger interface, the WEBSET commands and a few other processes. When the 1wire has errors or retries everything suffers. After about 8-9 firmware updates to make a DS2438 sensor work (sheepwalk SWE3) I gave up on humidity sensing. The WC8 designer has since removed support of the DS2438 on the newer versions of firmware for the WC8 board.

Did you delete it in the ISY, factory reset the 2441TH, and then re-find and link it in the ISY?

Insteon devices use a completely different network using radio frequencies and powerline codes to connect with fellow Insteon devices in your home. This "Insteon Network" is not related or dependant on your home network (LAN) or the Internet in any way. However, As LeeG stated above, your LAN (home network) handles the communications between the Admin Console and your ISY box.

Does your humidity update regularly?

Nice! Happy programming!

I assume we are discussing the Insteon 2842-222 model. Many of us use the MS units with the 'Off' disabled as it makes it easier to manage time-offs in ISY through decision making logic. This may be set that way in your unit but I can't explain the "off" if you have ever seen one. There is a jumper that sets this preference and if the rightmost jumper is on the two p[ins then the software in ISY options at the bottom of the device page sets that option in software. Note the Linking mode must be set on the MS first. The downside is the MS will never indicate "Off" in the ISY and "status" based logic cannot be used. A peel at your Events in level 3 may be usefull to observe the consistency of how many "hops left" are involved in it's communications. This may give an indication of flakey communications with the PLM.

I tried setting Retries=0 and then I tried setting the MS sleep after detection for 0.5 minutes in order to stop multiple motion triggers with no detectable changes in events recorded for either setting. Next I recorded events with the MS linked to the Switchlinc in a direct link scene. Only one program trigger event happens using this method. It seems the MS sends a different pattern to the ISY in this case and only causes a single event trigger. I am surprised the PLM and the MS don't have a similar link to make the MS act the same as when linked to a Switchlinc. This could avoid a lot of ISY CPU time processing useless repeated signals. This also doesn't happen with the RemoteLinc keypads or X10 keypads. Note: Time lines were removed. Wed 10/01/2014 05:29:46 PM : [iNST-SRX ] 02 50 2D.67.81 00.00.01 C7 11 01 LTONRR (01) Wed 10/01/2014 05:29:46 PM : [std-Group ] 2D.67.81-->Group=1, Max Hops=3, Hops Left=1 Wed 10/01/2014 05:29:46 PM : [D2D EVENT ] Event [2D 67 81 1] [DON] [1] uom=0 prec=-1 Wed 10/01/2014 05:29:46 PM : [ 2D 67 81 1] DON 1 Wed 10/01/2014 05:29:46 PM : [D2D-CMP 0067] CTL [2D 67 81 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 10/01/2014 05:29:46 PM : [D2D-CMP 006F] CTL [2D 67 81 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 10/01/2014 05:29:46 PM : [D2D-CMP 0023] CTL [2D 67 81 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 10/01/2014 05:29:46 PM : [D2D-CMP 007E] CTL [2D 67 81 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 10/01/2014 05:29:46 PM : [D2D EVENT ] Event [29 C3 DB 1] [sT] [255] uom=0 prec=-1 Wed 10/01/2014 05:29:46 PM : [ 29 C3 DB 1] ST 255 Wed 10/01/2014 05:29:46 PM : [D2D EVENT ] Event [2D 67 81 1] [sT] [255] uom=0 prec=-1 Wed 10/01/2014 05:29:46 PM : [ 2D 67 81 1] ST 255 Wed 10/01/2014 05:29:47 PM : [iNST-SRX ] 02 50 2D.67.81 00.00.01 C7 11 01 LTONRR (01) Wed 10/01/2014 05:29:47 PM : [std-Group ] 2D.67.81-->Group=1, Max Hops=3, Hops Left=1 Wed 10/01/2014 05:29:47 PM : [iNST-DUP ] Previous message ignored. Wed 10/01/2014 05:29:48 PM : [iNST-SRX ] 02 50 2D.67.81 2A.1C.95 41 11 01 LTONRR (01) Wed 10/01/2014 05:29:48 PM : [std-Cleanup ] 2D.67.81-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Wed 10/01/2014 05:29:48 PM : [iNST-DUP ] Previous message ignored. Wed 10/01/2014 05:29:49 PM : [iNST-SRX ] 02 50 2D.67.81 11.02.01 C7 06 00 (00) Wed 10/01/2014 05:29:49 PM : [std-Group ] 2D.67.81-->11.02.01, Max Hops=3, Hops Left=1 Wed 10/01/2014 05:29:49 PM : [iNST-INFO ] Previous message ignored. Wed 10/01/2014 05:29:50 PM : [iNST-SRX ] 02 50 2D.67.81 11.02.01 C7 06 00 (00) Wed 10/01/2014 05:29:50 PM : [std-Group ] 2D.67.81-->11.02.01, Max Hops=3, Hops Left=1 Wed 10/01/2014 05:29:50 PM : [iNST-INFO ] Previous message ignored.

I haven't noticed a detectable brightness change from a straight switch to a SwitchLinc at full brightness. Big differences can be noted with many other dimmers and since most don't have any smarter circuitry powered up 24/7 so that is understandable. Other dimmers need to start timing from the waveform zero crossing, charge some capacitor-based variable delay circuit and then fire the Triac ASAP. Smarter dimmer circuits can fire the triac right at the zero crossing and have no waveform rise time missing and thus less switching high-frequency harmonics generated. Easier on the bulb ballasts. I haven't experienced any shorter life with my SwitchLincs and CFL bulbs. OTOH, I populated my new house with all new CFL bulbs and most of them blew within a year the first round . This was all before I had any dimmers. The upside down, potlight, construction was never a good idea for CFL bulbs. The ballast overheated. I had one that lasted a week and the second one from the pair, less than an hour. Most are replaced with LED bulbs now.

Does my Retries=0 file not show that the MS is not sending the commands more than once? I thought it hadn't resent the On and Cleanup a second time? http://forum.universal-devices.com/index.php?app=core&module=attach&section=attach&attach_id=3558

Have you also noticed the 'beep duration' doesn't affect the length of beep? Mine aren't worth beeping as they can't be heard more than 10 feet away (3m) if there is even wind outside.

This was only a test program to understand Insteon congestion vs ISY program decision speed. Normally an Off would not be sent this fast and the On-Off-On-Off sequence would not be seen. My question was about methods to eliminate some of this Insteon traffic for events like MS to lights that don't need to be that secure. The extra transmission ever time 2 seconds later seems like a waste of bandwidth and I have events that take up to 20 seconds to respond at times. That's annoying when a beeper is alerting me to perform a certain device Off scene and it takes that long or never seems to complete. It's real weird to trigger a SwitchLinc and have the first line of a program code function 20 or 30 seconds later. Now I do have an X10 beeper and I had several programs that are all trying to turn off that beeper simultaneously. In view of this delay I have tried a status check program to avoid multiple X10 Off signals but it occasionally thinks the beeper is already off and won't send the Off command. Sometimes the X10 beeper just won't turn off for some reason but it seems that X10 doesn't play well with Insteon on the PLM. It seems X10 transmissions can clobber Insteon and vice versa. I have since incorporated a 2 second delay after every X10 command and sequenced them to make allowances for the clash. This definitely helps things work more reliably. Rethinking some of this, with your inputs, my question is; will linking a MS with a device give an ACK to stop the retry of MS transmission and relieve some of the Insteon congestion?

You could also make the switch beep a few times to teach that snoop a lesson!

You can't stop the SwitchLinc Dimmer from dimming the lights wired to it (locally) but you can insure they don't stay that way long with a program that monitors it.