DynamicGroupController and attributes

[toggledbits]

I need to see device attributes for those devices (from the Entities list -- use Copy Attributes and paste as fenced code block, no screenshots please). Also would be helpful to see the hass_states.json and hass_services.json from the logs directory, but these are larger. If any of you are willing to upload them, let me know and I will provide you a link.

Edit: it looks like HA 2025.11.0 breaks the homeassistant domain commands (turn_on, turn_off). I'm digging more into that, to see if it's a change to their required parameter structure, or just brokeness, but HA does not reply with an error when those services are attempted, and that's usually what happens when parameters/service definition changes.

Edit 2: ...and a little more info. The service data published by the API in 2025.11.0 now omits the target data detail. That's odd. Maybe they are assuming that when target data is empty, just supply an entity? I need to dig through the release notes. But, easy to work around.

[gwp1]

@toggledbits I was able to grab this between meetings lol

dimming.maximum=1
dimming.minimum=0
dimming.step=0.03
light_effect.current=null
light_effect.speed=null
power_switch.state=false
x_hass.domain="light"
x_hass.entity_id="light.master_br_lamp_lamp_2"
x_hass.services=["light","lifx"]
x_hass.source="lifx"
x_hass.state="off"
x_hass_attr.brightness=null
x_hass_attr.color_mode=null
x_hass_attr.effect=null
x_hass_attr.effect_list=["effect_pulse","effect_stop"]
x_hass_attr.friendly_name="Master BR Lamp"
x_hass_attr.supported_color_modes=["brightness"]
x_hass_attr.supported_features=36

[toggledbits]

OK. I'm on this. See my previous post above yours. HA changes the way the definition of some services is published -- there's now no data/detail where there used to be data/detail. I'm not sure if that's an error they'll correct later, or if that's a new way of saying "just use the default behavior" (which in this case is pretty easy to guess). I will have a workaround update published shortly.

FWIW, specifically, from 2025.10.4:

        "homeassistant": {
            "save_persistent_states": {
                "name": "Save persistent states",
                "description": "Saves the persistent states immediately. Maintains the normal periodic saving interval.",
                "fields": {}
            },
            "turn_off": {
                "name": "Generic turn off",
                "description": "Generic action to turn devices off under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },
            "turn_on": {
                "name": "Generic turn on",
                "description": "Generic action to turn devices on under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },
            "toggle": {
                "name": "Generic toggle",
                "description": "Generic action to toggle devices on/off under any domain.",
                "fields": {},
                "target": {
                    "entity": [
                        {}
                    ]
                }
            },

Compare this to 2025.11.0:

        "homeassistant": {
            "save_persistent_states": {
                "fields": {}
            },
            "turn_off": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },
            "turn_on": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },
            "toggle": {
                "fields": {},
                "target": {}    # <--- where did the detail go???
            },

[gwp1]

@toggledbits I've uploaded the two log files to folder HASS 11.0 for you.

[toggledbits]

OK... I found the PR in HA's code and the reasoning behind it. They are trying to make their data/responses more compact (performance reasons). I will have an updated build shortly for this change.

[Pmccraw]

thanks all for the quick action on this issue!

[toggledbits]

OK. Please pull 25310 (aka latest) again. I've patched HassController for this change.

[gwp1]

@toggledbits would this be latest-25310-dc2bb580?

[toggledbits]

@gwp1 yes!

[Crille]

This post is deleted!