Dimming

[avworldme]

I am able to pull all my lights from the C4 controller (running version 3.3.0). However the lights are all pulling in as switches with no dimming options. Although under info I am seeing this. What am I doing wrong?

MINUTES ON
68,413
MINUTES OFF
1,857,867
MINUTES ON TODAY
0
CURRENT POWER
0
ENERGY USED
22,596
ENERGY USED TODAY
0
WATTS
100
MODULE OVERRIDE LEVEL
100
Navigator Dynamic Capabilities
DynamicCapabilities:
dimmer: true
supports_target: false
supports_color: false
supports_color_correlated_temperature: false
color_correlated_temperature_min: 1000
color_correlated_temperature_max: 20000
color_rate_behavior: 1
color_rate_min: 0
color_rate_max: 0
has_extras: false
click_rate_min: 250
click_rate_max: 86400000
hold_rate_min: 1000
hold_rate_max: 86400000
LIGHT STATE
0
Brightness Presets
Brightness Active Presets
light_brightness_active_presets:
preset:

• name: 'Off'
  id: 2
• name: Slow Off
  id: 4
  Brightness Percent
  0
  PRESET LEVEL
  100
  Item ID
  353
  Parent item ID
  352

[avworldme]

I think this is a solution: After the initial install, I turned the light on / off and the brightness slide showed up.

[mlbfamily]

The above works (turning on / off) to get the dimming feature to appear. However, every time you restart HA, you have to do this for every light, otherwise any automation or integration that relies on dimming just breaks. Most notably for me, the HomeKit bridge. Would be cool if the integration realized they were dimmers upon initialization without requiring this.

[xmaxzzz]

no solution found? its rgbw problem too - only on/off

[Xesyliad]

This appears to be ongoing still, same issue.

[mellis]

Do the entities have a LIGHT_LEVEL property? That is how it currently determines whether or not it is a dimmer. Perhaps the entity properties changed in 3.3, my dimmers work correctly but my system is on 3.2 still.

[Xesyliad]

No, from diagnostics these are all the supported entity features. The one that stands out is the "Brightness Percent"

This is one entity, there's 15 more just like it, all the same and no reporting a dimmer functionality until the light is initially switched on, then the dimmer becomes available, which breaks other integrations that depend on the dimmer capabilities being reported at startup, not at entity activation.

      "2787106070": {
        "aid": 2787106070,
        "config": {
          "manufacturer": "Control4",
          "model": "Panel-Dimmable",
          "platform": "control4"
        },
        "category": 5,
        "name": "Lights",
        "entity_id": "light.lights_10",
        "entity_state": {
          "entity_id": "light.lights_10",
          "state": "off",
          "attributes": {
            "supported_color_modes": [
              "onoff"
            ],
            "MINUTES_ON": 105540,
            "MINUTES_OFF": 971451,
            "MINUTES_ON_TODAY": 0,
            "CURRENT_POWER": 0,
            "ENERGY_USED": 16506,
            "ENERGY_USED_TODAY": 0,
            "WATTS": 26,
            "MODULE_OVERRIDE_LEVEL": 100,
            "Navigator Dynamic Capabilities": {
              "DynamicCapabilities": {
                "dimmer": true,
                "supports_target": false,
                "supports_brightness_stop": false,
                "supports_color": false,
                "supports_color_correlated_temperature": false,
                "supports_color_stop": false,
                "brightness_rate_min": 250,
                "brightness_rate_max": 86400000,
                "color_correlated_temperature_min": 1000,
                "color_correlated_temperature_max": 20000,
                "color_rate_behavior": 1,
                "color_rate_min": 0,
                "color_rate_max": 86400000,
                "has_extras": false,
                "click_rate_min": 250,
                "click_rate_max": 86400000,
                "hold_rate_min": 1000,
                "hold_rate_max": 86400000
              }
            },
            "LIGHT_STATE": 0,
            "Brightness Presets": "",
            "Brightness Active Presets": {
              "light_brightness_active_presets": {
                "preset": {
                  "name": "Off",
                  "id": 2
                }
              }
            },
            "Brightness Percent": 0,
            "PRESET_LEVEL": 40,
            "item id": 220,
            "parent item id": 219,
            "friendly_name": "Lights",
            "supported_features": 0
          },
          "last_changed": "2023-08-08T04:46:08.267144+00:00",
          "last_updated": "2023-08-08T04:46:08.267144+00:00",
          "context": {
            "id": "01H79QEWWBQMXP8B768YYB486X",
            "parent_id": null,
            "user_id": null
          }
        }
      },

[mellis]

Do they work correctly in the core version of the integration? It looks like this bug was probably fixed there home-assistant/core#95196

[Xesyliad]

Unfortunately I'm not in a position right now to test this until next week. Perhaps others out there are?