device type changed to Interface Variable.1

[pete17c]

I did a fresh install of HS 2.1.104.0 and ADIOcelot and went through the setup a few times to get things set and all seemed well, but after a HS restart I got an error similar to this . .

11/8/2006 7:53:24 PM - Warning - (1)Device Ocelot HVAC OutsideTemp has properties different from its current device type of Interface Variable - device type has been changed to Interface Variable.1


. . for each of my ADI variables and the devices stopped updating . .

appreciate any ideas . .

Pete C

[YoYo]

Been doin' that to me for a long time....

[ajgriglak]

This is happening to me now too.

Any updates on this issue?

What are you guys doing as a workaround? Redoing all Ocelot variables each startup?

[Michael McSharry]

I submitted a help desk ticket related to this a couple months ago. Rupp indicated that patience is in order since Rich is backed up.

[Rupp]

Michael,
Rick put up this Knowledge Base article a while back about this error:

http://www.homeseer.com/cgi-bin/help...iew=67&lang=en

[Michael McSharry]

Rupp,
The reference describes that new device types will be created automatically, but provides no insight into how hs treats one type vs. another such as why it would no longer update a device who's device type was changed. I read this reference to mean there will be an annoying warning message in the log, but otherwise no change in how a device operates. That was why I submitted the ticket.

[Rupp]

Rupp,
The reference describes that new device types will be created automatically, but provides no insight into how hs treats one type vs. another such as why it would no longer update a device who's device type was changed. I read this reference to mean there will be an annoying warning message in the log, but otherwise no change in how a device operates. That was why I submitted the ticket.

Michael,
What's the ticket number?

[Michael McSharry]

I went looking for it and see that my ticket was about IOType and not DeviceType, but a simiar class of uncertainty about the property and expected HS actions. This means that the devicetype is an open issue if it causes devices to no longer be updated when the devicetype changes. I suspect, however, that there is something else happening and may not be directly related to devicetype. There are many ADIOcelot users and it appears to not be a problem for most.