implemented support for EEP A5:04:01

[thomasletsch]

Hi Johannes, except for the small comment ok. Can you please clarify that so that I can merge it?

R., Thomas

[jo-we]

fixed RANGE_MAX to 250 according to spec.

[maggu2810]

EEP differ between teach-in and data packages. Teach-in packets are handled differently. The packets have a different meaning.

There are profiles, that are using the DB0.7 on data packets: See profile:

• A5-07-02: DB0.7 PIR status
• A5-07-03: DB0.7 PIR status
• A5-11-01: DB0.7 Repeater
• A5-11-02: DB0.7 Alarm
• A5-11-03: DB0.7 Service Mode
• A5-11-04: DB0.7 Service Mode
• A5-12-00: DB0.7...DB0.4 Measurement channel
• A5-12-01: DB0.7...DB0.4 Tarif info
• A5-12-02: DB0.7...DB0.4 Tarif info
• A5-12-03: DB0.7...DB0.4 Tarif info
• A5-13-01: DB0.7...DB0.4 Identifier
• A5-13-02: DB0.7...DB0.4 Identifier
• A5-13-03: DB0.7...DB0.4 Identifier
• A5-13-04: DB0.7...DB0.4 Identifier
• A5-13-05: DB0.7...DB0.4 Identifier
• A5-13-06: DB0.7...DB0.4 Identifier
• A5-13-10: DB0.7...DB0.4 Identifier
• A5-20-12: DB0.7 Fan override
• A5-37-01: DB0.7...DB0.4 DR Level
• A5-38-08: CMD 0x07: DB0.7...DB0.4: Function
• A5-38-09: DB0.7...DB0.4: Function
• A5-3F-00: DB0.7...DB0.4 RSSI Level in dBm

If the profiles you are using do not reuse the data and if the device program logic fill in the sensor data also in teach-in packets, it is ok. But a library have to implement the standard, that should be used by the devices.

And the EEP specification differs between teach-in and data packets and there is no guarantee, how the remaining bits are filled.

If the temperature sensor implementation do not check the teach-in bit, this is a bug and should be fixed!