Siemens hood venting level change ignored

[takerukoushirou]

I have a Siemens kitchen hood LC91KLT60 in my Home Connect setup, remote control activated, remote start allowed, and generally properties are also properly reported. I can also power on/off the hood, light and update the configuration.

Except for the venting level. Whenever the venting level (or interval stage for the Interval program) is changed, the value immediately reverts back to the previous value.

The command is successfully received by hcpy, but as can be seen in the log, with the next properties update the value is immediately reverted:

2025-12-16 15:37:26.914219 homeconnect/hood/set received mqtt message [{"uid":55308,"value":"FanStage05"}]
2025-12-16 15:37:26.914639 hood Processing feature Cooking.Common.Option.Hood.VentingLevel with uid 55308
2025-12-16 15:37:27.095678 hood updating {
    "BSH.Common.Setting.RemoteControlLevel": "PermanentRemoteStart",
    "BSH.Common.Status.Favorite.Handling": "AsButtons",
    "resource": "/ro/activeProgram",
    "eNumber": "LC91KLT60/05",
    "brand": "SIEMENS",
    "vib": "LC91KLT60",
    "haVersion": "4.1",
    "swVersion": "5.16.1.5",
    "hwVersion": "1.0.0.1",
    "deviceType": "Hood",
    "BSH.Common.Status.RemoteControlStartAllowed": true,
    "BSH.Common.Status.RemoteControlActive": true,
    "BSH.Common.Setting.PowerState": "On",
    [...redacted...]
    "Cooking.Common.Option.Hood.VentingLevel": "FanStage01"
}

If I change the setting inside the Home Connect app, the venting level can be freely adjusted. hcpy reports in that case program and venting level changes (and no other property changes).

Is this a known limitation or is there possibly another issue causing this behaviour? Anything else I could test to help investigate?

Running the hcpy 0.4.6 add-on under Home Assistant.

[Meatballs1]

I believe you have to start a new program with the venting level as an option, rather than setting the value. I do have a hood and noticed similar so I might give it a try later

[takerukoushirou]

Thanks for the quick reply @Meatballs1. I tried a few things, but it seems that both the activeProgram and selectedProgram are read-only for some reason:

action: mqtt.publish
data:
  topic: "homeconnect/hood/activeProgram"
  payload: '[{"program":55307, "options":[{ "uid":55308, "value":"FanStage03" }]}]'

Log output:

2025-12-16 16:25:22.047306 homeconnect/hood/activeProgram received mqtt message [{"program":55307, "options":[{ "uid":55308, "value":"FanStage03" }]}]
2025-12-16 16:25:22.273296 hood {'error': 400, 'resource': '/ro/activeProgram'}

Any ideas on this are very welcome.

[Meatballs1]

The following works for me:

action: mqtt.publish
data:
  topic: "homeconnect/hood/activeProgram"
  payload: '{"program":"Cooking.Common.Program.Hood.Venting","options":[{"uid":55308,"value":3}]}'

You can use the Cooking.Common.Program.Hood.Venting or 55307 for the program. I dont think I am processing the options UID/Values from display names back to values though in the activeProgram, but I think I did have it being processed when selecting specific options. It may be worthwhile making these values like Cooking.Common.Option.Hood.VentingLevel as readonly sensors in discovery.yaml but they are displaying as readWrite in my devices.json

[takerukoushirou]

Sadly doesn't seem to work in my case, same error (I just powered the hood on, which defaults to program Venting with venting level 2, and then published the message):

2025-12-16 22:36:49.696242 homeconnect/hood/activeProgram received mqtt message {"program":"Cooking.Common.Program.Hood.Venting","options":[{"uid":55308,"value":3}]}
2025-12-16 22:36:49.780732 hood {'error': 400, 'resource': '/ro/activeProgram'}

Anything else I could check?

The VentingLevel feature itself also appears as readWrite in my devices.json:

            "55308": {
                "name": "Cooking.Common.Option.Hood.VentingLevel",
                "access": "readWrite",
                "available": "true",
                "refCID": "03",
                "refDID": "80",
                "values": {
                    "0": "FanOff",
                    "1": "FanStage01",
                    "2": "FanStage02",
                    "3": "FanStage03",
                    "4": "FanStage04",
                    "5": "FanStage05"
                }
            },

Not sure whether it gives any extra insight, the ActiveProgram feature is listed without any additional attributes in the devices.json:

            "256": {
                "name": "BSH.Common.Root.ActiveProgram"
            },

[Meatballs1]

Just checking you aren't using the physical controls as my hood puts a 15s lockout on remote commands after a physical button is pushed?

The Java proxy should allow mitm and see the proper communication between mobile phone and device so you can work out exactly how the mobile app works? https://github.com/bruestel/homeconnect-appliance-proxy

[takerukoushirou]

I used the remote power control to activate the hood and then sent the manual MQTT message—no physical controls were used.

Will have a look at the MITM proxy and report back (might take a bit to find the time).
Thank you for the help and feedback so far!