Can't control VenStar tstats from ISY or MobiLinc App

[muck4618]

I installed two VenStar T1700's yesterday, they linked up fine, I can query them fine, change settings on the tstat and they update on the ISY/MobiLinc but if I change any settings on the ISY-99i or Mobilink it never updates the tstat. I was running the current official firmware but upgraded to the latest Beta and same symptoms. I tried deleting the tstat from both the official firmware and the beta release; same symptoms. I have tried having setting the tstat in different modes at the tstat (Auto, Cool, etc) and same symptoms. Any suggestions would be appreciated.

 

Thanks,

Scott

[Michel Kohanim]

Hi Scott,

 

Please:

1. Remove your thermostat from ISY

2. Upgrade to 3.2.4 (viewtopic.php?f=25&t=8495)

3. Add your thermostat back

 

With kind regards,

Michel

[muck4618]

I have already upgraded to 3.2.4. Is there a way to get it to work after upgrading or will I have to remove them, downgrade, upgrade and add them after the upgrade. In other words is there a way to get the tstats to work after upgrading to 3.2.4?

[LeeG]

Stay on 3.2.4, there is no need to downgrade. Delete the tstat adaptor and add it back under 3.2.4. I think there is concern it could be an I2CS device. It would not have been added correctly under 3.1.17.

[muck4618]

I removed one of them and added it back in after upgrading but it still did the same thing. Do I need to remove both of the tstats and reboot the ISY or something before adding them back in?

 

I just want to send a thanks to everyone on this forum. This is a great source of information.

[muck4618]

If anyone else is having this problem ISY has looked at the communication logs between the ISY and the VenStar and they think it has to do with the firmware version running on the tstats. Mine report firmware version .95. ISY recommends that I request replacements for the tstats which I will do tomorrow.

[Michel Kohanim]

Hello muck4618,

 

Thanks so very much for the post and YES INDEED integrated thermostats v95 have a buggy firmware such that the engine reports as i1 but the device itself acts as an i2cs device (it expects checksum and rejects PEEK/POKE).

 

With kind regards,

Michel

[muck4618]

I ordered two replacement tstats today. They said v .95 is the current shipping firmware so I'm not encouraged that the replacements will behave any differently.

[jahn]

hmm. This looks to be my issue as well. Is there any way to force the isy to use i2cs commands with the v95 thermostat?

[LeeG]

No. There is an advance option in link management that directs the ISY to use what the device says it supports. If the adaptor is not reporting I2CS the ISY will not use it that way.

 

Did you trace the Query Insteon Engine to verify the adaptor is not reporting I2CS?

[jahn]

hmm...says INST-TX-I1 --- can I assume it's using I1 then?

 

 

Sat 04/14/2012 11:32:02 PM : [All ] Writing 1 bytes to devices

Sat 04/14/2012 11:32:02 PM : [iNST-TX-I1 ] 02 62 14 92 49 0F 0D 00

Sat 04/14/2012 11:32:02 PM : [iNST-ACK ] 02 62 14.92.49 0F 0D 00 06 (00)

Sat 04/14/2012 11:32:02 PM : [iNST-SRX ] 02 50 14.92.49 1B.FC.68 2B 0D 02 (02)

Sat 04/14/2012 11:32:02 PM : [standard-Direct Ack][14.92.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 04/14/2012 11:32:02 PM : [14 92 49 0 ] Calibrating engine version

[jahn]

this is strange. Now the Thermostat works (after I did the query). Here is a trace when I changed it from heating -> off. Strange strange.

 

 

Sat 04/14/2012 11:37:39 PM : [iNST-TX-I2CS] 02 62 14 92 49 1F 6B 09 00 00 00 00 00 00 00 00 00 00 00 00 00 8C

Sat 04/14/2012 11:37:39 PM : [iNST-ACK ] 02 62 14.92.49 1F 6B 09 00 00 00 00 00 00 00 00 00 00 00 00 00 8C 06 (09)

Sat 04/14/2012 11:37:40 PM : [iNST-SRX ] 02 50 14.92.49 1B.FC.68 2B 6B 09 (09)

Sat 04/14/2012 11:37:40 PM : [standard-Direct Ack][14.92.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 04/14/2012 11:37:40 PM : [ 14 92 49 1] CLIMD 0

Sat 04/14/2012 11:37:40 PM : [iNST-TX-I1 ] 02 62 14 92 49 0F 6A 20

Sat 04/14/2012 11:37:40 PM : [iNST-ACK ] 02 62 14.92.49 0F 6A 20 06 (20)

Sat 04/14/2012 11:37:40 PM : [iNST-SRX ] 02 50 14.92.49 1B.FC.68 2B 6A 00 (00)

Sat 04/14/2012 11:37:40 PM : [standard-Direct Ack][14.92.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

[LeeG]

The tstat reports as an I2CS device.

 

Sat 04/14/2012 11:32:02 PM : [iNST-SRX ] 02 50 14.92.49 1B.FC.68 2B 0D 02 (02)

 

Perhaps the correct value was not set from the device add.

 

Do a Show Device Links Table for the tstat and then Compare to see if all the link records the ISY thinks should be there are there.

[jahn]

I get a lot of mismatch

What does it all mean? Also, is there anywhere I can download all these codes?

 

 

Device Links Table : 14.92.49 - Main / 14 92 49 1

4088

162

0

1834088

216646

4080

162

0

1834088

153931

4072

0

0

0

0

4064

226

2

1834088

16719618

4056

226

3

1834088

16719619

[LeeG]

Can you do a screen capture of the Show Device Links Table results. That export file was not meant to be processed by a human. I suspect that something did not work correctly during the device add process. Thus the links are not correct.

 

Now that the device is reporting as an I2CS device try a Restore Device to recreate the links in the tstat.

 

The question about link record format came of a day or two ago. I could not find any of the old documents that cover the link record format.

[jahn]

did a restore and it looks a lot better now. Thanks a lot for all the help

[muck4618]

I was able to get one of my tstat to start working by removing it and the LampLinc (dual-mode) from the ISY and doing a "Add new Insteon Device" and manually selecting the lamplinc model and then adding in the tstat. After adding in the lamplinc back in I am getting some periodic "Unable to communicate" error on the lamplinc and the tstat because it is communicating through the lamplinc. When I query the tstat I get Max hops = 3, Hops remaining = 0. Is that normal because it is the last device in the chain and can relay to anything else?

[LeeG]

muck4618

 

What ISY firmware is being used?

 

The latest LampLinc is an I2CS device which requires 3.2.4.

[muck4618]

Yep, I'm running 3.2.4.

[LeeG]

If the LampLinc was added to the ISY under 3.2.4 there is a comm problem to that circuit. Hops left 0 is another indication of poor comm to that location.