Christoph Cantillon

I agree that this behaviour is somewhat dubious, but that's how it is documented. I don't think using it should ever potentially affect the parent overrideContext however. > Doing it...

I don't think my patch changes that behavior; it's currently already invoking the getter in the `Object.assign(overrideContext, $event);` line. The only real difference is that instead of reusing and modifying...

I'm not sure assigning in the call expression would result in the expected behavior anyway; I would expect that to set the property on the viewModel, but wouldn't this only...

Is this still intended to be merged into 2.8, or when can we expect this to be available in a general release?

Would it be possible to configure this using HomeAssistant's "schedule" entities? Where I live the eco period lasts all through the weekend, and I'd rather not unnecessarily charge and discharge...

I think I have the same issue. My complications haven't updated in a few weeks now. I think the issue started when I accidentally removed and reinstalled my Home Assistant...

The same quirk also appears to work fine with the NIKO zigbee dimmer: ``` class NikoDimmer(NikoSwitch): """Niko Connected Dimmer 552-722X1.""" model = "Connectable dimmer,3-200W,2-wire" model_friendly = "Connected dimmer" button_count =...

> @ccantill That's neat! I don't have a dimmer here to test though. Would it need anything beyond the code you've added? There might be more dimmer-specific properties. Nothing additional...

Any update on when this is going to be merged?