LeeG

Yes to all three. As an FYI about the number of different Scenes a device supports, the User Guide for the device would provide instructions for linking responders to different Scenes if such capability exists. The same thing applies to whether a device is a Controller Only, Responder Only or both. The User Guide provides information about linking as a Controller or as a Responder or both. What instructions are in the User Guide, or not in the User Guide, can help clarify the capability of any given device.

The basic On/Off commands from a paddle press cannot be changed. The SwitchLinc User Guide even notes that the paddle itself cannot be used to generate a Fast On/Fast Off to override the Sense line. The Fast On/Fast Off has to come from another Controller. There are sequences of SwitchLinc Set button taps that will Enable and Disable the Sense line. The SwitchLinc sends an On command when it turns On but there is no way to distinguish whether that was from a paddle press On or the Sense line turning the SwitchLinc On. Same with Off. I don't think it would be against code to take the paddle off and stick it inside a box. At that point it would be much like an InLineLinc. Never done that but so long as nothing electrical is exposed I don't see the harm. Smarthome has a 30 day return policy so perhaps you could return the SwitchLincs in favor of InLineLincs.

Brian Would expect that will be true. I have a new FanLinc that also arrived yesterday I expect to be I2CS but have not had a chance to test it yet. Some differences could be whether extended ALDB is used as must be used with the Motion Sensor or Peek/Poke as I think will be used with the FanLinc.

You can try something like this. It is necessary to handle in two Programs so the Repeat loop does not get canceled at Sunrise. The Off Program would stop ‘Program On Repeat’ If From Sunset To Sunrise (Next day) and Program 'C1 Status' is True Then Run Program ‘Program On Repeat’ (If) Else Program On Repeat If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat every 24 hours Set 'Entry Light On' Set Living room.....etc Else -No Actions-

I'm afraid the SwitchLinc Relay w/sense does not function the way you hoped it did. There is not a separate "Sense Node" such as with an I/O Linc. The Sense line on the SwitchLinc works like the Sense line on the InLineLinc. It turns the SwitchLinc On/Off, not a separate node On/Off. Like the InLineLinc the Sense line can be overridden with a Fast On or Fast Off from another Insteon controller. Fast On turns the SwitchLinc On regardless of the state of the Sense line and Fast Off turns the SwitchLinc Off regardless of the state of the Sense Line. In fact the SwitchLinc w/sense User Guide section on the Sense line was patterned after the InLineLinc, even to the point where one sentence refers to the InLineLinc rather than SwitchLinc.

I can confirm I2CS devices are in the retail stream. The Motion Sensor that arrived today along with not being able to Set Options, all the commands to write link records were rejected with Nacks. Even though New INSTEON Device added the Motion Sensor it is not functional without link records.

Once you have the 3000 receiver I would go with the EZIO6I as it is less expensive than the EZSnsRF and it eliminates any range question. Of course if more than 4 Dakota Alert transmitters will be used and sharing channels is not appropriate the EZSnsRF could be the better choice. Hope you have as much success with your Dakota Alert equipment as I have.

I use Dakota Alert WPT-3000 sensors at the mailbox and the driveway. The sensors use to come with different buried cable lengths as they cannot be spliced. The mailbox cable is 50’ longer (from memory) as it is located further away. I positioned both sensor transmitters a little closer to the house to avoid having to send signals through a heavily wooded section of property. Both transmitters are a good 200’ from the house. It looks like some of the security distributors are selling Dakota Alert packages. There is a WPA-3000 package which includes one wireless magnetic probe and the wireless receiver. Don't remember packages being available back when I got my equipment. It may be less expensive to get a package rather than buy the individual pieces as I did. I suggest asking Simplehomenet the question about the EZSnsRF supporting other than Dakota Alert. I always thought it was limited to Dakota Alert equipment specifically but I could be wrong.

Brian Thanks for that trace. It confirms what the OP is seeing. The fact that the motion sensor accepted link records in the conventional manor suggests another possibility. The MS options are being set using a 2F ALDB command to alter memory where the options are stored. That is outside the bounds of the link database and could be rejected for being out of range by this new MS. Are the link records actually functional? That is, does the MS Sensor node reflect motion On/Off messages? I’m wondering if they were rejected with a Nack making them not functional.

There is no option to manually specify the location of the link database. I suspect the errors that type of option could generate would override the limited usefulness. There are at least four different starting points I am aware of today. That type of option would be chasing a moving target. There will be a small delay driving the relay from a Program. I turn on the bathroom lights with a Program triggered from a motion sensor. The delay is very small.

I don't know the internals of an InLineLinc but that would be my concern. Powering the InLineLinc from the battery side and the sense line from the grid. I'd be inclined to keep the sides isolated with the same 120V relay approach. The relay coil is powered from grid with the relay contacts switching the sense line from 120V to Gnd on the battery side. It may not be an issue with a solar system particularly if the solar system is sending excess capacity back to the power grid.

Power a 120V AC relay from the grid. When grid power drops the relay will close the NC/Com contacts which can turn an I/O Linc Sensor On which triggers an ISY Program.

Click on the line My Lighting which displays a summary of all the defined devices. Click the Address column heading to sort by Insteon address. Is the Insteon address in the list?

What happens when adding the device? If the Insteon address already exists nothing happens when the device is added again. Note that new devices appear at end of the My Lighting tree (not in collating sequence) until the Admin Console is exited and started again. To be in a Scene it must have appeared in the My Lighting tree at one point. Anything unusual happen between when it was in the My Lighting tree and when it was not.

fuentesa I've had a discussion with Simplehomenet regarding the EZIO4O test results. Likely related to the EZIO4O PLM that is currently being used. The PLM is new (did not mean to imply the EZIO4O was a used device) but it looks like the PLM does not recognize the large memory configuration nor does it handle the extended ALDB command. As a work around you can use an ISY Program that triggers on the device that initiates the Open Gate Scene and have the ISY Program send a Direct command to the desired EZIO4O Relay.

I doubt the Mighty Mule works with the Dakota Alert equipment or the EZSnsRF. The advertised range is less than Dakota Alert and the Dakota Alert uses a 10 bit switch code. The EZSnsRF is designed specifically for Dakota Alert equipment. If the Might Mule receiver has a c-form relay it could be connected to an I/O Linc Sensor to generate an Insteon command. I use a buried magnetic sensor that detects the mail carrier vehicle. I tried various devices (not Dakota Alert) that mounted on the mailbox itself but none had the needed range. The magnetic sensor has a sensitivity adjustment which I lowered so it takes a vehicle pulling up to the mailbox to trip the alarm. Was not sure how it would work in the beginning but since the mailbox attached devices were not reliable I did not have much to lose. After dropping the sensitivity to prevent cars driving by from tripping the sensor it has worked very well for several years. I use a similar magnetic sensor for the driveway alarm. Tried various motion based devices but they all false tripped from deer that roam the area.

Brian Thanks for that information. There is a post under one of the FanLinc topics that one of the latest FanLincs is displaying FF FF --- FF FF for the current link record in the FanLinc. This is classic response from the MorningLinc if PLM access authorization is lost. I suspect the latest FanLinc is also an I2CS. Have ordered another FanLinc (my two FanLincs are older) to confirm as well as another Motion Sensor to confirm the cause of the Nack.

Skripo Thanks for posting a working example. Boser The posted example issues a Set Scene Off followed by Direct commands to each Responder to turn Off. This should not be necessary and will be cumbersome if several Responders are in the Scene. I suggest trying it the way Insteon protocol is expecting it to be done with a Fade Stop. If Control 'Downstairs / Stair.Light' is switched On Or Control 'Downstairs / Stair.KP.Down Garden Lights / Stair.KP.A.Staircase Light' is switched On Then Set Scene 'Downstairs / Scene:Staircase Light' Fast On Wait 2 minutes Set Scene 'Downstairs / Scene:Staircase Light' Fade Down Wait 4 seconds Set Scene 'Downstairs / Scene:Staircase Light' Fade Stop Else - No Actions - (To add one, press 'Action')

A Fade Down (or Fade Up) is half of the expected sequence which is the functional equivalent to pressing and holding the Off button/paddle. When done from a device the sequence always ends with a Fade Stop when the button/paddle is released. This is missing in the posted example. Don't know if a Fade Stop will resolve the problem but it is necessary to complete the Fade process in each device. Add a Wait of some seconds to allow the Fade Down to run its course and then issue a Fade Stop.

craigf There are a couple of possibilities. The v2.1 Motion Sensors may require a different method for updating the configuration data or they may be an I2CS device which UDI is currently adding support for. I ordered a new Motion Sensor so I can test the various possibilities. Michel Any thoughts about the new v2.1 hardware Motion Sensors?

Thanks for the additional information. The Program is triggered once at 8 AM, once 10 hours later at 6 PM, and between 8 AM and 6 PM once for each change in motion sensor status (using If Status) or once for each Insteon command received that matches the command code using If Control. Always event driven either from a time event or a device event in this example. There are other events such as a change in value of a State variable for example that can trigger Programs. When the Program is triggered either the Then clause or the Else clause will run depending on how the If evaluates at the time the Program is triggered. When the If is True the Then clause runs, when the If is False the Else clause runs.

I've used Dakota Alert for years, monitoring mail delivery, driveway access, high water level at the dock, and have been very satisfied. I have an EZSnsRF but have not done any comparisons regarding relative range, etc. The native Dakota Alert transmitters to the Dakota Alert receiver have operated flawlessly for several years. A new battery in the transmitters about once a year is all that is necessary. I also use the small pager when I am expecting a delivery. Lets me move around the property and still know when something comes down the drive.

Sorry I did not understand initially. The LED Brightness does not come back on a Query. I got to 3.1.17 through the evolution of Beta releases rather than from 2.8.16. Can't say I have every paid attention to the LED Brightness numbers across an ISY update. I just tested a reboot and the values remain across a restart. Does sound like the values were not preserved across firmware update. I’ll have to watch what happens on the next firmware update.

Not sure of the function you are referring to. The ISY is event driven. It does not check status of anything every few seconds.

The EZSnsRF receives Dakota Alert RF directly sending Insteon On/Off messages in response. The EZIO6I can be used if the Dakota Alert receiver is used to receive the RF signal. I like the Dakota Alert receiver because it has the chimes built in. I started using the Dakota Alert equipment to achieve the RF range I needed. Later when I decided to integrate the Dakota Alert signals into the Insteon did I add the EZIO6I driven by the c-form relays built into the Dakota Alert receiver.