Feedback of Light and Covers slow

[dominikfrey]

It looks like the feedback for covers and lights is going over the API and not MQTT (Eventhough it looks like the MQTT feedback for covers is implemented in the release 0.4.2). This makes the feedback pretty slow and thus automation scripts are not very usable.

It would be great if all services would run over MQTT to get immediate feedback.

Not sure though if it is a Dingz issue or an issue that could be addressed in this library.

[altery]

I noticed the same. I do see the MQTT messages immediately in the broker after state changes of Dingz, but HA still takes much longer to update, for example light state or power consumption. It even doesn't show the exact same values for sensor values that are sent using MQTT, so I suspect the values are fetched using API polling. Note that the MQTT sensor shows 'connected'. I also tried to disable polling in the integration, but that didn't change anything.

Edit: I quickly checked the code of this integration, and it looks that various entities are not updated using MQTT, for example

dingz//dz1f-pir/state/light/
or
dingz//dz1f-pir/power/light/

Would be great if that could be extended!

Also, the integration reports the IoT class local_polling in the manifest (not local_push). Not sure if that changes anything at runtime, though.

[siku2]

The manifest specifies 'local_polling' because polling is the default behavior of the integration and I expect most users don't have an MQTT broker set up. This doesn't have any influence on the runtime though.

The MQTT connection isn't set up for lights and covers because I experienced some inconsistencies with them and didn't personally need the data in real-time.

Adding support for it is very straight-forward though. I will pick it up the next time I have a personal need to work on the project. Unless, of course, someone else PR's it first ;)