Homeseer Script to monitor & Control ELV MAX! Thermostats

[blb]

Hi,

Based on the ELV MAX! protocol description (see domoticaforum.eu/viewtopic.php?f=66& ... amp;t=6654) I have developed a Homeseer Script to monitor and control the Max! Thermostats (via the Max! Cube). I will keep this post & the attached files up to date. This topic can be used to discuss further development of the Homeseer scripts.

See topic Individual Room Control ELV the MAX! domoticaforum.eu/viewtopic.php?f=66& ... amp;t=6239 for more information about the ELV Max product.

P.S. I'm using no other devices than the Thermostats; the script is for Thermostats only!

Capture29-4-2010-23.04.305-11-2011-0.39.43.jpg

Created events:

HS CM MAX Events.jpg

20130111 version 02p new / changed functionality since version 02l:
changed device type with MAX part (Cube or RT), Serial number/address/Firmware version/[device number]
removed separate device with Serial number/address/Firmware version/[device number]
changed MAX!RT device value "Mode/Setpnt/Valve%/EndDateTime" to Setpoint value
added MAX!RT device "Current Temperature" (Corrected with Offset). The current temperature is not always available, the device value/string stay untouched in that case
added option to hide status IF status = OK and hide Temperatures via .ini file
added WaitSec option in .ini file to set the waittime (for response from cube) in the .ini file. Too short time can lead to out of array error as found by Fischi
added listboxes for temperature control for each Radiator Termostat, setpoint can be set via this listbox
added latest update time Thermostat Status after change device string
added firmware version Thermostats, Firmware version is now displayed in Decimal (and not HEX)
20121004 version 02l new functionality:
adapted debug setup. debug levels 0 (no), 1 (all full decoded info), 2 (1 + all base64 decoded info)
improved C: response decoding, now response from other devices (wall switch, wall Thermostat) will be skipped properly
default port changed in config file to 62910 due to change since firmware version 0109
added comment in script file for solution for out of array error found by Fischi
20120108 version 02i new functionality:
Improved L: response decoding, now response from other devices (wall switch, wall Thermostat) with other response length will be skipped properly
20120108 version 02h new functionality:
via parameter in ini file the location and location2 fields can be interchanged
20111105 version 02f new functionality:
new decoding: Cube date, Time and timezones (including check with current time), Valve opening, boost settings
Send s: command (Send Device Command) in script
2011101 initial version (02a)

[jrkalf]

Very nice work BLB.

I've moved your project to the Homeseer Scripts Forum and created a "shadow copy" in the ELV thread.

[djdive]

Nice job, think need to change the valves in my home so i can use this system

[Phaeton]

I'm keen to do this to. Do you use the thermostat and thermostic valves? Are both controlable with this script?

[blb]

Phaeton,

I'm only using the thermostats (and off course a Cube), this script is only to monitor & control the thermostats. I don't see that much reason to use other MAX! components, via Homeseer I can use any other temperature sensor, door/window sensor and controls to control the thermostats.

[Phaeton]

The reason why i asked is because of this.

I assume when you use thermostats you mean the thermostatic valves mounted on the radiator.

For i know the thermostatic valves do not send a request to the kettle when they need additional heating.

Example:
on a cold winternight... I would like my bedroom on 19c but i dont need heating in my livingroom. In my livingroom i have a regular thermostat which is set on 14c during the night. Because the temperature in my livingroom is 14c, the kettle is turned off. If i set the thermostatic valve in the bedroom to 19c i won't get the heating because the regular thermostat (livingroom) doesn't signal the kettle to start heating and pumping warm water through the radiators. This because the temperature in the living room has already reached its setting.

So to be in total control i need to be able to either switch the kettle on directly or i should be able to let the thermostat in the livingroom send a signal to turn the kettle on.

Maybe i'm mistaken. But this was the reason to ask this. What do you think?

[Digit]

I have the same problem: one thermostat in the livingroom to control the central heating.
With as additional problems lots of glass on the south side (-> sun is warming up the living, central heating very often stops burning at noon when it's not too cloudy). To make it a bit more difficult: I want my central heating to be controlled by a modulating thermostat, cause on/off causes too much ups & downs in floor(heating) temperatures; we don't like that.

I've got a few options:
- use a modulating thermostat with external input (like a Honeywell Chronotherm Modulation with TELE);
- learn my system to talk OpenTherm with this: http://www.tclcode.com/opentherm/index.html

For an on/off system a relay (parallel on the thermostat wire) which you can control would probably suffice.

HTH

[blb]

Well, I'm afraid we can have a long off-topic discussion on heating..... I'll try to keep is as much as possible on-topic....
I have a very common setup in my house with 1 main room thermostat in the living room and thermostatic valves in all other rooms in my house. I'm now replacing the standard manual operated thermostatic valves by Max! Thermostatic valves. The main reason for me is to be able to central manage temperature per room. In practice all valves are always in the same position, trying e.g. to get the temperature in the bathroom the whole day long at 21 degrees....

The overall advantages and disadvantages of a setup with 1 room thermostat and thermostatic valves in the other rooms are not changed by this replacement. One major disadvantage of this setup is you don't get the other rooms warm if it's already warm enough in the living room. In a lot of houses the heating capacity in the living room is big and after the initial heating in the morning there is no need for a lot of 'power' anymore. Especially with a modulating boiler (CV), the water temperature will be low and it will be almost impossible to heat an other room during the day. The boost function of the MAX! Thermostatic valves will not have a big effect as well; with a water temperature of 40 degrees you don't feel radiation warmth. To improve this you need a good water balance in the system (after wards / in practice you can close the valves in the living room a bit). To get rid of this, you need and other setup like separating your house in zones or weather dependent control, all coming with their own advantages and disadvantages... see some information on the following links:

cvtuning.nl/zo-werkt-dat/hoofdregelinge ... en-nadelen
renewable-energy-now.org/2010/03/weersa ... k-regelen/
http://www.heatnet.nl/zoneregeling-heatnet.html

Off course I'm planning some improvements in the (near) future. My room thermostat and (modulating) boiler (CV) are communicating via Opentherm. I have build an Opentherm gateway and monitoring and controlling this as well via Homeseer, see the topic domoticaforum.eu/viewtopic.php?f=47& ... amp;t=6634. Based on the feedback from the Max! Thermostats (% valve opening) or external temperature sensors, the system (HS) should be able to conclude the setpoint of the boiler should be higher or change temporary to weather dependent control (fireplace function). In that case I need a solution which avoids overheating the living room (separate zone)....

[Phaeton]

thanks for the, because of me, slight offtopic answer…

I’ll go back ontopic! Mega made an PHP script and a couple of days ago he integrated the wall thermostat into this PHPscript. Hey added his findings on the wall thermostat in the main MAX! encoding topic. He said there is not much difference between the wall and radiator thermostats.

As you know, I would like to use your solution within homeseer. If it is possible to integrate the wall thermostat in your script then (for me) it would be perfect. Since I don’t know how to program I would like to ask you to help me adding this functionality to your script or to add this functionality tot his script. Would this be possible? I think option 1 will cost more time

(edit) unfortionatily is the wall thermostat not a real thermostat but more or less a remote for the radiator valve thermostats. So its not necessarily to implement.

[Bastiaan]

Hi Bernard, First off all, thanks for all the work. Roberts story and your work made me buy the valves for some testing.
Currently I have 3 thermostats, one windows switch, one Ecoswitch. (as temp solution while still waiting for the wall thermostat)
Got it all installed, working better than expected. Usually got some trouble with the long distances in my house but for now it all works fine.

Installed your script and ran it.
It creates the cube and the first thermostat but than hangs on:

16-12-2011 21:25:17 - Error - Max Monitor: Index was outside the bounds of the array.

I have deleted all devices and retried but the same happens, here is a full info/debug of running the script with the current cube + one thermostat:

16-12-2011 21:22:00 ~!~Event~!~Event Trigger "Max!Recurring"
16-12-2011 21:22:00 ~!~Event~!~Running script in background: BLB_Max_monitor 02.vb
16-12-2011 21:22:02 ~!~Max_debug~!~C3: unknown device: 05
16-12-2011 21:22:02 ~!~Max_debug~!~C6: unknown device: 04
16-12-2011 21:22:02 ~!~Error~!~Max Monitor: Index was outside the bounds of the array.
16-12-2011 21:23:43 ~!~Event~!~Event Trigger "Max!Recurring"
16-12-2011 21:23:43 ~!~Event~!~Running script in background: BLB_Max_monitor 02.vb
16-12-2011 21:23:43 ~!~Max_debug~!~SWversion: 0.2f
16-12-2011 21:23:45 ~!~Max_debug~!~Full Reply: H:IEQ0114738,00ad95,0109,00000000,21d8b5ac,0c,32,0b0c10,1517M:00,01,VgIDAQZPZmZpY2UA+vQCB0JlZHJvb20A+14DCEJhY2tyb29tAJ+xBQEA+vRJRVEwMTg0OTEyFVJhZGlhdG9yIFRoZXJtb3N0YXQgMQEBAPteSUVRMDE4NDk2NhVSYWRpYXRvciBUaGVybW9zdGF0IDICAQCfsUlFUTAxODIwNTMVUmFkaWF0b3IgVGhlcm1vc3RhdCAzAwUAShRJRVEwMTQ1MDY5EUVjbyBTd2l0Y2ggb2ZmaWNlAAQAHcFJRVEwMTYwNDY2D1dpbmRvdyBTZW5zb3IgMQIBC:00ad95,7QCtlQAJAQBJRVEwMTE0NzM4AQsABEAAAAAAAAAAAP///////////////////////////wsABEAAAAAAAAAAQf///////////////////////////2h0dHA6Ly93d3cubWF4LXBvcnRhbC5lbHYuZGU6ODAvY3ViZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAENFVAAACgADAAAOEENFU1QAAwAAAAAcIA==C:00fb5e,0gD7XgECFP9JRVEwMTg0OTY2KB49CQcYAzAM/wA8WkxsPN889UUSURpFIEUgRSBFIEUgRSBFIDxaTGxA3kD2RRJRGkUgRSBFIEUgRSBFIEUgPFpMbEDeTPZFElEaRSBFIEUgRSBFIEUgRSA8WkxsQN5M9kUSURpFIEUgRSBFIEUgRSBFIDxaTGxA3kz1RRJRGkUgRSBFIEUgRSBFIEUgPFpMbEDeTPVFElEaRSBFIEUgRSBFIEUgRSA8WkxsQN5M9kUSURpFIEUgRSBFIEUgRSBFIA==C:004a14,EQBKFAUAEg9JRVEwMTQ1MDY5C:009fb1,0gCfsQEDFP9JRVEwMTgyMDUzKiI9CQcYAzAM/wBESFUIRSBFIEUgRSBFIEUgRSBFIEUgRSBFIERIVQhFIEUgRSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIERIVGxEzFUURSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIA==C:00faf4,0gD69AEBFP9JRVEwMTg0OTEyKh49CQcYAzAM/wA8STxsPNg9FD0gPSA9IEUgRSBFIEUgRSBFIDxJPGw82D0UPSA9ID0gRSBFIEUgRSBFIEUgPEk8bDzYPRQ9ID0gPSBFIEUgRSBFIEUgRSA8STxsPNg9FD0gPSA9IEUgRSBFIEUgRSBFIDxJPGw82D0UPSA9ID0gRSBFIEUgRSBFIEUgPEk8bDzYPRQ9ID0gPSBFIEUgRSBFIEUgRSA8STxsPNg9FD0gPSA9IEUgRSBFIEUgRSBFIA==C:001dc1,EQAdwQQCEw9JRVEwMTYwNDY2L:CwD7XgkSGAAiAAAABgBKFAkAAAsAn7EJEhgAAAAAAAsA+vQJEhgAHgAAAAYAHcFMEhB=
16-12-2011 21:23:45 ~!~Max_debug~!~H: IEQ0114738,00ad95,0109,00000000,21d8b5ac,0c,32,0b0c10,1517
16-12-2011 21:23:45 ~!~Max_info~!~H: Cubedate: 16-12-2011 21:23:00 systemtime: 16-12-2011 21:23:45 Datediff: 0
16-12-2011 21:23:45 ~!~Max_info~!~H: Cube Serial number: IEQ0114738 Cube Address: 44437 Cube Firmware: 0109 Cube Date: 16-12-2011 21:23:00
16-12-2011 21:23:45 ~!~Max_debug~!~M: 00,01,VgIDAQZPZmZpY2UA+vQCB0JlZHJvb20A+14DCEJhY2tyb29tAJ+xBQEA+vRJRVEwMTg0OTEyFVJhZGlhdG9yIFRoZXJtb3N0YXQgMQEBAPteSUVRMDE4NDk2NhVSYWRpYXRvciBUaGVybW9zdGF0IDICAQCfsUlFUTAxODIwNTMVUmFkaWF0b3IgVGhlcm1vc3RhdCAzAwUAShRJRVEwMTQ1MDY5EUVjbyBTd2l0Y2ggb2ZmaWNlAAQAHcFJRVEwMTYwNDY2D1dpbmRvdyBTZW5zb3IgMQIB
16-12-2011 21:23:45 ~!~Max_debug~!~M: 00 01 56020301064F666669636500FAF40207426564726F6F6D00FB5E03084261636B726F6F6D009FB1050100FAF449455130313834393132155261646961746F7220546865726D6F737461742031010100FB5E49455130313834393636155261646961746F7220546865726D6F7374617420320201009FB149455130313832303533155261646961746F7220546865726D6F7374617420330305004A14494551303134353036391145636F20537769746368206F66666963650004001DC1494551303136303436360F57696E646F772053656E736F7220310201
16-12-2011 21:23:45 ~!~Max_info~!~M: #rooms: 3 RoomNumber: 1 RoomName: Office 1stAddressInRoom: 64244
16-12-2011 21:23:45 ~!~Max_info~!~M: #rooms: 3 RoomNumber: 2 RoomName: Bedroom 1stAddressInRoom: 64350
16-12-2011 21:23:45 ~!~Max_info~!~M: #rooms: 3 RoomNumber: 3 RoomName: Backroom 1stAddressInRoom: 40881
16-12-2011 21:23:45 ~!~Max_info~!~M: #Devices: 5 DeviceType: 01 DeviceAddress: 64244 SN: IEQ0184912 DeviceName: Radiator Thermostat 1 DeviceRoom: 1
16-12-2011 21:23:45 ~!~Max_info~!~M: #Devices: 5 DeviceType: 01 DeviceAddress: 64350 SN: IEQ0184966 DeviceName: Radiator Thermostat 2 DeviceRoom: 2
16-12-2011 21:23:45 ~!~Max_info~!~M: #Devices: 5 DeviceType: 01 DeviceAddress: 40881 SN: IEQ0182053 DeviceName: Radiator Thermostat 3 DeviceRoom: 3
16-12-2011 21:23:45 ~!~Max_info~!~M: #Devices: 5 DeviceType: 05 DeviceAddress: 18964 SN: IEQ0145069 DeviceName: Eco Switch office DeviceRoom: 0
16-12-2011 21:23:45 ~!~Max_info~!~M: #Devices: 5 DeviceType: 04 DeviceAddress: 7617 SN: IEQ0160466 DeviceName: Window Sensor 1 DeviceRoom: 2
16-12-2011 21:23:45 ~!~Max_info~!~C1: address: 44437 type: 00 SerialNR: IEQ0114738 C response: ED00AD950009010049455130313134373338010B0004400000000000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B0004400000000000000041FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF687474703A2F2F7777772E6D61782D706F7274616C2E656C762E64653A38302F6375626500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043455400000A000300000E10434553540003000000001C20
16-12-2011 21:23:45 ~!~Max_debug~!~C: C response: ED00AD950009010049455130313134373338010B0004400000000000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B0004400000000000000041FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF687474703A2F2F7777772E6D61782D706F7274616C2E656C762E64653A38302F6375626500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043455400000A000300000E10434553540003000000001C20
16-12-2011 21:23:45 ~!~Max_debug~!~C: C Cube response: CET

[Bastiaan]

Hope you don't mind that I scribble some of the things I find in the script here. My knowledge is pretty limited but I feel comfortable enough to play around the script code a bit...

Did a few tests:
When I deleted the devices again, I got an error: ~!~Error~!~Max Monitor: Conversion from string "29-1-2001 2-1-0001 14:00:00" to type 'Date' is not valid.
I commented out line 247 and then the error went out and it started to create the devices again but got stuck on the: 17-12-2011 10:04:48 - Error - Max Monitor: Index was outside the bounds of the array.
Line 247: Tdate(t) = DateSerial(2000 + (datehex And &h0F),((datehex And &hE000) >> 12)+((datehex And &h80) >> 7),(datehex And &h1F00) >>

My Date system is set to Dutch, so I am using the format with the hyphen as you can see in the logging. That seems the same as you used in the coding.
Enabling line 247 again keeps the error.

The other thought I had was about the out of bounds error: Just saw that you are only using thermostats, while I also got the windows switch and the eco switch.
Unfortunately I see no way to remove them from the cube other than doing a factory reset.....

[blb]

hi Bastiaan,

Yes, I have only the Thermostats, not any of the other devices. I'll do any other control (if required) with other devices and events in Homeseer. I'll have a look if I can improve the script to avoid the errors you did get.

[Bastiaan]

Here is a screengrab fromt the first (and only one) thermostat created. It might help finding the Out of bounds error:

Maxscreen1280.png

Bastiaan

[Bastiaan]

Some further testing:

Deleted the additional eco switch and windows switch, so I got a plain system with Cube + 3 thermostats.
Deleted all devices in HS

Ran the scipt and got the same error. It seems it is already in the reading of the first thermostat but if I look at the end of this log, I can see that (L) Device 2 seems to popup 2 times (looking at the same valve value, then it goes to the next but I guess the array was set for only 3 device and errors out?

===========================================

26-12-2011 12:56:28 Max_info H: Cube Serial number: IEQ0114738 Cube Address: 44437 Cube Firmware: 0109 Cube Date: 26-12-2011 12:56:00
26-12-2011 12:56:28 Max_debug M: 00,01,VgIDAQZPZmZpY2UA+vQCB0JlZHJvb20A+14DCEJhY2tyb29tAJ+xAwEA+vRJRVEwMTg0OTEyFVJhZGlhdG9yIFRoZXJtb3N0YXQgMQEBAPteSUVRMDE4NDk2NhVSYWRpYXRvciBUaGVybW9zdGF0IDICAQCfsUlFUTAxODIwNTMVUmFkaWF0b3IgVGhlcm1vc3RhdCAzAwE=
26-12-2011 12:56:28 Max_debug M: 00 01 56020301064F666669636500FAF40207426564726F6F6D00FB5E03084261636B726F6F6D009FB1030100FAF449455130313834393132155261646961746F7220546865726D6F737461742031010100FB5E49455130313834393636155261646961746F7220546865726D6F7374617420320201009FB149455130313832303533155261646961746F7220546865726D6F7374617420330301
26-12-2011 12:56:28 Max_info M: #rooms: 3 RoomNumber: 1 RoomName: Office 1stAddressInRoom: 64244
26-12-2011 12:56:28 Max_info M: #rooms: 3 RoomNumber: 2 RoomName: Bedroom 1stAddressInRoom: 64350
26-12-2011 12:56:28 Max_info M: #rooms: 3 RoomNumber: 3 RoomName: Backroom 1stAddressInRoom: 40881
26-12-2011 12:56:28 Max_info M: #Devices: 3 DeviceType: 01 DeviceAddress: 64244 SN: IEQ0184912 DeviceName: Radiator Thermostat 1 DeviceRoom: 1
26-12-2011 12:56:28 Max_info M: #Devices: 3 DeviceType: 01 DeviceAddress: 64350 SN: IEQ0184966 DeviceName: Radiator Thermostat 2 DeviceRoom: 2
26-12-2011 12:56:28 Max_info M: #Devices: 3 DeviceType: 01 DeviceAddress: 40881 SN: IEQ0182053 DeviceName: Radiator Thermostat 3 DeviceRoom: 3
26-12-2011 12:56:28 Max_info C1: address: 44437 type: 00 SerialNR: IEQ0114738 C response: ED00AD950009010049455130313134373338010B0004400000000000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B0004400000000000000041FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF687474703A2F2F7777772E6D61782D706F7274616C2E656C762E64653A38302F6375626500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043455400000A000300000E10434553540003000200001C20
26-12-2011 12:56:28 Max_debug C: C response: ED00AD950009010049455130313134373338010B0004400000000000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B0004400000000000000041FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF687474703A2F2F7777772E6D61782D706F7274616C2E656C762E64653A38302F6375626500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043455400000A000300000E10434553540003000200001C20
26-12-2011 12:56:28 Max_debug C: C Cube response: CET CEST
26-12-2011 12:56:28 Max_debug C1: response: ED00AD950009010049455130313134373338010B0004400000000000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B0004400000000000000041FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF687474703A2F2F7777772E6D61782D706F7274616C2E656C762E64653A38302F6375626500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043455400000A000300000E10434553540003000200001C20
26-12-2011 12:56:28 Max_info C2: address: 64350 type: 01 SerialNR: IEQ0184966 C response: D200FB5E010214FF49455130313834393636261E3D09071803300CFF003C604A7240DE40F645114D1A45204520452045204520452045203C604A7240DE40F645114D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A4520452045204520452045204520
26-12-2011 12:56:28 Max_info C2: za 3 (1) 15/08:00 (2) 18,5/09:30 (3) 16/18:30 (4) 16/20:30 (5) 17/22:45 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: zo 3 (1) 15/08:00 (2) 18,5/09:30 (3) 16/18:30 (4) 16/20:30 (5) 17/22:45 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: ma 3 (1) 15/07:30 (2) 18,5/09:00 (3) 16/18:15 (4) 19/20:00 (5) 17/22:50 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: di 3 (1) 15/07:30 (2) 18,5/09:00 (3) 16/18:15 (4) 19/20:00 (5) 17/22:50 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: wo 3 (1) 15/07:30 (2) 18,5/09:00 (3) 16/18:15 (4) 19/20:00 (5) 17/22:50 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: do 3 (1) 15/07:30 (2) 18,5/09:00 (3) 16/18:15 (4) 19/20:00 (5) 17/22:50 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: vr 3 (1) 15/07:30 (2) 18,5/09:00 (3) 16/18:15 (4) 19/20:00 (5) 17/22:50 (6) 19/23:30 (7) 17/00:00
26-12-2011 12:56:28 Max_info C2: ComT: 19 EcoT: 15 MaxT: 30,5 MinT: 4,5 OffT: 0 WinT: 12 WinDur: 03 Boostdur: 1 BoostVal: 80% datetime_decal: za 12:00uValve_Max: 100Valve_off: 0
26-12-2011 12:56:28 Max_debug C2: response: D200FB5E010214FF49455130313834393636261E3D09071803300CFF003C604A7240DE40F645114D1A45204520452045204520452045203C604A7240DE40F645114D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A45204520452045204520452045203C5A4A6C40DB4CF045124D1A4520452045204520452045204520
26-12-2011 12:56:28 Max_info C3: address: 18964 type: 05 SerialNR: IEQ0145069 C response: 11004A140500120F49455130313435303639
26-12-2011 12:56:28 Max_debug C3: unknown device: 05
26-12-2011 12:56:28 Max_debug C3: response: 11004A140500120F49455130313435303639
26-12-2011 12:56:28 Max_info C4: address: 40881 type: 01 SerialNR: IEQ0182053 C response: D2009FB1010314FF4945513031383230353326183D09071803300CFF002849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A29202920292029202920452045204520452045204520
26-12-2011 12:56:28 Max_info C4: za 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: zo 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: ma 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: di 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: wo 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: do 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: vr 3 (1) 10/06:05 (2) 10/22:10 (3) 10/00:00
26-12-2011 12:56:28 Max_info C4: ComT: 19 EcoT: 12 MaxT: 30,5 MinT: 4,5 OffT: 0 WinT: 12 WinDur: 03 Boostdur: 1 BoostVal: 80% datetime_decal: za 12:00uValve_Max: 100Valve_off: 0
26-12-2011 12:56:28 Max_debug C4: response: D2009FB1010314FF4945513031383230353326183D09071803300CFF002849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A292029202920292029204520452045204520452045202849290A29202920292029202920452045204520452045204520
26-12-2011 12:56:28 Max_info C5: address: 64244 type: 01 SerialNR: IEQ0184912 C response: D200FAF4010114FF494551303138343931322A1E3D09071803300CFF003C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D20452045204520452045204520
26-12-2011 12:56:28 Max_info C5: za 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: zo 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: ma 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: di 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: wo 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: do 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: vr 3 (1) 15/06:05 (2) 15/09:00 (3) 15/18:00 (4) 15/23:00 (5) 15/00:00
26-12-2011 12:56:28 Max_info C5: ComT: 21 EcoT: 15 MaxT: 30,5 MinT: 4,5 OffT: 0 WinT: 12 WinDur: 03 Boostdur: 1 BoostVal: 80% datetime_decal: za 12:00uValve_Max: 100Valve_off: 0
26-12-2011 12:56:28 Max_debug C5: response: D200FAF4010114FF494551303138343931322A1E3D09071803300CFF003C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D204520452045204520452045203C493C6C3CD83D143D203D203D20452045204520452045204520
26-12-2011 12:56:28 Max_info C6: address: 7617 type: 04 SerialNR: IEQ0160466 C response: 11001DC10402130F49455130313630343636
26-12-2011 12:56:28 Max_debug C6: unknown device: 04
26-12-2011 12:56:28 Max_debug C6: response: 11001DC10402130F49455130313630343636
26-12-2011 12:56:28 Max_debug L: Device 1: 0B00FB5E0912180020000000
26-12-2011 12:56:28 Max_info L: address: 64350 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 16 date: --
26-12-2011 12:56:28 Max_debug L: Device 2: 06004A140912100B009FB109
26-12-2011 12:56:28 Max_info L: address: 18964 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 11% Temp: 0 date: --
26-12-2011 12:56:28 Max_debug L: Device 3: 121800140078000B00FAF409
26-12-2011 12:56:28 Max_info L: address: 1572884 tvalid: 1 Terror: 1 Tanswer: 0 mode: Auto Valve: 11% Temp: 0 date: --
26-12-2011 12:56:28 Max_debug L: Device 4: 1218241E00AC0006001DC14C
26-12-2011 12:56:28 Max_info L: address: 1582110 tvalid: 0 Terror: 1 Tanswer: 1 mode: Auto Valve: 6% Temp: 0 date: --
26-12-2011 12:56:28 Error Max Monitor: Index was outside the bounds of the array.

[Bastiaan]

One other issue: it seems that 'Floor" and "Room" are switched when creating the devices.