Upgrading from HS V2.2.0.66 to V2.3.0

[ANTOLIVEIRA]

[Michael McSharry]

It seems as if something is interfering with the ability of ADIOcelot to interact over the RS232 link with the ocelot. At startup ADIOcelot gets the parameters from the ocelot including the rev info and the connected units. The units provided by ocelot are displayed on the setup form. The request for units is done only on startup or upon return from spawning out to use CMAX. Error events are logged for bad communications so it seems like you are more likely seeing HS not seeing the units vs. ADIOcelot not seeing the units. You will need to confirm this by looking at the setup form to see what units are reported. In the same form you will see house code assignments for each interface unit. You should confirm that these are as you expect. If house codes have been reassigned then a variety of things within HS could be messed up.

[Rupp]

The first thing I would recommend is upgrading to the latest release version of HomeSeer that was released today. It's version 2.3.0.16.

[ANTOLIVEIRA]

It seems as if something is interfering with the ability of ADIOcelot to interact over the RS232 link with the ocelot. At startup ADIOcelot gets the parameters from the ocelot including the rev info and the connected units. The units provided by ocelot are displayed on the setup form. The request for units is done only on startup or upon return from spawning out to use CMAX. Error events are logged for bad communications so it seems like you are more likely seeing HS not seeing the units vs. ADIOcelot not seeing the units. You will need to confirm this by looking at the setup form to see what units are reported. In the same form you will see house code assignments for each interface unit. You should confirm that these are as you expect. If house codes have been reassigned then a variety of things within HS could be messed up.

Hi,

Michael, after a night with all the system down, next day, when restarting the plugin identified correctly all the units. Also the house codes are correct.

Using scripts some output's triggered, some others diddn't trigger at all.

I tryed to understand the reason and I found that when I use something like "cpuxa.setpoint 11,10,1" the output turns on, but when I used something like hs.execx10 "`13","on (that worked on the previous version) doesn't work anymore (...)

Also I had to change the way some stand alone VB6 programms connected to HS 2.3.0, because in version 2.2.0.66 the previous method worked fine but now Not anymore. I think HS really changed something in the HS core

Nevertheless my heating control script still doesn't work as expected. It appears sometimes (even using the cpuxasetpoint method)it fails turning on or off (...)

Mainlobby still fails triggering events

I'm seriously thinking on restore my disk image of the last HS version

Rupp: Can you give me the link to try the new 2.3.0.16, before I downgrade?

[Rupp]

The latest release is available in the HomeSeer forum here:
http://board.homeseer.com/showthread.php?t=132080