Having trouble installing EZFlora

[satwar]

I have a Isy99i (recently ordered a isy994i) running firmware 3.3.10, and EzFlora v28.

 

I'm really struggling with this device.  I used "add an Insteon device" and I got 8 different Irrigation zones (which was good).  The first sign of trouble is when I select a zone and send the "ON" command it will not turn on.  It takes multiple tries of "ON" then "OFF" commands on a zone before it finally changes state 

 

It goes without saying that my Irrigation Program (which turns on each zone on in sequence) does not work either.

[LeeG]

Is this on the 99i or the 994i?   If the 994i what ISY firmware and UI is being used?  (Help | About)

 

How far away is the EZFlora from the PLM? 

[satwar]

I'm currently running isy99i @ firmware 3.3.10

 

I have a small house and both modules are in the basement, perhaps within 20 ft.

[LeeG]

I am surprised that the v.28 EZFlora works at all on 3.3.10.   That version of EZFlora is I2CS (I have one) which I did not think the 3.3.10 Admin Console would accept.

 

What does Help | About show for Firmware and UI levels.  I'm concerned a later level Admin Console is being used on 3.3.10 ISY.

 

The EZFlora could be on the opposite 120v leg as the PLM.   Can the EZFlora be plugged into the same circuit as the PLM?

 

With the possibility the Admin Console level may be an issue along with what looks like a comm issue it is hard to know which direction to pursue.

 

Run Tools | Diagnostics | Event Viewer at LEVEL 3 and trace a few EZFlora zone On/Off commands.  It may help direct where the corrective action should be taken. 

[paulw]

Not input to your issue, but something I have experienced with EZFlora's.  I have gone through several of them, seems they do not like quick power fluctuations which we often have.  My solution was to use the dual band version and put it on a small UPS. Have not lost one since.

[satwar]

I am surprised that the v.28 EZFlora works at all on 3.3.10.   That version of EZFlora is I2CS (I have one) which I did not think the 3.3.10 Admin Console would accept.

 

What does Help | About show for Firmware and UI levels.  I'm concerned a later level Admin Console is being used on 3.3.10 ISY.

 

The EZFlora could be on the opposite 120v leg as the PLM.   Can the EZFlora be plugged into the same circuit as the PLM?

 

With the possibility the Admin Console level may be an issue along with what looks like a comm issue it is hard to know which direction to pursue.

 

Run Tools | Diagnostics | Event Viewer at LEVEL 3 and trace a few EZFlora zone On/Off commands.  It may help direct where the corrective action should be taken. 

 

Well I ran an electrical extension cord from the same receptacle that the EZFlora is plugged into and ran the extension cord to the PLM.  With both PLM and EZFlora on the same cicuit, the on/off commands still are not working reliably

 

Diagnostics Level 3: First attempt didn't work

 

Wed 09/23/2015 03:28:15 PM : [iNST-TX-I1  ] 02 62 1E 7A 55 0F 40 00

Wed 09/23/2015 03:28:15 PM : [iNST-ACK    ] 02 62 1E.7A.55 0F 40 00 06                 (00)

Wed 09/23/2015 03:28:15 PM : [iNST-SRX    ] 02 50 1E.7A.55 13.20.08 2B 40 00           (00)

Wed 09/23/2015 03:28:15 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Second attempt worked

 

Wed 09/23/2015 03:28:18 PM : [iNST-TX-I1  ] 02 62 1E 7A 55 0F 40 00

Wed 09/23/2015 03:28:18 PM : [iNST-ACK    ] 02 62 1E.7A.55 0F 40 00 06                 (00)

Wed 09/23/2015 03:28:18 PM : [iNST-SRX    ] 02 50 1E.7A.55 13.20.08 2B 40 80           (80)

Wed 09/23/2015 03:28:18 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 09/23/2015 03:28:18 PM : [  1E 7A 55 1]       ST 255

 

My Isy99i has firmware 3.3.10 and UI 4.2.30

[LeeG]

The first On command was received and ACKed but the ACK did not have to expected x'80' response.

 

The second On command was also Acked and did have the expected x'80'

 

I am looking into it.  I'm concerned about the ISY at 3.3.10 and Admin Console at 4.2.30.

 

Thanks for the trace.  Very helpful.

 

 

Diagnostics Level 3: First attempt didn't work

 

Wed 09/23/2015 03:28:15 PM : [iNST-TX-I1  ] 02 62 1E 7A 55 0F 40 00
Wed 09/23/2015 03:28:15 PM : [iNST-ACK    ] 02 62 1E.7A.55 0F 40 00 06                 (00)
Wed 09/23/2015 03:28:15 PM : [iNST-SRX    ] 02 50 1E.7A.55 13.20.08 2B 40 00           (00)
Wed 09/23/2015 03:28:15 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Second attempt worked

 

Wed 09/23/2015 03:28:18 PM : [iNST-TX-I1  ] 02 62 1E 7A 55 0F 40 00
Wed 09/23/2015 03:28:18 PM : [iNST-ACK    ] 02 62 1E.7A.55 0F 40 00 06                 (00)
Wed 09/23/2015 03:28:18 PM : [iNST-SRX    ] 02 50 1E.7A.55 13.20.08 2B 40 80           (80)
Wed 09/23/2015 03:28:18 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 09/23/2015 03:28:18 PM : [  1E 7A 55 1]       ST 255
 

My Isy99i has firmware 3.3.10 and UI 4.2.30

[LeeG]

Do you have the Simplehomenet Utility Suite installed.  

 

The EZFlora command specs indicate the 0x00 response is from the EZFlora being in Inhibit state.  The SHN Utility has the function to read the Config register where the Inhibit indicator resides.

 

The other option is to go back to the 3.3.10 Admin Console and repeat the event trace.

[LeeG]

paulw

 

Thanks for that information.   I have several EZFlora devices.  The latest I found not functional when I went to trace a simple Zone On command to see if there was some difference I had forgotten.   There have been a few very short power outages that looked like they were switching primary power feed.  I'm near the state line so the power company can switch to the adjacent state for backup if work on substation is needed.  That may explain why this one EZFlora has stopped working.   It is the only device i have had fail in recent history.  Appreciate the input. 

[satwar]

Do you have the Simplehomenet Utility Suite installed.  

 

The EZFlora command specs indicate the 0x00 response is from the EZFlora being in Inhibit state.  The SHN Utility has the function to read the Config register where the Inhibit indicator resides.

 

The other option is to go back to the 3.3.10 Admin Console and repeat the event trace.

     

I think you got it right, about the inhibit state.  After pounding away on the keyboard for a few hours, I finally remembered how to connect to the PLM and then to EZFlora.  I turned Inhibit Off and all is fine (i think it's too late now)

 

I'll check it more rigorously tommorow.

 

Thank you so much, this problem was driving me nuts.

[paulbates]

paulw

 

Thanks for that information.   I have several EZFlora devices.  The latest I found not functional when I went to trace a simple Zone On command to see if there was some difference I had forgotten.   There have been a few very short power outages that looked like they were switching primary power feed.  I'm near the state line so the power company can switch to the adjacent state for backup if work on substation is needed.  That may explain why this one EZFlora has stopped working.   It is the only device i have had fail in recent history.  Appreciate the input. 

Lee

The non responsive zone is a test for a fried ezflora that can be programmed. Turn the zone on, query the zone, wait 5 seconds then call a program that checks for it to be off. If it is, notify etc.

 

Paul