Strange EZIO8SA PLM behavior 2007-07-02T15:20:35+00:00

HOME Forums Input/Output EZIOxx Strange EZIO8SA PLM behavior

Viewing 15 posts - 1 through 15 (of 27 total)
  • Author
    Posts
  • Anonymous
    Post count: 20
    #39731 |

    I received my EZIO8SA and PLM combo from simplehomenet the other day. I have been trying to get it working in Homeseer ever since. I have been able to get the plugin script to load the 3 input & 8 output devices. I have also been toying with the free utility from simplehomenet to peek & poke around in the EZIO. I have a momentary switch hooked up to Input 1. Here is my strange behavior:

    If I link the EZIO to another device (a lamp module) then I get “extra” activity on the PLM. When I say extra activity here is what I mean: I can see the Insteon command getting to the SDM by watching the log and the lamp module turns on. If I let go of the switch within about 6 seconds, which should send the off command, I get no messages in the SDM log. If I wait for more than about the 6 seconds, I get the messages in the log and the lamp turns off. I also noticed that the LED on the side of the PLM does the following during the 6 second period of time: Bright, Bright, Off, Bright otherwise it is the regular dim level.

    Another piece of the puzzle is that if I do not have the particular input linked to a device, then I get no Insteon commands in the SDM, but by coupling input 1 to output 1 I can hear the output relay switch on and off instantaneously.

    I was planning on using this thing for contact closures, but given this behavior, I am sure that the switch state and Homeseer will get out of sync.

    Any ideas on how to get the PLM to send the Insteon messages and still respond to the input changes without delay?

    Anonymous
    Post count: 15

    This is what I get when I try to link the EZIO8SA in Homeseer:
    Unknown Device Type 0704

    Is this the normal behaviour??

    Dan

    Anonymous
    Post count: 15

    Insteon Device ID: 08.21.10

    Device Name:

    Device Location:

    Device Type: Unknown Device Type 0704
    Firmware Version: FF [Comm Reliability: 92% (6 failed out of 71 cmds)]
    Resume dim mode: False
    Default local on level: 7%

    Polling Interval (Minutes, 0=None):


    Link table present in remote device:



    Link# 1 – Unknown controls RC RC Hall keypad (0A.B1.33)
    Link# 2 – Unknown Group/Button Name #41 is controlled by HomeSeer (Using Insteon Link# 254) HomeSeer ‘All Devices Group’
    Link# 3 – Unknown has local control reporting to HomeSeer
    Link# 4 – Unknown is controlled by HomeSeer (Using Insteon Link# 254) HomeSeer ‘All Devices Group’

    Anonymous
    Post count: 192

    Device type 0704. Is the ID of the EZIO8SA. The PLM is an ID 0305, but it has the ability to have a ID set in it to match the device connected to it.
    My guess is part of the startup writes the 0704 to the configuration table; that is being read for the modules ID.
    So you are most likely seeing the correct ID. It looks like Homeseer doesn’t know that ID number.

    Anonymous
    Post count: 256

    Brian is correct. The EZIO has a unique ID and it writes it to the PLM upon power up. Thus, the PLM and EZIO8SA become one unit. The support software needs to recognize athe EZIO8Sa, not a regular PLM.

    Al

    Anonymous
    Post count: 12

    Hi – I notice the same 6 second issue as jatracy started this thread with:
    Note: this is with the EZIO8SA V17 and SimpleHomeNet Utility 1.4

    What I need:

      sense a momentary or sustained switch closure
      send a Group On message right away
      send a Group Off message after 1 min

    What I get:

      if I hold the swich closed for more than Jatracy’s 6 sec and hold the switch open for more than 6 sec
      it sends a Group On on close and Group Off on open

      if I do either in less than 6 sec
      it doesn’t send the command for the action that occured inside 6 sec

      if I set the Input timer mins with the Utility and “save all changes permanently”
      it doesn’t seem to have any effect (goes back to 0) see my other post

      if I set the Output timer to one min (and Enable Output Timers)
      I can hear the output relay switch at close and switch back one min later 🙂
      but only if the PLM doesn’t have a link on that Group

      if I link the PLM on that group to another INSTEON device (to get the Group Commands)
      I can hear the relay switch at close and switch again about 1 sec later 🙁
      it only sends out the Group On and never the Group Off

      I even started hooking up outputs of inputs without PLM Group Links to inputs with PLM links but nothing I’ve tried gives me what I need.

    Can anyone lend a hand?

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 12

    All-Link Cleanup ACK… Isn’t that handled automatically by the PLM? Do we have any way to affect the SC ACK other than changing 1 or 2 bytes in the ACK (or telling it to send a NACK)?

    I agree with you that the 6 seconds isn’t the issue, it’s the missed inputs during that 6 seconds.

    By the way have you had the EZIO8SA stop generating any messages to it’s PLM until you unplug it and plug it back in?

    Anonymous
    Post count: 20

    I was told that this bahavior is due to the group cleanup messages that need to occur. To me this is still insufficient. I can not tolerate the possibility of missing a trigger to an event if these devices are to be used in a critical application (like a security system). I have basically started looking elsewhere to fulfill the requirements of the systems I would be building.

    Let me be perfectly clear. The 6 second delay is NOT the issue. The issue I have is that the events within that 6 second delay are not reported! They should be at least queued and sent when possible.

    The reason I started using Insteon was so I would not be missing events. These devices fail to impress me in that regard. They are good for slowly changing inputs though (like a garage door). I have been monitoring my garage door with my EZIO8SA for about 6 months now but I did have to implement a polling routine to make sure that even when I don’t get the message from the EZIO, the software stays in sync.

    Anonymous
    Post count: 20

    Sorry for the multiple responses, I kept getting errors and I didn’t think that the messages got sent!

    Anonymous
    Post count: 20

    @bwelsh wrote:

    By the way have you had the EZIO8SA stop generating any messages to it’s PLM until you unplug it and plug it back in?

    I did get some very strange behavior, but the modules were in the garage and the temp got below freezing so I moved them inside about two weeks ago by extending the wiring to the sensor and opener switch and I have not seen any issues since.

Viewing 15 posts - 1 through 15 (of 27 total)
  • You must be logged in to reply to this topic.