EZeye & EZIO6I

[Anonymous]

#43453

Since I am using Broadcast Status Change I can get the cycling, so every time there is a change to the binary input it gets logged so perhaps the cycling accounts for my long log entries. Does this cycling happen when using linking?

The example in the Product Guide is to use the digital input to close drapes below a certain light level, but couldn’t the cycling cause close/open/close/open cycling until the light finally fell below a certain level?

[Anonymous]

#43454

Cycling would not account for your trace. It is showing the same Input state pattern on consecutive entries. Mine shows Input 1 On, then Off, then On, then Off, etc. The drapery example depends on whether using the digital or analog output. Also not sure what I am seeing is not unique to this particular EZEye. I will test another EZEye and see. I don’t remember seeing the cycling when I used this device before.

EDIT: I have another EZEye under test. Sun was already up by the time I installed it so I will have to wait for sunset to see if the digital output will cycle on this one.

EDIT2: The new EZEye digital output also cycles Off/On/Off/On/Off…. as the light level declines through the digital output activation point. I will set up Input 1 with an active link so that Group commands are issued for that Input rather than a Broadcast message to see if that has any affect on the cycling. Won’t know the effect of that change until tomorrow morning atSunrise. As expected the Analog input sent a single Broadcast message when it turned Off. The light level would have had to generate a large swing in the Analog value to activate the Off to On trip point.

[Anonymous]

#43455

Lee,

My EZeye does indeed cycle. At a set point in the evening I have the digital input turn on the power for my living room motion detector but as per the log below it cycled ON and OFF several times. I have separated the cycles for clarity but all this occurred as the light dropped to the digital set point in the EZEye. If I change to the analog I won’t get the cycle as you advised.

My use in this case is similar to the example used in the product guide to close the drapes – so the drapes would be closing and opening until the light drops well below the set point.

I am not trying to be critical of the EZEye, I’m just trying to get a better grip on it’s functions so as to use it properly.

regards,

bob

4-Aug-10 9:22:36 PM
Received INSTEON “EZIO6I” inputs status changed: 0, 0, 0, 0, 1, 0
Trigger Action dayLight_OFF
Trigger Action ON_livingMotPwr
Trigger Action _EZeyeBinary

Received INSTEON “EZIO6I” inputs status changed: 1, 0, 0, 0, 1, 0
Trigger Action dayLight_ON
Trigger Action OFF_livingMotPwr
Trigger Action _EZeyeBinary

Received INSTEON “EZIO6I” inputs status changed: 0, 0, 0, 0, 1, 0
Trigger Action dayLight_OFF
Trigger Action ON_livingMotPwr
Trigger Action _EZeyeBinary

Sent X10 “livingMotPwr” on
Trigger Action _4r4_livingMotPwrON
Trigger Action livMotPwrON
Sent X10 “livingMotPwr” off
Trigger Action _4r4_livingMotPwrOFF
Trigger Action livMotPwrOFF
Sent X10 “livingMotPwr” on
Trigger Action _4r4_livingMotPwrON
Trigger Action livMotPwrON
Time/Date Action OFF_livingMotPwr (delayed action)

Received INSTEON “EZIO6I” inputs status changed: 1, 0, 0, 0, 1, 0
Trigger Action dayLight_ON
Trigger Action OFF_livingMotPwr
Trigger Action _EZeyeBinary

Time/Date Action _4r4_livingMotPwrON (delayed action)
Sent X10 “livingMotPwr” off
Trigger Action _4r4_livingMotPwrOFF
Trigger Action livMotPwrOFF
Time/Date Action OFF_livingMotPwr (delayed action)

Received INSTEON “EZIO6I” inputs status changed: 0, 0, 0, 0, 1, 0
Trigger Action dayLight_OFF
Trigger Action ON_livingMotPwr
Trigger Action _EZeyeBinary

Sent X10 “livingMotPwr” on
Trigger Action _4r4_livingMotPwrON
Trigger Action livMotPwrON
Time/Date Action _4r4_livingMotPwrON (delayed action)

Received INSTEON “EZIO6I” inputs status changed: 1, 0, 0, 0, 1, 0
Trigger Action dayLight_ON
Trigger Action OFF_livingMotPwr
Trigger Action _EZeyeBinary

Sent X10 “livingMotPwr” off
Trigger Action _4r4_livingMotPwrOFF
Trigger Action livMotPwrOFF
Time/Date Action OFF_livingMotPwr (delayed action)

Received INSTEON “EZIO6I” inputs status changed: 0, 0, 0, 0, 1, 0
Trigger Action dayLight_OFF
Trigger Action ON_livingMotPwr
Trigger Action _EZeyeBinary

Sent X10 “livingMotPwr” on
Trigger Action _4r4_livingMotPwrON
Trigger Action livMotPwrON
PowerLinc Unexpected command 02 60 (flushing)
Time/Date Action _4r4_livingMotPwrON (delayed action)

[Anonymous]

#43456

Your findings are consistent with the two EZEyes I have tested. I added a link for Input 1 so I can see if Input 1 cycles at sunrise when Group commands are used rather than the Broadcast command.

[Anonymous]

#43457

Bob, what product guide are you referring to about the drapes. I looked at the EZIO6I and EZEye Quick Start Guides and did not see a reference to using drapes. Perhaps there is some additonal information that will help understand how they planned to use the EZIO6I and EZEye to control drapes. The drape controller may have the logic to move the drapes in one direction or the other without concern for the EZEye cycling. Just a thought.

Lee

[Anonymous]

#43458

Lee – The product guide that came with the EZEye. It says;

The digital output is used to determine if the illumination is above or below a certain threshold which is adjusted with the potentiometer on the back of the EZeye. The digital level will be on when the signal is above the set threshold. This could be integrated in an automation sequence where you may want your drapes to close when the ambient light in the room rises above a certain level.

Anyway the cycling combined with a script I had caused the long log entries I previously asked you about. For now I’m going to use the Analog input to trigger my lights and that should fix the cycling. I’ll be interested in hearing what the designers had in mind for the digital input though.

I think I’m finally in business using the EZeye & EZIO6I. I’m sure I will eventually get some glitches due to using Broadcast Status Change but I do plan to get the ISY device and see how that works out for me.

best regards,

bob

[Anonymous]

#43459

Bob,

Thanks. I was looking for something that described hooking the EZIO6I up directly to a drapery controller. Glad to hear things are working using Broadcasts.

Switching to Group processing made no difference. The Input 1 simply sends Group On/ Group Off/Group On/ …… messages rather than Broadcast messages. The On/Off/On/Off…. cycling happens either way.

I think your choice of using the Analog output is the best approach. With the separate Off to On and On to Off trip points you can achieve drapery control even with variations in ambient light level. Things such as clouds moving by or even the difference in the ambient light with the drapes open versus drapes closed can be handled with the appropriate spread in the trip point values. That varying light level situation would have to be dealt with in the automation software with the digital output. If the EZEye digital output was used having two EZEyes would be the simplest approach. One set with a high ambient light level to initiate drapery close operation and the other set with a low ambient light level to initiate drapery open operation. The spread in ambient light level settings between the two EZEyes would provide the same capability as the two trip point values for the Analog output. The Analog approach is better. Fewer components needed and no unnecessary Insteon traffic as the EZEye digital output settles down as the ambient light increases/decreases past the initial trip point.

Lee

EDIT; just thought of another option. Each EZIOxx Input has a timer option that delays sending the On to Off message. That could be used to add a delay to avoid the cycling of the EZEye digital output.

[Anonymous]

#43460

Hello,

I’ve had good success with the Simplehomenet Utility so I’m going to try it on the problems earlier in this post. I’ve had some success right away. In Indigo when I select the Analog inputs to ON I get the log continually updating the inputs status. Using the Utility I turned off the broadcast status change and the updating stopped. Nice 🙂

I have the EZEYE connected as per the instructions to the #1 Analog Input.
1) My first problem is I am getting a value for Analog 3 which is unused. Is there a way to turn it off?
2) The readings I get differ slightly between the Utility & Indigo. I just would like your thoughts then I’ll post to then Indigo Form.

thanks,

bob

[Anonymous]

#43461

bob

Where are you seeing an AN3 value?

Each time an Analog value is retrieved it is recalculated so there can be slight differences between values.

Lee

[Anonymous]

#43462

Lee,

Opps that should be AN2. I see a value displayed in the Utility for AN2 and also in Indigo. Nothing is connected to that input.

bob

[Anonymous]

#43463

bob

The AN1 and AN2 analog values are in separate memory locations in the EZIO6I. As a Utility it has the ability to retrieve either AN1 or AN2 analog values. The On/Off state of each Input is represented by a single Bit for each Input. The On/Off Input state Bits reside in one byte. The state of all Inputs is retrieved by reading that one byte. There is no means of configuring the Utility or the EZIOxx to return only selected Input states.

Whether an application reports a particular Input is at the applications discretion.

Lee

[Anonymous]

#43464

Lee,

I don’t understand. The EZeye is connected to AN1 and reports an analog value when queried, from 0 when totally dark to 1023 when very bright. Nothing is connected to AN2 but it doesn’t show 0. It shows a value anywhere from 1 to 1023, it seems to be random. This is using the Utility to read AN2.

As nothing is connected to is why is it returning a value?

bob

[Anonymous]

#43465

bob

The process of converting the Input from an analog value to a digital value occurs for both analog inputs whenever the Configuration Register enables the inputs for analog processing. If nothing is connected to AN2 it is electrically floating, picking up stray electrical potential from the surroundings. Connecting it to GND will stop the random values.

Lee

[Author]

Posts