LeeG

If you have a scope check the level and form of the converted AC to DC signal. The circuits in the EZIO8SA will have problems if the converted AC signal is not clean, steady DC. Apply the 12 DC line from the EZIO8SA to Input 4 + (- should be connected to EZIO8SA Gnd). . Does that cause the Input to signal On and Off to the ISY? If that works but the Input is not reliable when an EZIO8SA relay is being controlled at the same time the relay messages and the Input state change messages are likely interfering with each other.

That is correct. Query EZIO8SA relay 1, two commands are issued. The first command, 0x4F 0x02, returns the state of all relays as a single byte bit map (0x10). Thu 09/04/2014 03:13:22 AM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 4F 02 Thu 09/04/2014 03:13:22 AM : [iNST-ACK ] 02 62 0D.FC.71 0F 4F 02 06 IOCTL (QUERY) Thu 09/04/2014 03:13:22 AM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 4F 10 IOCTL (10) Thu 09/04/2014 03:13:22 AM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 09/04/2014 03:13:22 AM : [D2D EVENT ] Event [D FC 71 1] [sT] [0] uom=0 prec=-1 Thu 09/04/2014 03:13:22 AM : [ D FC 71 1] ST 0 Thu 09/04/2014 03:13:22 AM : [D2D-CMP 0059] STS [D FC 71 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true The second command, 0x49 0x00, returns the state of all Inputs as a single byte bit map (0x30) Thu 09/04/2014 03:13:22 AM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 49 00 Thu 09/04/2014 03:13:22 AM : [iNST-ACK ] 02 62 0D.FC.71 0F 49 00 06 RINPUT (00) Thu 09/04/2014 03:13:22 AM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 49 30 RINPUT (30) Thu 09/04/2014 03:13:22 AM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

A Query of the EZIO8SA takes two commands. One command returns the state of all relays and one command returns the state of all Inputs.

I think there is another issue to be worked out. Having a relay change the state of one of the Inputs can be a problem. The EZIO8SA is in the process of generating a response to the relay command at the same time the EZIO8SA is trying to generate a message about the change in Input state. Have not seen that combination in some time but memory of that combination was always an issue. Its like pressing multiple KPL buttons at same time. The KPL will usually lose the change in state of one of the buttons. .

"Output 2 as you said shows on and off. Reality was that 2 did not go off. " That is not a comm issue. The response from the EZIO8SA indicates the EZIO8SA turned the relay Off. If it did not actually turn Off (which I have to question) it indicates a failure in the EZIO8SA itself.

Input 4 turned Off ... Wed 09/03/2014 01:42:22 PM : [INST-SRX ] 02 50 21.2D.92 00.00.0C C7 13 00 LTOFFRR(00) The Inputs 1-7 are numbered 9,A,B,C,D,E,F. The message from C is for Input 4 with the 0x13 being the Off command. Relay 2 turned On Wed 09/03/2014 01:42:06 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 01 -- Relay 2 On Wed 09/03/2014 01:42:07 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 0B IOON (0B) -- relay 1,2,4 On response Wed 09/03/2014 01:42:07 PM : [ 21 2D 92 2] ST 255 and Relay 2 turned Off Wed 09/03/2014 01:42:20 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 01 -- Relay 2 Off Wed 09/03/2014 01:42:21 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 46 09 IOOFF (09) -- relay 1,4 On response Wed 09/03/2014 01:42:21 PM : [ 21 2D 92 2] ST 0 All Relay commands traced from PLM reached the EZIO8SA and the EZIO8SA responded with the expected cmd2 value (bit map of relays, from right to left relay 1-8, bit On indicates relay On)

barkster "From what I read you can't have two plm's on the network." No problem with multiple PLMs in use. I run two ISYs, each with its own PLM and at present also have an EZIO8SA with its own PLM. Of course the ISYs are controlling their own unique set of Insteon devices and the EZIO8SA is defined to only one ISY..

Every Relay On or Off sent to EZIO8SA was received and the correct response was sent from the EZIO8SA back to the ISY/PLM. If relays are not functioning as expected check the wiring connections to the relays. Wed 09/03/2014 01:41:51 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 03 -- Relay 4 Off Wed 09/03/2014 01:41:52 PM : [ 21 2D 92 4] ST 0 Wed 09/03/2014 01:41:58 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 03 -- Relay 4 On Wed 09/03/2014 01:41:58 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 08 IOON (08) -- relay 4 On response Wed 09/03/2014 01:41:58 PM : [ 21 2D 92 4] ST 255 Wed 09/03/2014 01:42:03 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 00 -- Relay 1 On Wed 09/03/2014 01:42:05 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 09 IOON (09) -- relay 1 and 4 On response Wed 09/03/2014 01:42:05 PM : [ 21 2D 92 1] ST 255 Wed 09/03/2014 01:42:06 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 01 -- Relay 2 On Wed 09/03/2014 01:42:07 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 0B IOON (0B) -- relay 1,2,4 On response Wed 09/03/2014 01:42:07 PM : [ 21 2D 92 2] ST 255 Wed 09/03/2014 01:42:13 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 02 -- Relay 3 On Wed 09/03/2014 01:42:13 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 0F IOON (0F) -- relay 1,2,3,4 On response Wed 09/03/2014 01:42:14 PM : [ 21 2D 92 3] ST 255 Wed 09/03/2014 01:42:14 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 45 05 -- Relay 6 On Wed 09/03/2014 01:42:14 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 45 2F IOON (2F) -- relay 1,2,3,4,6 On response Wed 09/03/2014 01:42:14 PM : [ 21 2D 92 6] ST 255 Wed 09/03/2014 01:42:17 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 02 -- Relay 3 Off Wed 09/03/2014 01:42:18 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 46 2B IOOFF (2B) -- relay 1,2,4,6 On response Wed 09/03/2014 01:42:18 PM : [ 21 2D 92 3] ST 0 Wed 09/03/2014 01:42:18 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 05 - Relay 6 Off Wed 09/03/2014 01:42:18 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 46 0B IOOFF (0B) -- relay 1,2,4 On response Wed 09/03/2014 01:42:18 PM : [ 21 2D 92 6] ST 0 Wed 09/03/2014 01:42:20 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 01 -- Relay 2 Off Wed 09/03/2014 01:42:21 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 46 09 IOOFF (09) -- relay 1,4 On response Wed 09/03/2014 01:42:21 PM : [ 21 2D 92 2] ST 0 Wed 09/03/2014 01:42:22 PM : [iNST-SRX ] 02 50 21.2D.92 00.00.0C C7 13 00 LTOFFRR(00) -- Input 4 Off Wed 09/03/2014 01:42:22 PM : [ 21 2D 92 C] DOF 0 Wed 09/03/2014 01:42:23 PM : [iNST-TX-I1 ] 02 62 21 2D 92 0F 46 00 -- Relay 1 Off Wed 09/03/2014 01:42:23 PM : [iNST-SRX ] 02 50 21.2D.92 2F.B8.09 27 46 08 IOOFF (08) -- relay 4 On response Wed 09/03/2014 01:42:23 PM : [ 21 2D 92 1] ST 0

Are all the devices in the residence On (required for it to be All On issue) as well as the garage door being open? If all the devices are not On then analysis has to move to something else. You can contact Smarthome and request participation in the beta PLM test. I have my doubts they will do that but that is the only option. The Query Program example to query every 30 minutes If Time is 12:01:00AM Then Repeat 47 times Set 'IO Linc-Sensor' Query Wait 30 minutes Else - No Actions - (To add one, press 'Action') The notification Program example to issue Notify if door open more than 10 minutes. If Status 'IO Linc-Sensor' is On Then Wait 10 minutes Send Notification to 'xxxxx' Else - No Actions - (To add one, press 'Action')

Not possible with the All On symptom. The All On command is believed to come from the PLM (uncommanded) so there is nothing to trigger a Program. SmartLabs just provided one PLM with beta changes that has gone to a customer that is seeing many All On events. A Program can query the I/O Linc Sensor at some interval that will not interfere with the installation and issue a notification (requires a second Program) if the door is found open when not expected.

Some of the information is in the topic, second post. http://forum.universal-devices.com/topic/13919-subscription-to-isy-time-out/?hl=subscription

From an Insteon perspective Scenes have no Status. A Scene is not On or Off. Under ISY Programs, "Condition" Status and Control cannot test a Scene for On/Off. Under Dashboard the On/Off buttons select the command to be applied to the Scene. They do not reflect Scene Status as Insteon has no concept of a Scene Status.

Yes. The mode of the button does not affect the result of the Scene used to turn the button LED On or Off.

Did you switch from WeatherBug to HAM? WB became fee based making a switch to HAM a requirement.

No. Restoring a later ISY Backup will lose the new node. The only option is to Delete the EZFlora and add it back.

The //www. was changed to //isy. some time ago. The 3.3.10 announcement shows //isy. Perhaps a //www. URL existed from before 3.3.10 and was deleted. Too far back for my memory.

The WWW is not correct. See this topic, second post from UDI, with the correct URL for accessing 99i. http://forum.universal-devices.com/topic/13889-isy-99i-connection-issue/?hl=99i From that second post ...... Please try http://isy.universal-devices.com/99i . (note the isy.).

I think the link to the old Admin Console for a 99i is http://isy....... rather than www.......

There is no command driven Factory Reset. As oberkc already indicated a Restore Device usually resolves link database issues but that is dependent on the links option used when adding the device to the ISY. If "remove existing links" was used there are no previous links carried forward. If ".... keep existing links" was used old links are carried forward and Restore Device will restore them. Also note that it might be another device that was linked as a Controller to this device that is causing the On/Off issues (if not caused by comm issues).

Restoring an ISY Backup taken just before that node was deleted if no other changes have been made to the ISY environment. Otherwise the EZFlora has to be Deleted and added back to get the deleted node back.

I cannot answer that question. The device did not respond to the three commands. Would it respond to a 994i with later firmware I have no way of knowing. There were Insteon devices moved to I2CS after 3.3.10. I know for sure that later KPLs are not handled by 3.3.10 but that is the result of SmartLabs changing the device type.

Having the irrigation controller automatically turn Off a Zone insures water is not used longer than needed/expected. Some geographic areas are very sensitive to water usage. An individual Zone can open multiple valves. There is a current limit so each controller may have a different number on concurrent valves open by the current zone. Running without timers could allow a valve to remain open if Insteon comm to the EZIO8SA (or EZFlora) fails. The number of heads I use on each valve is based on water flow. Running two at once would lower the pressure such that the heads would not work. The irrigation system was designed using a RainBird controller. It was replaced with a newer RainBird when lightning damaged the first one. With the EZFlora design based on a normal irrigation it was simple to substitute an EZFlora when Insteon control was added.

That is an I2CS device. It did not answer the request for it to identify itself (tried three times). Sat 08/23/2014 11:52:39 AM : [iNST-TX-I1 ] 02 62 20 8B C4 0F 10 00 Sat 08/23/2014 11:52:39 AM : [iNST-ACK ] 02 62 20.8B.C4 0F 10 00 06 ID-REQ (00) Sat 08/23/2014 11:52:48 AM : [iNST-TX-I1 ] 02 62 20 8B C4 0F 10 00 Sat 08/23/2014 11:52:48 AM : [iNST-ACK ] 02 62 20.8B.C4 0F 10 00 06 ID-REQ (00) Sat 08/23/2014 11:52:57 AM : [iNST-TX-I1 ] 02 62 20 8B C4 0F 10 00 Sat 08/23/2014 11:52:57 AM : [iNST-ACK ] 02 62 20.8B.C4 0F 10 00 06 ID-REQ (00) Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Cannot determine device type Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Failed to add device Later ISY firmware may issue a different sequence of commands. Overall comm with the device is good.

The EZFlora design is patterned after most other irrigation controllers. I have used two different RainBird controllers and they both only allowed one Zone at a time. The EZIO8SA has 8 independently controlled relays which can be used for irrigation. An irrigation controller does not need to have the current Zone turned Off when moving to a new Zone as the current Zone is automatically turned Off. Valve operation with the EZIO8SA is controlled by ISY programming. The ISY does not support setting the EZIO8SA timers. The relay timers are set with the Simplehomenet Utility Suit (free software from Smartenit). Usually requires an additional PLM used by the Utility.

Deleting and adding the device will resolve the missing E2 link record. I would display the device link database after the add to double check the E2 link record pointing to the PLM was created. The devices are removed from the Scenes during the Delete. The Scenes will have to be rebuilt for the deleted devices. There is no fast means of processing a large list of devices.