ELV MAX! protocol description
Moderator: jrkalf
Re: ELV MAX! protocol description
S-command, setting weekly programm:
s:AAQQAAAAAJPRBQJYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQNYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQRYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQVYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQZYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQBYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQFYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQJYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQNYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQRYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQVYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQZYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQBYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQFYTlxeSNJQ8Fj8XxRZIA==\r\n
this are 2 times setting the weekly-programm (same thermostat, all day same programm, changed from first to second one temperature). decoding follows...
s:AAQQAAAAAJPRBQJYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQNYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQRYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQVYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQZYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQBYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQFYTl5eSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQJYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQNYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQRYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQVYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQZYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQBYTlxeSNJQ8Fj8XxRZIA==\r\n
s:AAQQAAAAAJPRBQFYTlxeSNJQ8Fj8XxRZIA==\r\n
this are 2 times setting the weekly-programm (same thermostat, all day same programm, changed from first to second one temperature). decoding follows...
Max! 1 x Cube, 4 x Thermostat, 1 x Wandthermostat,1 x Fensterkontakt
Re: ELV MAX! protocol description
Could this be the weekly program you used? (based on first set of 7 s-commands)
22 till 06:30
23.5 till 07:50
18 till 17:30
20 till 20:00
22 till 21:00
23.5 till 23:00
22 till 24:00
22 till 06:30
23.5 till 07:50
18 till 17:30
20 till 20:00
22 till 21:00
23.5 till 23:00
22 till 24:00
Re: ELV MAX! protocol description
Yes 

Max! 1 x Cube, 4 x Thermostat, 1 x Wandthermostat,1 x Fensterkontakt
Re: ELV MAX! protocol description
OK
This means the switchpoints look similar as how they are received, which is already documented.
Encoding a switchpoint to a word (2 bytes) is the reverse function...
Also see http://blog.hekkers.net/2011/09/11/elv- ... y-program/
Add a few bytes (RF addres, DOW indicator etcetera) and you're done

This means the switchpoints look similar as how they are received, which is already documented.
Encoding a switchpoint to a word (2 bytes) is the reverse function...
Also see http://blog.hekkers.net/2011/09/11/elv- ... y-program/
Add a few bytes (RF addres, DOW indicator etcetera) and you're done

Re: ELV MAX! protocol description
s-command:
- setting to 'auto' accepts (needs?) temperature (used then until next step in auto-programm).
- the above samples have an error: until date+time are 3 bytes, but the samples with and without date+time are different length with 2 bytes.
- setting a boost is possible (mode 11)
- setting to 'auto' accepts (needs?) temperature (used then until next step in auto-programm).
- the above samples have an error: until date+time are 3 bytes, but the samples with and without date+time are different length with 2 bytes.
- setting a boost is possible (mode 11)
Max! 1 x Cube, 4 x Thermostat, 1 x Wandthermostat,1 x Fensterkontakt
Re: ELV MAX! protocol description
about the L: response: It looks like some yet unknown data is provided in auto mode. In auto mode there should be no relevant date & Time information in the response, but the last 'date byte' is giving some info (C9, BE, ED etc. in responses below). I don't know what it is, but maybe it is an indication of the current temperature, maybe an offset between temperature setting and the current temperature...
I have now 8 Thermostats active, see recent debug output of my HS script below:
I have now 8 Thermostats active, see recent debug output of my HS script below:
Code: Select all
L: address: 39685 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 17 date: --
L: Device 8: 0B009B05091218002200C900
L: address: 70849 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 17 date: --
L: Device 7: 0B0114C1091218002200BE00
L: address: 13815 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 17 date: --
L: Device 6: 0B0035F7091218002200ED00
L: address: 14871 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 17 date: --
L: Device 5: 0B003A17091218002200E200
L: address: 14259 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 56% Temp: 17 date: --
L: Device 4: 0B0037B3091218382200B800
L: address: 13838 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 40% Temp: 15 date: --
L: Device 3: 0B00360E091218281E009800
L: address: 13789 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 16% Temp: 17 date: --
L: Device 2: 0B0035DD091218102200CD00
L: address: 13937 tvalid: 1 Terror: 0 Tanswer: 0 mode: Auto Valve: 0% Temp: 17 date: --
L: Device 1: 0B003671091218002200DB00
Bernard
Re: ELV MAX! protocol description
My wall-thermostat has arrived.
- L-response is 1 byte longer
- Devicetype is 3
- LiveReadLength is the correct 1 byte more value.
- the other data from L-response is the same as in the thermostate.
- L-response is 1 byte longer
- Devicetype is 3
- LiveReadLength is the correct 1 byte more value.
- the other data from L-response is the same as in the thermostate.
Max! 1 x Cube, 4 x Thermostat, 1 x Wandthermostat,1 x Fensterkontakt
Re: ELV MAX! protocol description
C-Command:
Response: C
RFAddress: 0x009E7C
DeviceType: 0x01,Thermostat
RoomID: 0x04 <----- Byte on Postion 5 is RoomID 4
?: 0x14FF
SNR: IEQ0181616
ComfortTemp: 0x2A,21.0
EcoTemp: 0x22,17.0
Response: C
RFAddress: 0x009E7C
DeviceType: 0x01,Thermostat
RoomID: 0x04 <----- Byte on Postion 5 is RoomID 4
?: 0x14FF
SNR: IEQ0181616
ComfortTemp: 0x2A,21.0
EcoTemp: 0x22,17.0
Re: ELV MAX! protocol description
Can anyone post a detailed description and correct examples about the S Command pls.
7x Thermostat / 1x WindowContact / 1x Max! Cube
Re: ELV MAX! protocol description
most info about the s: command is in the opening topic. Some examples are:
see also the Homeseer vb script I use to send (s:)commands to the Thermostats.
domoticaforum.eu/viewtopic.php?f=47& ... 850#p51917
Code: Select all
s:AARAAAAAADXdAoqBiwA=\r\n decoded: 0004400000000035DD028A818B00 command: M05gr01-9u00:00
s:AARAAAAAADoXAQA=\r\n decoded: 000440000000003A170100 command: auto week
s:AARAAAAAADoXAVc=\r\n decoded: 000440000000003A170157 command: M11,5gr
domoticaforum.eu/viewtopic.php?f=47& ... 850#p51917
Bernard
Re: ELV MAX! protocol description
Hello,
I also bought the MAX system (3 thermostats and an Cube).
I want to write my own program, but when I connect to the cube I get an H,M,C(couple) and een L response.
But then it stops sending data, even when I change the setpoint manually.
Do I need to send someting to get the new data?
thanks,
Peter
I also bought the MAX system (3 thermostats and an Cube).
I want to write my own program, but when I connect to the cube I get an H,M,C(couple) and een L response.
But then it stops sending data, even when I change the setpoint manually.
Do I need to send someting to get the new data?
thanks,
Peter
Re: ELV MAX! protocol description
Sending l:+CR+LF to the Cube will give you the data you want.
Re: ELV MAX! protocol description
ok, thanks.
Re: ELV MAX! protocol description
Does anyone know how to set the next parameters:
- ECO and COMFORT temperature
- Temperature offset
- Valve offset
- Boost valve value
- Boost duration
- Window open temp
Most of them can be set by the MAX program, so it must be posible to change them.
Thanks ,
Peter Wolbers
- ECO and COMFORT temperature
- Temperature offset
- Valve offset
- Boost valve value
- Boost duration
- Window open temp
Most of them can be set by the MAX program, so it must be posible to change them.
Thanks ,
Peter Wolbers
Re: ELV MAX! protocol description
Hi Peter,
You can set the temperature with the s: command, see the opening post. You can have a look at my Homeseer script for more info: domoticaforum.eu/viewtopic.php?f=47& ... mp;start=0
Because it should not be necessary to change the other settings very often, I have not spend time in setting these values. If I need to changes these settings or the week schedule, I do so via the MAX! application.
You can set the temperature with the s: command, see the opening post. You can have a look at my Homeseer script for more info: domoticaforum.eu/viewtopic.php?f=47& ... mp;start=0
Because it should not be necessary to change the other settings very often, I have not spend time in setting these values. If I need to changes these settings or the week schedule, I do so via the MAX! application.
Bernard