ELV MAX! protocol description

Forum about the home automation suites by ELV etc

Moderator: jrkalf

Re: ELV MAX! protocol description

Postby mike7 » Tue Nov 11, 2014 5:54 am

Error323 wrote:For my attempt in home automation I want to bypass the cube completely and control the valves directly via a 868 MHz transceiver. Does anybody here know the internal protocol between cube and valve components? I can't seem to find it anywhere, is it FHT based or completely different?

you can start here domoticaforum.eu/viewtopic.php?f=66& ... mp;start=0
mike7
Member
Member
 
Posts: 69
Joined: December 2013

Re: ELV MAX! protocol description

Postby Error323 » Tue Nov 11, 2014 9:31 am

Excellent! Thank you!
Error323
Starting Member
Starting Member
 
Posts: 5
Joined: November 2014

Re: ELV MAX! protocol description

Postby Massi » Tue Nov 11, 2014 9:47 am

i really can't see the advantage of bypassing the cube (except the €30 not spent, obviously :D).. could you please explain me?
Massi
Member
Member
 
Posts: 51
Joined: November 2013

Re: ELV MAX! protocol description

Postby mactoolz » Fri Dec 05, 2014 8:40 pm

Hi,

this is my first post and came across this very interesting topic.
Has anyone tried the protocol on Ethernet socket base with a wago controller 750-880 implemented.

MacToolz
mactoolz
Starting Member
Starting Member
 
Posts: 8
Joined: December 2014

Re: ELV MAX! protocol description

Postby philjung77 » Sat Dec 27, 2014 4:32 pm

Hello,

Regarding wall thermostat (device type = 3), the L message contains 12 bytes. Length is 12 (of course :-) ) and last byte represents the real temperature x 10.

0xaf => 175 => 17,5 degrees

Philippe
philjung77
Starting Member
Starting Member
 
Posts: 1
Joined: December 2014

Re: ELV MAX! protocol description

Postby pbrand » Sun Dec 28, 2014 2:29 pm

philjung77 wrote:Hello,

Regarding wall thermostat (device type = 3), the L message contains 12 bytes. Length is 12 (of course :-) ) and last byte represents the real temperature x 10.

0xaf => 175 => 17,5 degrees

Philippe


Don't know if you have a new type wall thermostat Philippe, but my wall thermostat L message is 7 bytes long whereas the actual temperature is represented by the MSB bit of the third byte together with the seventh byte ( x 10).

Regards,
Peter
pbrand
Member
Member
 
Posts: 100
Joined: October 2008
Location: Netherlands

Re: ELV MAX! protocol description

Postby Massi » Sun Dec 28, 2014 6:20 pm

pbrand wrote:
philjung77 wrote:Hello,

Regarding wall thermostat (device type = 3), the L message contains 12 bytes. Length is 12 (of course :-) ) and last byte represents the real temperature x 10.

0xaf => 175 => 17,5 degrees

Philippe


Don't know if you have a new type wall thermostat Philippe, but my wall thermostat L message is 7 bytes long whereas the actual temperature is represented by the MSB bit of the third byte together with the seventh byte ( x 10).

Regards,
Peter


12th byte is actual temp*10, so theres a limit: 25,5 degrees. if it's higher, the count starts from 0 again and the first bit of byte 8 (set temp) is set to one

This is the standard wall thermostat.
I don't believe your response can be simply 7 bytes, as always it will be 6 bytes for ecoswitch, 11 for radiator thermostat and 12 for wall thermostat.

Maybe you are not counting starting bytes :)
1) data lenght
2,3,4) rf address
5) unknown

So then there are 7 bytes :)
Massi
Member
Member
 
Posts: 51
Joined: November 2013

Re: ELV MAX! protocol description

Postby pbrand » Sun Dec 28, 2014 7:06 pm

Oh silly me. You are quite right, Massi. I only looked at the specific device bytes and forgot about the generic part :)
pbrand
Member
Member
 
Posts: 100
Joined: October 2008
Location: Netherlands

Re: ELV MAX! protocol description

Postby Massi » Mon Dec 29, 2014 5:17 pm

pbrand wrote:Oh silly me. You are quite right, Massi. I only looked at the specific device bytes and forgot about the generic part :)


No, you'll not get excused.
For that, you need to add to you blog the protocol description of the s: command :)
Massi
Member
Member
 
Posts: 51
Joined: November 2013

Re: ELV MAX! protocol description

Postby mactoolz » Mon Dec 29, 2014 11:43 pm

Hi,

it may be that in the new firmware 1.4.1, the commands have changed in their byte protocol?

Thanks

MacToolz
mactoolz
Starting Member
Starting Member
 
Posts: 8
Joined: December 2014

Re: ELV MAX! protocol description

Postby Massi » Wed Dec 31, 2014 12:17 am

mactoolz wrote:Hi,

it may be that in the new firmware 1.4.1, the commands have changed in their byte protocol?

Thanks

MacToolz


my "simple" commands (manual temp set) still work. What commands are you referring to?
Massi
Member
Member
 
Posts: 51
Joined: November 2013

Re: ELV MAX! protocol description

Postby mactoolz » Wed Dec 31, 2014 9:36 am

Hi,

i want to use all the commands. At least M / H / C / L and also the sending of data.
e.g. the byte arrangement of the M command I am missing some information. Rather, I do not know what type specific bytes of information again.
e.g. I have not in my receiving data, the RF address.
Look Please purely in the excel. Since I have the Empfangsdasten divided times.
You may find, for example, the RF address.


Thanks

MacToolz
Attachments
M-Command XLS.xlsx
M-Command list recorded from wireshark
(18.77 KiB) Downloaded 159 times
mactoolz
Starting Member
Starting Member
 
Posts: 8
Joined: December 2014

Re: ELV MAX! protocol description

Postby pbrand » Wed Dec 31, 2014 1:06 pm

I am running 1.4.1 firmware here and have seen no changes in the M / H / C / L messages.
pbrand
Member
Member
 
Posts: 100
Joined: October 2008
Location: Netherlands

Re: ELV MAX! protocol description

Postby Massi » Fri Jan 02, 2015 2:12 pm

pbrand wrote:I am running 1.4.1 firmware here and have seen no changes in the M / H / C / L messages.


Full quote.
No changes in last firmware
Massi
Member
Member
 
Posts: 51
Joined: November 2013

Re: ELV MAX! protocol description

Postby mactoolz » Fri Jan 02, 2015 3:26 pm

Hi,

have you looked at the excel. This is an excerpt from the M command. I see no RF address here. The first topic is described which can be seen in the M-command for a device address.
I do not see them unfortunately. Can you tell me the individual bytes?

Code: Select all
Result JEQ0416392    --> 21('21')    3('3')    1('1')    210('Ò')    240('ð')    74('J')    69('E')    81('Q')    48('0')    49('1')    54('6')    51('3')    57('9')    50('2')   
Result AZ_WandThermo -->    48('0')    13('CR')    65('A')    90('Z')    95('_')    87('W')    97('a')    110('n')    100('d')    84('T')    104('h')    101('e')    114('r')    109('m')    111('o')


Thanks


MacToolz
mactoolz
Starting Member
Starting Member
 
Posts: 8
Joined: December 2014

PreviousNext

Return to Homematic, FS20, FHT, ESA and ELV

Who is online

Users browsing this forum: No registered users and 1 guest