search

Achronite / node-red-contrib-energenie-ener314rt

Node Red nodes for Energenie ENER314-RT Raspberry Pi board
MIT License
12 stars 3 forks source link

MIHO013 eTRV: VALVE_STATE #65

Closed genestealer closed 1 year ago

genestealer commented 1 year ago

I cannot see when/which commands are needed to make the MIHO013 eTRV will return the "VALVE_STATE", can you please confirm?

Achronite commented 1 year ago

Yeah, as far as I know it is never returned by the eTRV. You can find out what is sent back (and when) here: https://github.com/Achronite/node-red-contrib-energenie-ener314rt#etrv-monitor-messages

genestealer commented 1 year ago

That is really frustrating, so we need to assume "VALVE_STATE" is as we last set, no way to check it. We may be able to infer though, as I 'think' the 5 mins returned data of a "closed/open" valve is different to a valve set to "auto". Will need to check.

Achronite commented 1 year ago

@genestealer Did you get any further with this? In mqtt-energenie-ener314rt I optimistically update the state topic based on command after receipt.

I noticed you also have the MiHome gateway - are you seeing anything being sent/returned to the eTRV (in debug logs) that I have not documented?

genestealer commented 1 year ago

Hi @Achronite , I'm no longer using the MiHome gateway, it's completely unplugged.

Regarding state optimism, I am trying the approach of not retaining the values sent via MQTT, but allowing Home Assistant to "remember" what was last sent (E.G. see REPORTING_INTERVAL below)

image

eTRV after setting interval image

eTRV with interval never set. image

Achronite commented 1 year ago

I have checked again with energenie, here is their response:

Hi Achronite,

The eTRV does not provide a confirmation of receipt for target temperatures or valve state. The valve state when set up will be normal operation and as each valve type will have a slight difference in stem length, the valve does not full open or close unless a specific command is sent, or if there is a large enough difference between the target temperature and the current temperature.

So I'm going to close this as it cannot be done.

genestealer commented 1 year ago

Thank you for reaching out to their support to confirm this. It's good to know that they are still actively responding to technical queries. It would be also really interested to know if there was some sort of special command that we could send that would increase the polling rate to something less than 5 minutes or is that a question that's already been asked? I was waiting 5 minutes for it to respond can be quite frustrating when doing debugging.

Achronite commented 1 year ago

I think I got the 5 minutes from the energenie docs as the minimum wait. SET_REPORTING_PERIOD is the command that changes this; you could try using it to change the wakeup period to less than 300 and see what happens?

From docs: To save power and extend battery life, the eTRV communicates with the Gateway once every 5 minutes.  It will not begin to respond to a command for those 5 minutes.  Once it has received the command, the eTRV will slowly make adjustments to the radiator valve to adjust to the new target temperature.  Wait 30 minutes to confirm whether the new target temperature has been received.