search

Achronite / energenie-ener314rt

Node module for RaspberryPi energenie ener314-rt board, used by node-red-contrib-energenie-ener314rt
MIT License
4 stars 2 forks source link

Add support for SET_REPORTING_INTERVAL for thermostat #40

Closed Achronite closed 4 months ago

Achronite commented 6 months ago

Initial testing of SET_REPORTING_INTERVAL command for the thermostat, provided by energenie support, has led to inconsistent results.

The message only seems to gets processed by the thermostat (i.e. it returns its cached values) when the data is sent in 2 bytes instead of 4 as indicated, but the values bear no correlation to the wait time; it is almost as though it is taking the first byte of the CRC (which happens to be the fourth byte) and using that when I send 0x00, 0x00 as the data. It's sleeping about 3 mins 40 at the moment with 0 sent. If I send anything other that 0 it seems to wait absolutely ages!

e.g (full RMF69 message in decimal, unencrypted with length): 14,4,18,81,255,224,29,132, 210,4,0,0, 0,198,89, causes a response to be sent back from the thermostat; but the command (in hex) was 0xD2,0x04,0x00,0x00 (and not 0xD2,0x04,0x00,0x00,0x00,0x00); I suspect it could be setting the wait to CRC byte-1='198' in this case.

The case is outstanding with energenie support and currently unable to progress.

Achronite commented 6 months ago

Related to https://github.com/Achronite/mqtt-energenie-ener314rt/issues/56

Achronite commented 6 months ago

Blocked, awaiting reply from energenie support

Achronite commented 4 months ago

Still no reply from energenie support... Also I've been trying to capture what is issued when changing the settings on the MiHome app / gateway - I have tried multiple times; and have failed to capture a single change (I can capture all other commands). Methinks that this functionality isn't implemented by energenie either!

Changed to wontfix for now, until this position changes.