RemoteLinc and EZIO40

[porscheguy]

I have a remotelinc controlling an EZIO40 in a scene. The scene looks correct to me now that I've updated my firmware to 8.14 (it didn't before). I've checked the link tables on both devices and they seem to be correct and the compare shows everything as it should be.

 

I can activate the EZIO40 device by using the device window directly so the ISY-EZIO communications is good. If I activate the key on the remotelinc (the first key) the scene updates to show the EZIO turned on or off as the case may be. The problem is that a query shows the EZIO is not responding to the key. The same result occurs if I activate the scene.

 

Watching the event window I don't see anything wrong - but I may not recognize it if it is wrong.

 

Any suggestions? I'm under the impression the EZIO40 and remotelincs are fully supported now. The version number of the EZIO40 seems to be VFF and for the remotelinc it seems to be v00 (does that make sense?).

 

By the way I have multiple access points and on both phases of power. But since I see ISY to EZIO communication and remotelinc to ISY it seems that shouldn't be the problem. And the fact the scene itself doesn't work indicates to me something else is amiss.

 

Suggestions?

[LeeG]

What firmware were you running when the EZIO4O was added to ISY?

 

EDIT: I created a Scene with RemoteLinc button 1 as Controller and EZIO4O relay 4 as Responder. RL button controls EZIO4O relay and Admin Console reflects state change and a Query reflects the state of the relay.

 

Note that the EZIO4O has to be added to the EZIO4O under one of the 2.8.x images. If the EZIO4O was added to the ISY under 2.7.15 and then the ISY image updated to 2.8.14 the Scene will not work.

 

If the EZIO4O was added to the ISY under a 2.8.x image what EZIO4O relay is used in the Scene?

 

Lee

[porscheguy]

Thanks for the input.

 

I'm afraid I didn't write down the previous build number. My ISY is new, but I know it didn't have anything in the 2.8.x range. When I couldn't get the scene to work under the old firmware I realized I might need to update.

 

As for the relay on the EZIO40 - I want to use the first relay in this scene.

 

I have tried Write Updates to device and restore device. What are the steps to remove the device from the ISY world and re-adding it? Any special procedures needed? I will try deleting and re-adding the device and see if that works.

[porscheguy]

Update:

 

I deleted the EZIO40 and re-added it under 2.8.14 firmware. I then added the EZIO to the scene and made sure the remotelinc was linked again. When I do the links compare with the ISY for both the remotelinc and the EZIO40 all links are identical but there is an extra record with a bunch of FFs which I take to be meaningless.

 

Similar result: I cannot control the device with either the remotelinc or the scene itself. The scene indicates all is well but a query shows no response by the EZIO.

 

In the event viewer, when I press the button on the remotelinc, I get a lot of activity but I note a phrase "process message failed" which obviously isn't good. However when I activate the scene, I get a single communication line and that also is wrong. I haven't advanced to the position of fully understanding every hex character but there should be more activity than a single line. That line is

 

Wed 02/09/2011 08:49:59 AM : [iNST-ACK ] 02 62 00.00.10 CF 13 00 06 LTOFFRR(00)

 

So far I don't know what this means.

 

It seems the first line of attack is to get the scene itself to work correctly since that is just ISY to EZIO40 communication (as far as the EZIO responding anyway). I repeat I can operate the EZIO fine directly using the device communication window - just not the scene that has the EZIO in it.

 

Any more input or suggestions?

[Sub-Routine]

[iNST-ACK ] 02 62 00.00.10 CF 13 00 06 LTOFFRR(00)

 

This line says the group command is sending an Off.

Be sure that within the scene the EZIO is set to On.

 

Here's some help concerning the Event Viewer:

ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer

[porscheguy]

Well, OK. the command was to send a group command to the EZIO to turn off (or open) the relay when it was actually already off. Maybe that is what is supposed to happen. Here is what happens when it is off (previously determined by a query) and a command to turn it On is given followed by a query which shows it is still Off:

 

Wed 02/09/2011 10:32:08 AM : [iNST-ACK ] 02 62 00.00.10 CF 11 00 06 LTONRR (00)

 

Wed 02/09/2011 10:32:08 AM : [ 1 72 14 1] ST 255

 

Wed 02/09/2011 10:32:22 AM : [iNST-ACK ] 02 62 01.72.14 0F 4F 02 06 IOCTL (QUERY)

 

Wed 02/09/2011 10:32:22 AM : [iNST-SRX ] 02 50 01.72.14 AA.AA.AA 2B 4F 00 IOCTL (00)

 

Wed 02/09/2011 10:32:22 AM : [standard-Direct Ack][01.72.14-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Wed 02/09/2011 10:32:22 AM : [ 1 72 14 1] ST 0

 

Wed 02/09/2011 10:32:22 AM : [iNST-ACK ] 02 62 01.72.14 0F 49 00 06 RINPUT (00)

 

Wed 02/09/2011 10:32:22 AM : [iNST-SRX ] 02 50 01.72.14 AA.AA.AA 2B 49 00 RINPUT (00)

 

Wed 02/09/2011 10:32:22 AM : [standard-Direct Ack][01.72.14-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

In this case the first 2 records seem to indicate an ISY command to turn the EZIO relay on, and indicates that it is on but the quesry shows it is actually still off.

 

 

My point after all this is I think I have followed all the correct procedures (updated firmware, deleted both the EZIO and the remotelinc, added them back in, re-established the links and verified them, re-created the scene and so on and yet neither the remotelinc nor the scene work as advertised or expected.

 

At this point I guess I need to ask for phone support. In time, and after way too much grinding in the intricacies of error logs, event viewers etc., maybe I could figure this out. But this is supposed to be straightforward and I need some clues.

 

Thanks for the input so far -

[LeeG]

porscheguy

 

Which device has the bunch of FF's in the link record? Can you post the link record display.

 

If you can post the Event Viewer (be sure Device communications events set) when the RemoteLinc button is pressed I can be sure but it is normal for several messages to flow from a RemoteLinc (and other RF devices such as Motion Sensors and TriggerLincs).

 

 

 

This is the Event Log from my test with RL button 1 controlling EZIO4O relay 4. This is the RL On button press

 

Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C7 11 00 LTONRR (00)

 

Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 12:36:06 PM : [ 11 AD CF 1] DON 0

 

Wed 02/09/2011 12:36:06 PM : [ 1 DC 76 4] ST 255

 

Wed 02/09/2011 12:36:06 PM : [ 11 AD CF 1] ST 255

 

Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C3 11 00 LTONRR (00)

 

Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=0

 

Wed 02/09/2011 12:36:06 PM : Duplicate: ignored

 

Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 00.00.01 C3 11 00 LTONRR (00): Process Message: failed

 

Wed 02/09/2011 12:36:06 PM : [standard-Group][11.AD.CF-->Group=1] Max Hops=3, Hops Left=0

 

Wed 02/09/2011 12:36:06 PM : [iNST-SRX ] 02 50 11.AD.CF 12.9F.E4 41 11 01 LTONRR (01)

 

Wed 02/09/2011 12:36:06 PM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

This is the Event Viewer of the Admin Console Scene On button click. There is no status line display as the relay was already On

 

Wed 02/09/2011 12:36:49 PM : [iNST-ACK ] 02 62 00.00.3C CF 11 00 06 LTONRR (00)

 

This is the Event Viewer of the Admin Console Scene Off button click.

 

Wed 02/09/2011 12:37:04 PM : [iNST-ACK ] 02 62 00.00.3C CF 13 00 06 LTOFFRR(00)

 

Wed 02/09/2011 12:37:04 PM : [ 1 DC 76 4] ST 0

 

This is the Event Viewer of the Admin Console Scene On button click.

 

Wed 02/09/2011 12:37:12 PM : [iNST-ACK ] 02 62 00.00.3C CF 11 00 06 LTONRR (00)

 

Wed 02/09/2011 12:37:12 PM : [ 1 DC 76 4] ST 255

 

This is the Event Viewer of the Admin Console Scene Off button click.

 

Wed 02/09/2011 12:37:17 PM : [iNST-ACK ] 02 62 00.00.3C CF 13 00 06 LTOFFRR(00)

 

Wed 02/09/2011 12:37:17 PM : [ 1 DC 76 4] ST 0

 

Lee

[LeeG]

porscheguy

 

Thanks for your last post. I was writing mine before seeing the newest post.

 

How old is the EZIO4O?

 

The Scene On/Off from the ISY is only one command.

 

It was necessary to add the device under a 2.8.x image as they are the only images which have the code to determine the size of the internal PLM memory in the EZIO4O.

 

The symptoms appear as though the link records in the EZIO4O are not working. In the past (before 2.8.x) this was the result of the link records being written at the wrong location because of a larger memory in the EZIOxx devices.

 

When you added the EZIO4O did you use the New INSTEON Device AND specify the Device Type as EZIO4O? This is the only technique which has the code to determine the PLM memory size.

 

Lee

[porscheguy]

The EZIO is perhaps 2 yrs old - I'd have to do some research.

 

I used the New command and chose the EZIO40 from the drop-down list. All seemed to go well. The link lists seem to be good. It came up with all 4 parts of the EZIO and so far I am only working on the first relay. Outside of the scene and the use of the remotelinc, all works fine, even the other relays in programs or direct device communication (under the old firmnware and not in scenes).

 

Unfortunately I have other duties calling and won't be able to continue this until later.

 

I will look into when the EZIO was purchased.

 

Thanks -

[LeeG]

porscheguy

 

Sorry you are having this difficulty. You have done everything correctly. There was a small window of time when Smartlabs was moving the PLM to the large memory model (supports 2000+ links) where PLMs had the large memory but the PLM firmware used it as though it had small memory. The result of this combination is that the ISY writes the link records where they should be for a large memory PLM but the PLM firmware ignores these link records. The only solution to this is to return the EZIO4O to SHN and have them update the device to the latest PLM and firmware levels.

 

There is a method to determine this condition. It is somewhat involved. Factory reset the EZIO4O, do a Set button link with another Insteon Controller device. The internal PLM firmware in the EZIO4O writes the link record in this case. Use the Show Device Links Table to display the EZIO4O link database. If the Set button link does not display then there is a memory/firmware mismatch. If the link record does display then see if the other Controller device will actually turn the linked relay On and Off. The relay can be heard (click) when it turns On.

 

I ran my initial test here to be sure nothing had regressed at 2.8.14. With it working here either the problem is specific to your EZIO4O or a communication problem where the EZIO4O is plugged. The EZIO4O can be moved to the ISY PLM plug point to see if the ISY Scene will turn the relay On/Off.

 

Lee

[porscheguy]

Thanks for the input, Lee:

 

I purchased my EZIO40 5/12/09 from SmartHome.

 

either the problem is specific to your EZIO4O or a communication problem where the EZIO4O is plugged.

 

But if the ISY does communicate fine with the EZIO as I have mentioned (just not within a scene) can the EZIO be "plugged"? By the way what does that mean, anyway? And also - it seems the links are alright.

 

Also, earlier you asked:

 

If you can post the Event Viewer (be sure Device communications events set) when the RemoteLinc button is pressed I can be sure but it is normal for several messages to flow from a RemoteLinc (and other RF devices such as Motion Sensors and TriggerLincs).

 

Here is what mine does when I press button 1 on the RL:

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00)

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : [ A 2C 72 1] DON 0

 

Wed 02/09/2011 03:20:13 PM : [ 1 72 14 1] ST 255

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00)

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : Duplicate: ignored

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00): Process Message: failed

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 AA.AA.AA 41 11 01 LTONRR (01)

 

Wed 02/09/2011 03:20:13 PM : [standard-Cleanup][0A.2C.72-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

 

I'm going to try your procedure anyway and I'll get back after I do it.

[porscheguy]

Thanks for the input, Lee:

 

I purchased my EZIO40 5/12/09 from SmartHome.

 

either the problem is specific to your EZIO4O or a communication problem where the EZIO4O is plugged.

 

But if the ISY does communicate fine with the EZIO as I have mentioned (just not within a scene) can the EZIO be "plugged"? By the way what does that mean, anyway? And also - it seems the links are alright.

 

Also, earlier you asked:

 

If you can post the Event Viewer (be sure Device communications events set) when the RemoteLinc button is pressed I can be sure but it is normal for several messages to flow from a RemoteLinc (and other RF devices such as Motion Sensors and TriggerLincs).

 

Here is what mine does when I press button 1 on the RL:

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00)

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : [ A 2C 72 1] DON 0

 

Wed 02/09/2011 03:20:13 PM : [ 1 72 14 1] ST 255

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00)

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : Duplicate: ignored

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 00.00.01 C7 11 00 LTONRR (00): Process Message: failed

 

Wed 02/09/2011 03:20:13 PM : [standard-Group][0A.2C.72-->Group=1] Max Hops=3, Hops Left=1

 

Wed 02/09/2011 03:20:13 PM : [iNST-SRX ] 02 50 0A.2C.72 AA.AA.AA 41 11 01 LTONRR (01)

 

Wed 02/09/2011 03:20:13 PM : [standard-Cleanup][0A.2C.72-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

 

I'm going to try your procedure anyway and I'll get back after I do it.

[LeeG]

Sorry, I meant to move where the EZIO4O is plugged into to the same location as the ISY PLM to eliminate any question about powerline communication. I don't think it is a communication problem but it is easy to eliminate the question by moving where it is plugged in.

 

The content of the link records should be correct under 1.8.14. It is where they are written in memory. Specifically I am assuming the internal PLM memory is large so the ISY is writing link records at 3FF8 which is where is should for a large memory PLM. I'm concerned the EZIO4O was built around the time that Smartlabs was shipping PLMs which had the large memory anticipating the move to supporting 2000+ links. We have found two PLMs (this would make three if my memory is correct) where the firmware in the PLM was at the old level where the link database memory was small and had the link records starting at 0FF8. If this is the case for your EZIO4O PLM, the PLM is looking for link records at 0FF8 with the ISY writing link records at 3FF8. Again, the physical link record has the correct information, just not written where the PLM firmware is looking.

 

There are some Zebras that I have not covered. There could be an old link record in the EZIO4O that came from 2.7.15 which the PLM is finding. I doubt that since adding the EZIO4O under 2.8.14 would normally erase all the old link records (assuming the default delete exising link records option was used during add).

 

Oh good grief. That could be a problem. The 2.7.15 image would write link records at 0FF8 but the link record content is wrong at 2.7.15. The LD1/2/3 data is not correct for controlling relays. When the EZIO4O was added using 2.8.14 it would not have cleared the links at 0FF8. Sorry. I should have thought about that sooner. I hate to ask this but I would suggest doing a factory reset of the EZIO4O after deleting the EZIO4O from the ISY. Then add it back. The factory reset will clear the entire link database. This will not fix a conflict between the memory size and PLM firmware but will fix the problem if it is related to the links records 2.7.15 wrote that 2.8.14 will not clear.

[porscheguy]

LeeG

 

Sorry, but I guess I don't know how to do a factory reset on the EZIO40. It doesn't seem to be in any of my documentation.

[Brian H]

Try unplugging it for at least ten seconds.

While holding the set button plug it back in.

Keep holding the set button for ten seconds then release the set button.

[porscheguy]

OK - now what is going on! This is like many of my projects - I start making a small change and things snowball.

 

I decided to do your last suggestion: I deleted the EZ, then did the factory reset, then I added it back into the ISY using the address and pulldown menu approach.

 

I then decided to look at the links table of the EZ. It comes back with:

 

0FF8 : 00 10 AA.AA.AA FF 00 00

 

I then did a Compare. In the past a window comes up and shows the ISY table and says identical or not on each line. Now I never get the other window and I have an hourglass cursor that won't quit.

 

I exited out of the admin window, reopened and all looked good. But if I try to compare link tables I get the hourglass again.

 

Should I have removed the remotelinc too?

 

Finally - I did delete the remotelinc (because there might have been some vestiges of connection to the EZ) and restarted the admin window.

 

When I looked at the links table for the EZ it is a single line as above. But this time instead of a compare right away, I instead looked at the ISY links table and for the EZ it is blank. Why isn't there a link? And by the way the EZ works if I send a command from the device window.

 

Also by the way - once I removed the remotelinc I no longer get the hourglass when I hit the compare but I don't get the behavior I saw before either (window popping up showing identical on each line) even for a "good" behaving insteon device where the two links tables look the same except for a line in the device with all zeros.

 

Now what?

[LeeG]

The link record is the end of list marker, a 00 in the first byte. The other bytes have no meaning in the end of list record. A factory reset would normally clear all the link database area. This is another indication the PLM memory is large but the PLM firmware is treating it as small. The PLM only cleared the memory it thought it had rather than the memory it really has. The end of active list indicator was set by the ISY during the device add.

 

I will delete my EZIO4O to confirm this but I don't think the ISY establishes any links during the device add process. Since the device has no Inputs there is nothing to establish so the ISY would be aware of Input changes. The ISY does not establish links to the Output Relays until a Scene is defined with a relay as a responder.

 

I’m 95% sure this is a memory size PLM firmware mismatch. Defining a link between a Controller (like the RemoteLinc since you have deleted it from the ISY) with an EZIO4O relay using the Set button on the EZIO4O will confirm this. I expect the Set button link will work but the link record will not display. This will be the result of the PLM writing the Set button link at 0FF8 while the ISY is looking at 3FF8 because of the larger memory being physically present. There will be an audible click when the EZIO4O relay turns On.

 

The relays can be turned On and Off with the Admin Console because Insteon Direct commands are used which do not use link records.

 

I’ll post again after I have deleted and added the EZIO4O to my system and verified that no link records would be expected.

[LeeG]

porscheguy

 

The ISY device add for an EZIO4O does not create link records in the EZIO4O because it has no Inputs. The single end of list entry is normal.

 

Lee

[porscheguy]

I’m 95% sure this is a memory size PLM firmware mismatch. Defining a link between a Controller (like the RemoteLinc since you have deleted it from the ISY) with an EZIO4O relay using the Set button on the EZIO4O will confirm this. I expect the Set button link will work but the link record will not display. This will be the result of the PLM writing the Set button link at 0FF8 while the ISY is looking at 3FF8 because of the larger memory being physically present. There will be an audible click when the EZIO4O relay turns On.

 

So let me get this straight: for this experiment do I link the devices "outside of the ISY"? In otherwords act like there is no ISY and link the devices first by putting controlling device (e.g. a SwitchLinc) in the linking mode and then put the EZIO40 in linking mode (by using the Set button sequence for the particular relay)? Then add the EZIO40 and look at the links? Should both devices (the SwitchLinc and EZIO40) be deleted from the ISY before doing the preceding?

[LeeG]

The EZIO4O is currently defined in the ISY with no links (scenes). The Show Device Links Table shows the one end of list entry posted above.

 

The Set button link is done outside of the ISY. Do not change anything in the ISY. The EZIO4O remains defined in the ISY with no Scenes. Put a Controller into linking mode. A SwitchLinc would be fine. A button on the RemoteLinc would be fine. Most controllers will entry linking mode by pressing the On button for approx 10 seconds. Then press and hold the Set button on the EZIO4O until the controller recognizes the EZIO4O. This will take 3-4 seconds to link to most controllers. Tap the EZIO4O Set button once to have the link control relay 1. Press the EZIO4O Set button for 3-4 seconds to complete the Set button link. Press the controller On and Off buttons to confirm the relay turns On and Off (should hear the relay click). This manual linking process is described in the EZIO4O Quick Start guide.

 

Now run a Show Device Links Table in the ISY. I am expecting the link just established with the Set button will not be displayed.

[porscheguy]

OK. After some detours I was able to carry out the experiment and I think you've got it nailed.

 

I was able to link the EZIO40 to a SwitchLink in the same circuit a few feet apart. The relay on the EZIO40 does activate (click).

 

The links table on the SwitchLink does show a link to the EZIO40 but the links table on the EZIO40 is the same as before.

 

So - bottom line I need newer firmware on the EZIO40?

 

I've got a call into Simple Home Net to see how I can get this done.

 

Thanks for all the help. (I've got to go away for awhile but I'll check in later.)

[LeeG]

Yes. Simplehomenet provides a service that will refresh the device firmware to the latest level as well as updating the internal PLM to the latest firmware. This service can be ordered online from the SHN web site under Products | Services.

 

Sorry it took so much to get to this point. I don't like to suggest having a device updated unless absolutely certain and necessary. Most of the time the problem is not having added it under a 2.8.x image.

[fuentesa]

I'm having the same problems with an EZIO40. It shows on ISY as a v.00. I can control the outputs directly but they didn't respond to the scenes command. It work if I establish the link manually. The link was added mannualy does not appears when in the device link table.

 

When I connect to the EZI using the SHN software it displays as a version 28 and shows as a large memory device. I just purchase the EZI last month, so the version should be recent, however I haven't found what is the most recent version.

 

 

The version of ISY is 3.1.17. The links begins at memory 0FF8.

 

Any help?

[LeeG]

How was the EZIO4O added to the ISY? Start Linking, New INSTEON Device, what options were used?

 

Manual Set button links may not show up under the ISY. They are not known to the ISY and will eventually be erased or overlaid. Manual Set button links should not be done when using an ISY. They were done above as a diagnostic test.

 

The Show Device Links Table shows a starting address of 0FF8 even though the starting address is likely 3FF8 for a large memory internal PLM.

 

What will be helpful, besides knowing exactly how the EZIO4O was added to the ISY, is a Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected, and add one of the EZIO4O nodes as a Responder to an ISY Scene. That will show where the link record is actually being written. Post the Event Viewer trace.

[fuentesa]

I added it using the new insteon device, enter the device address and selecting the device type as a EZIO40 from the list. It was added successfully and the four outputs were displayed. I will post the event log when once I get home.