HOME › Forums › Input/Output › EZIOxx › trying to get EZIO2X4 to Control Somfy Drapery controller

Viewing 15 posts - 1 through 15 (of 24 total)
1 2 Next
  • Author
    Posts
  • Anonymous
    Inactive
    October 20, 2008 at 1:31 am
    Post count: 26
    #40069

    The somfy device needs a momentary contact to start the drapery controller to open or close the drapes (or stop the drapes while they are in motion).

    The ezio2x4 makes a sustained contact, so the only way that I’ve been able to use it is by always pressing “off” on the controlling switch before I press “on” (or pressing off after each “on”).

    Any better ways to make it work?

    Anonymous
    Inactive
    October 20, 2008 at 2:22 am
    Post count: 5
    #42286

    @someguy wrote:

    The somfy device needs a momentary contact to start the drapery controller to open or close the drapes (or stop the drapes while they are in motion).

    The ezio2x4 makes a sustained contact, so the only way that I’ve been able to use it is by always pressing “off” on the controlling switch before I press “on” (or pressing off after each “on”).

    Any better ways to make it work?

    What is the maximum length of the momentary contact that the somfy will allow?

    How about using the timers on the relays so they can turn off at a preset time after an On command is received .

    It can be done. Read the documentation on the unit.

    Anonymous
    Inactive
    October 20, 2008 at 4:40 am
    Post count: 1001
    #42287

    GaryFunk response is right on. Same situation where the EZIO2X4 is used to open/close garage doors as they require a momentary circuit. Each EZIO2X4 Output has an Output timer value that can be set using the Simplehomenet Utility Suite (free download). Use the EZIOxx tab, Read the Output Timer values, using the up/down arrows, set the particular Timer to the value needed (2-3 seconds is generally all that is needed), Write the Output Timer values. In the Configuration Register area click on Read, check Set Timers in Seconds and Enable Output Timers, click on Write. Then click yellow Save Changes to make Configuration Register change permanent. Now the respective Output will turn OFF n seconds after being turned on.

    Anonymous
    Inactive
    October 21, 2008 at 2:26 am
    Post count: 26
    #42288

    @grif091 wrote:

    In the Configuration Register area click on Read, check Set Timers in Seconds and Enable Output Timers, click on Write. Then click yellow Save Changes to make Configuration Register change permanent. Now the respective Output will turn OFF n seconds after being turned on.

    wow! it worked. I clicked everything that you said, then I clicked “read” again and it didn’t show my changes… so I thought it didn’t work, but when I pressed the button to open the drapes and then pressed it again, it worked each time (unlike before when I had to press “off” after each “on”).

    thanks alot guys. maybe the simplehomenet utility suite does work?

    Anonymous
    Inactive
    October 21, 2008 at 2:45 am
    Post count: 1001
    #42289

    I’ve had good success with the SHN Utility in this area. The underlying activities that occur when a button is clicked are not instantaneous. A command is sent on the powerline to the device; it reacts to it and then sends a command back across the powerline which is then interpreted and the results displayed.

    You may have been a little too quick on the buttons to get a correct response. Would expect the Configuration Register changes to be displayed on a Read.

    Anyway, good to hear you are working.

    Anonymous
    Inactive
    October 26, 2008 at 1:40 pm
    Post count: 26
    #42290

    Actually, this didn’t work. I am connecting the Utility Suite using my Smarthome PLC. I press “read”, then click the two boxes mentioned above, then “write” then “Save Changes”.

    One of the things that I notice is that the green bar in the bottom right (where it usually says “ready”) never moves. It always says ready. When I click “save changes” a windows pops up that says “This will write all changes to the EzioXX….” and I say “yes”. then when I press “read” the changes aren’t made.

    One of the frustrating thing about this utility suite is that it can’t remember the Insteon address from the last time that I entered it… but now I’m just complaining. sorry.

    Anonymous
    Inactive
    October 26, 2008 at 1:46 pm
    Post count: 26
    #42291

    here is some more info:

    when I go to the “output timers (local to ezio)” section, I read the output timer #1 as 255. when I change it to a number like 5, and click write, then click read, it goes back to 255. I tried clicking write and then “save changes” and that doesn’t work, because when I click “read” it still says 255.

    How could it be that my utility suite can read all of these things, but not write to them?

    Anonymous
    Inactive
    October 26, 2008 at 2:17 pm
    Post count: 1001
    #42292

    After Reading the Output timer values, go to Insteon Traffic tab and Clear both left and right windows. The EZIOxx Insteon ID will not be lost during the tab change. Go back to the EZIOxx tab, change the Timer value, click Write. Then go back to the Insteon Traffic tab and note the commands in both left and right window and post those back. I should be able to tell what is happening from that. Also, after entering the Insteon ID on the EZIOxx tab, below that input field is displayed Connected ???. The ??? value is the firmware level of the EZIO2X4. Post that back as well. Thanks

    EDIT: this is what the command sequence is expected to look like. Both Output Timers were set to 7 originally. I set Timer 1 to 4 and Timer 2 to 3 and then clicked on Write.

    To ID:0c.ae.5f flags:0F cmd1:28 cmd2:0 from ID:0C.AE.5F flags:23 cmd1:28 cmd2:0
    To ID:0c.ae.5f flags:0F cmd1:2B cmd2:0 from ID:0C.AE.5F flags:2B cmd1:2B cmd2:7
    To ID:0c.ae.5f flags:0F cmd1:29 cmd2:4 from ID:0C.AE.5F flags:2B cmd1:29 cmd2:4
    To ID:0c.ae.5f flags:0F cmd1:2B cmd2:1 from ID:0C.AE.5F flags:2B cmd1:2B cmd2:7
    To ID:0c.ae.5f flags:0F cmd1:29 cmd2:3 from ID:0C.AE.5F flags:2B cmd1:29 cmd2:3
    To ID:0c.ae.5f flags:0F cmd1:4F cmd2:1 from ID:0C.AE.5F flags:2B cmd1:4F cmd2:1

    Don’t worry if they don’t make sense. Just post back your results and I
    will interpret.

    EDIT2: I also posted this under the Simplehomenet Utility.

    In looking at the SHN Utility source to see how hard it would be to save the last Insteon ID of the EZIOxx device I discovered the mechanism is already there. Double click on empty Insteon ID field and the Device Type and Insteon ID fields are primed with the last used values.

    Anonymous
    Inactive
    October 26, 2008 at 8:26 pm
    Post count: 26
    #42293

    when I do this, the left box says:

    To ID:08.9B.D7 flags:0F cmd1:28 cmd2:0
    To ID:08.9B.D7 flags:0F cmd1:2B cmd2:0
    To ID:08.9B.D7 flags:0F cmd1:29 cmd2:1
    To ID:08.9B.D7 flags:0F cmd1:2B cmd2:1
    To ID:08.9B.D7 flags:0F cmd1:29 cmd2:7
    To ID:08.9B.D7 flags: cmd1:29 cmd2:7
    To ID:08.9B.D7 flags:0F cmd1:4F cmd2:1

    and the right box says:

    from ID:08.9B.D7 flags:2F cmd1:28 cmd2:0
    from ID:08.9B.D7 flags:2F cmd1:2B cmd2:FF
    from ID:08.9B.D7 flags:2B cmd1:29 cmd2:1
    from ID:08.9B.D7 flags:2F cmd1:2B cmd2:1E
    from ID:08.9B.D7 flags:2F cmd1:29 cmd2:7
    from ID:D3.24.6D flags:62 cmd1:DA cmd2:7E
    from ID:08.9B.D7 flags:2F cmd1:4F cmd2:1
    from ID:9B.BB.64 flags:20 cmd1:C9 cmd2:A4

    I actually tried this about ten different times and the blue bar is moving and it seems to be doing something. sometimes when I click “read” it will read it to what I set it to, but then a minute later, I click “read” and it reads output number one at 255 again.

    edit:
    also: thanks for the help with the Insteon I.D.

    edit 2:
    the version says v14

    Anonymous
    Inactive
    October 26, 2008 at 9:51 pm
    Post count: 1001
    #42294

    There is clearly a problem. It looks like the Poke to set Timer 2 (5th command on the To ID: side) was issued a second time but that may just be the result of an inbound message from the PLC that should not be there. The “from ID:D3.24.6D flags:62 cmd1:DA cmd2:7E” should not be there. There should only be “from” messages containing the ID of the EZIO2X4. Once that happens the “1 out 1 in” command sequence the Utility is written to expect is out of sync and processing stops waiting for something that is not going to happen. I see that from my PLC from time to time. Generally when I am displaying links which prevents the display links from completing because it disrupts the 1 out 1 in command sequence the Utility requires. I’ve thought about getting a new PLC but have not gotten around to it. Generally once you see an entry that occurs during an operation the Utility is performing things will not complete successfully.

    From the trace it shows Timer 1 had a value of FF (255) and was being changed to 1, Timer 2 had a value of 1E (30) and was being changed to 7.

    Do you always see a “from ID:” message that does not have the 08.9B.D7 address of the EZIO2X4 and if so is it always the 6th message coming back when you do a Write. The FF and 1E values look very much like part of a link record that has overlaid low memory. After your EZIO2X4 was functionally working a few posts back did you do another link with the Set button or through the Utility?

    What is the firmware level of the EZIO2X4?

    There is nothing I know to do to stop the message from the PLC that should not be there. When it happens to me while displaying links I just hit Display again until I get a good complete link display where the PLC has not dumped a bad message back to the Utility. If there is other powerline activity while you are working with the Utility, hold up on that while working with the Utility. If you can post back the firmware level of your EZIO2X4 I will research older forum activity to see if I can find something about link information overlaying storage. Just something I think I read somewhere. It might not have been on the SHN forum. I watch several forums so it might well be somewhere else.

    You can try doing another Write if you find messages in the Insteon Traffic tab. That works for me while doing Link displays. Don’t know how well that works for Writes. Link Display works okay when repeated but since I’ve never had this happen while doing a Write I don’t if that works. Looking at the Insteon Traffic tab will show if it worked.

    The bottom line so far is the Write did not complete because of the erroneous message from the PLC. The Timer values may have been overlaid with another link operation. Once you get the Timers set with a successful Write, those values should be okay unless you do another link to the EZIO2X4 (if my memory is correct about that being the cause). Once I get the firmware level I‘ll search all the forums I watch for something applicable.

    Just saw your post update with the firmware level. I’ll do some searching and post back what I find.

    Anonymous
    Inactive
    October 26, 2008 at 11:22 pm
    Post count: 1001
    #42295

    I have not found what I am looking for yet, there is a lot of old stuff out there and I am still looking. However, I just realized what you posted for firmware level. You are seeing Connected v14, not a sticker on the device that says 14. Firmware level v14 is pretty old. I have three 2X4s that are at least 6 months old; probably more and they are v25. If your EZIO2X4 was a recent purchase, you should contact that supplier and get a newer unit. A new unit won’t have any effect on the erroneous messages from the PLC but it would probably resolve the loss of Timer values written by a successful Write.

    Anonymous
    Inactive
    October 27, 2008 at 1:04 am
    Post count: 26
    #42296

    @grif091 wrote:

    I have not found what I am looking for yet, there is a lot of old stuff out there and I am still looking. However, I just realized what you posted for firmware level. You are seeing Connected v14, not a sticker on the device that says 14. Firmware level v14 is pretty old. I have three 2X4s that are at least 6 months old; probably more and they are v25. If your EZIO2X4 was a recent purchase, you should contact that supplier and get a newer unit. A new unit won’t have any effect on the erroneous messages from the PLC but it would probably resolve the loss of Timer values written by a successful Write.

    I bought my ezio2x4 a little over a year ago from smarthome. Is there any way to update the software without mailing the thing to someone?

    Anonymous
    Inactive
    October 27, 2008 at 1:22 am
    Post count: 1001
    #42297

    Unfortunately no field upgrade.

    Have you done any more Timer Write attempts to see how transient that message from the PLC actually is. This will not be limited to Write. A Read could have the same issue making it difficult to know if the values you are seeing displayed are actually from the EZIO2X4 or left over from the previous Write request. You will have to look at the Insteon Traffic tab so see if there has been traffic that interfered with the current function request.

    Anonymous
    Inactive
    October 27, 2008 at 11:45 am
    Post count: 26
    #42298

    I’ve tried it a number of times and it just won’t over-write. I’m thinking of getting an ISY-99i. Will that work any better than the utility suite? I’m sure it will be more difficult.

    Anonymous
    Inactive
    October 27, 2008 at 1:29 pm
    Post count: 1001
    #42299

    That is somewhat like comparing Apples to Oranges. The Utility is a piece of free software. The ISY is a dedicated HA hardware box and software for which you have to pay for. It has a good reputation for HA from everything I have read on the forums. If you are thinking about an ISY simply to configure your EZIO2X4 that is a waste of money. You would want to be sure it has the ability to configure an EZIO2X4 before going in that direction. There is a difference between knowing it has 4 Inputs and 2 Outputs, being able to establish links and so on, to knowing and configuring the specific features of the EZIO2X4. It may well have that capability, just be sure before that move. I am concerned that your powerline environment is such that you can’t get a dozen commands to run back to back without an error. To Write the Timer information, 6 commands out and 6 commands back is all it takes. The free Utility may lack the sophistication to handle those errors but they will remain even using an ISY.

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 24 total)
1 2 Next
  • You must be logged in to reply to this topic.