cooling_status_onoff unexpected behavior

[balerion]

cooling_status_onoff seems to not follow the expected behavior: it sets the setpoint temperature to either 24 (on) or 19 (off) on my system.

Is this a problem on my end?

[wrongisthenewright]

Hi, Which HP? In my case (Nimbus 70M) the command is correctly applied by the system. Pay attention to disable heating before enabling cooling and vice versa.

[balerion]

Hi, I have an Ariston One hybrid system connected to a Sensys thermostat. I tried with the disabled heating, and I still get the same unexpected behavior. I don't think this boiler is meant for any cooling option to be integrated, perhaps it strangely interprets the command differently?

[wrongisthenewright]

I have a system very similar to your and my CSV works correctly. It may be a HA related problem. try to issue a direct command with ebusd to write the status:

ebusctl write -c energymgr cooling_status on

if you use docker then the command should be

docker exec -ti CONTAINERNAME ebusctl write -c energymgr cooling_status on

[balerion]

Thanks for looking into this. I just tried what you suggested, and get the same result if i use ebusd directly or using the mqtt messages. It is not a problem for me, i just thought the problem could have implications for other commands that might be interpreted in unexpected ways on other systems.

[wrongisthenewright]

EDIT: sorry it doesn't work as I wrote before, I'm using broadcasted messages for cooling_status so the command to read it manually is different and you can use the hex feature.

Having a really similar system (may be the same one) I think it should work. Can you check and see what happens if you activate the cooling manually using the remote controller (Sensys in Ariston brand)?

You should then issue these commands to read the value:

ebusctl hex 182000020f23

if you use docker then the command should be

docker exec -ti CONTAINERNAME ebusctl hex 182000020f23

then report back what you'll find. You should receive a result like this:

020100 if the cooling is OFF (02=2 hex bite answer, 01=1 value reported, 00=OFF) 020101 if the cooling is ON (02=2 hex bite answer, 01=1 value reported, 01=ON)

[wrongisthenewright]

please post also the result of this command that lists all the occurrence of messages containinf the 0f23 PBSB

ebusctl grab result all | grep 0f23

[balerion]

So, when running ebusctl hex 182000020f23 i get ERR: read timeout and, when running ebusctl grab result all | grep 0f23, I get

70fe2000080f23102307810782 = 1
37fe200f100f230000102300000781000007820000 = 1
37fe20200b6276be00637696000f2300 = 24
31fe2020030f2300 = 62: energymgr cooling_status

[wrongisthenewright]

So, when running ebusctl hex 182000020f23 i get ERR: read timeout and, when running ebusctl grab result all | grep 0f23, I get

70fe2000080f23102307810782 = 1
37fe200f100f230000102300000781000007820000 = 1
37fe20200b6276be00637696000f2300 = 24
31fe2020030f2300 = 62: energymgr cooling_status

Can you share the ebusctl info command output?

[wrongisthenewright]

And, if you can also an

ebusctl grab result all