Release 3.3.3 (Beta) Is Now Available

[Michel Kohanim]

Hi Sïmon,

 

I do not think 3.3.3 was installed properly (or fully) and perhaps there lies all the problems.

 

Did you get any green 1011 icons next to any nodes? If so, it's possible that ISY is updating your devices.

 

With kind regards,

Michel

[MstrD]

I'm having a problem linking a new device. I don't know if this is a recent problem, or just my configuration.

 

I'm trying to link a 2466DW V5.9

 

It's physically connected (wired), right next to another 2466SW V5.3 (which links correctly).

 

When I start the linking process, the ISY sees it (1D.06.BE) and identifies it as a 2466DW v.41

 

It sees it, then starts the linking process. I get an error at the end that says "cannot determine device table link address" I thought maybe I had a bad switch, and installed another identical one, also V5.9. Same result. I don't think it's a a wiring issue, as it can see it fine. I even installed an access point on the same wiring about 6' away with the same result.

 

Here is the log:

Tue 10/30/2012 03:36:31 PM : [1d 6 be     ] Added to list of devices to link to ISY


Tue 10/30/2012 03:36:31 PM : [iNST-TX-I1  ] 02 62 1D 06 BE 0F 0D 00


Tue 10/30/2012 03:36:31 PM : [iNST-ACK    ] 02 62 1D.06.BE 0F 0D 00 06                 (00)


Tue 10/30/2012 03:36:32 PM : [iNST-SRX    ] 02 50 1D.06.BE 18.D0.D8 27 0D 02           (02)


Tue 10/30/2012 03:36:32 PM : [std-Direct Ack] 1D.06.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1


Tue 10/30/2012 03:36:32 PM : [iNST-TX-I1  ] 02 62 1D 06 BE 0F 10 00


Tue 10/30/2012 03:36:32 PM : [iNST-ACK    ] 02 62 1D.06.BE 0F 10 00 06          ID-REQ (00)


Tue 10/30/2012 03:36:33 PM : [iNST-SRX    ] 02 50 1D.06.BE 18.D0.D8 27 10 00    ID-REQ (00)


Tue 10/30/2012 03:36:33 PM : [std-Direct Ack] 1D.06.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1


Tue 10/30/2012 03:36:33 PM : [iNST-SRX    ] 02 50 1D.06.BE 01.1F.41 87 01 00           (00)


Tue 10/30/2012 03:36:33 PM : [std-Broadcast] 1D.06.BE-->01.1F.41, Max Hops=3, Hops Left=1


Tue 10/30/2012 03:36:33 PM : [1D 6 BE 0   ] Calibrating engine version


Tue 10/30/2012 03:36:33 PM : [iNST-TX-I2CS] 02 62 1D 06 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0


Tue 10/30/2012 03:36:33 PM : [iNST-ACK    ] 02 62 1D.06.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)


Tue 10/30/2012 03:36:33 PM : [iNST-SRX    ] 02 50 1D.06.BE 18.D0.D8 27 2F 00           (00)


Tue 10/30/2012 03:36:33 PM : [std-Direct Ack] 1D.06.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1


Tue 10/30/2012 03:36:42 PM : [iNST-TX-I2CS] 02 62 1D 06 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0


Tue 10/30/2012 03:36:42 PM : [iNST-ACK    ] 02 62 1D.06.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)


Tue 10/30/2012 03:36:43 PM : [iNST-SRX    ] 02 50 1D.06.BE 18.D0.D8 27 2F 00           (00)


Tue 10/30/2012 03:36:43 PM : [std-Direct Ack] 1D.06.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1


Tue 10/30/2012 03:36:52 PM : [iNST-TX-I2CS] 02 62 1D 06 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0


Tue 10/30/2012 03:36:52 PM : [iNST-ACK    ] 02 62 1D.06.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)


Tue 10/30/2012 03:36:56 PM : [1D 6 BE 0   ] Failed to add device

 

Is this a problem with my setup/wiring/communication or is it software problem?

[LeeG]

The I2CS Extended response to the link management command is not reaching the PLM. Without that response the ISY cannot determine where the device link database resides. Likely the other ToggleLinc is not an I2CS device where the location of the link database is assumed. This can be verified by right clicking the older ToggleLinc node, select Diagnostics | Query Insteon Engine with the Event Viewer running at Level 3.

 

The Insteon Engine command is likely returning an 01 from the older ToggleLinc rather than the 02 (I2CS) the new ToggleLinc is returning

 

Tue 10/30/2012 03:36:31 PM : [iNST-TX-I1 ] 02 62 1D 06 BE 0F 0D 00

Tue 10/30/2012 03:36:31 PM : [iNST-ACK ] 02 62 1D.06.BE 0F 0D 00 06 (00)

Tue 10/30/2012 03:36:32 PM : [iNST-SRX ] 02 50 1D.06.BE 18.D0.D8 27 0D 02 (02)

 

That aside how to get the Extended response back to the ISY PLM depends on the existing Insteon inventory. Perhaps adding a Dual Band device to the circuit the new ToggleLinc is on will help. I had a similar problem after adding an I2CS KeypadLinc Dimmer at the end of a circuit that had a collection of older I1 devices that do not repeat I2 Extended commands. Had to add a Dual Band SwitchLinc along side the I2CS KeypadLinc before I could build the link database.

 

If an outlet can be found on the same circuit (may be difficult because lighting and outlets are often on different circuits) an Access Point can be plugged in to provide the Dual Band capability.

[LeeG]

This situation can be verified easily by putting the new ToggleLinc on an Appliance cord, plugging the cord into the PLM plug point. I would expect the ToggleLinc to add when powered from the PLM location.

[brentrosales]

brentrosales

 

Right click the node, select Diagnostics | Query Insteon Engine. The 3.3.3 Beta has more device variations to support and is dependent on the Insteon Engine information being correct.

 

If that does not resolve what is the device type and firmware level show in the right pane. Run Tools | Diagnostics | Event Viewer at Level 3. Change the LED Brightness level and post the event trace.

 

This worked great! Thanks LeeG!

[MstrD]

Leeg-

 

I've had an access point installed about 6 feet away on the same circuit. My accesspoints are V2.0. Is there any reason why they wouldn't work as you described? The other Togglelinc v5.3 (which is physicall adjacent to the V5.9 and working properly) The one I'm having a problem with is V5.9. Are you saying that something in the Insteon Protocol between the V5.3 and the V5.9 that is causing a communication problem? I haven't tried yet putting the ToggleLinc on the same circuit as the PLM. That's my next step.

[LeeG]

The new ToggleLinc is I2CS, confirmed from the Event Trace. An I2CS device only supports the use of Extended length commands for link database management. I2CS devices have dropped the Peek/Poke Standard commands used by most devices for link database management.

 

SmartLabs does not publish documentation covering what devices at what firmware support I2CS. I am assuming since the older ToggleLinc works at the same location it is not an I2CS device. The older devices us Standard length commands for link database management. The procedure I described in my previous post tracing a Query Insteon Engine will confirm the older ToggleLinc is not I2CS.

 

When Standard length commands work and Extended commands do not the Insteon mesh network is not passing Extended length commands to the same degree as Standard length commands. Older devices do not know about Extended commands. They do not block them but they do not repeat them either which generally reduces the reliability of Extended commands when there are older devices involved.

 

The Access Point being a few feet away really does not mean anything since the ToggleLinc is not a Dual Band device. If the Access Point is powered from the opposite 120V leg the Extended messages would have to travel a much longer distance than 6'.

[ski2020]

3.3.3 upgrade went smoothly.

 

One new bug - every time I change a stat setpoint (by program or through the AC) it triggers my "stat out of range" email. To clarify, I have an alert email sent whenever any of my 6 stats are set below 60 or above 79. If I use the AC to change a stat from 70 to 69, it triggers the email. I noticed the problem when I started getting sets of 6 email alerts twice a day, when I set programmatically change my setpoints for all my stats. This never occurred in previous versions.

 

Thanks,

Ski

[LeeG]

Can you post the Program?

[MstrD]

Leeg,

 

I was able to "solve" my problem. I did as you suggested and put the Togglelinc on an cord and plugged it into the same outlet as the PLM. It worked fine. So that confirmed a communication problem.

 

My original setup uses a dual-band PLM, and I had an access point on the same circuit as the Togglelinc in my kitchen (and in this case it was plugged in only a couple feet from the Togglelinc, on the same circuit). I couldn't get it to work even though it would seem like it should.

 

I was able to swap the V5.9 for a V5.45 Togglelinc that I already had installed. It worked from that location. Once I had one V5.9 working, I was able to communicate with the Togglelinc that I was having the original problem. My "guess" is that once I had one, it would relay the signal. Once I had that working, it seemed to be ok. The more I add, the better the network will probably be.

 

So at this point, I'm all good.

[LeeG]

Great news. You are absolutely correct, the more new devices installed the better the overall network responds because each new device is now a repeater of Extended commands.

 

I have many old devices as I started with Insteon near the beginning of Insteon. Decided to start replacing the old stuff with new SwitchLincs and ran into the paddle color mismatch. Now I am stuck because I cannot replace the old I1 ICONs with new SwitchLincs because the paddle color does not match anything else. Not every switch I have is Insteon. Some switches did not make sense to be changed to Insteon so I have several manual paddle switches that would not match the SwitchLinc alongside it and the cover plates do not match. Got to love SmartLabs and Smarthome!

[ski2020]

Thanks Lee.

 

I am in heating mode now and it turns out that the cool setpoints were out of range (0) for all the stats. My program tested to see if either the heat or cool setpoint was out of range. So whenever I changed the heat setpoint, the program would send an alert. All set now.

[Automate the World]

Anyone else having issues with the 2441ZTH? Shows up as an unsupported Device:5.10 when I try to link it to the ISY994i.

[LeeG]

alphamale78

 

Run Help | About and verify both Firmware and UI indicate 3.3.3. Sounds like the UI (Admin Console) is not at 3.3.3. That is caused by not clearing the Java cache after installing 3.3.3 on the ISY and/or no using the correct URL to invoke the 3.3.3 Admin Console.

 

I have installed a 2441ZTH successfully.

[Automate the World]

alphamale78

 

Run Help | About and verify both Firmware and UI indicate 3.3.3. Sounds like the UI (Admin Console) is not at 3.3.3. That is caused by not clearing the Java cache after installing 3.3.3 on the ISY and/or no using the correct URL to invoke the 3.3.3 Admin Console.

 

I have installed a 2441ZTH successfully.

 

 

I had a shortcut to 3.3.2, thank you so much, working great now!