-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No configuration for expire_after #159
Comments
This feature will be available in the upcoming version of the library. Please refer to the linked Pull Request for more information. |
As there were no more modifications I had to Fork the library, I added expire_after and state_class; but the most important thing was changing the mqtt connection. |
@PM04290 the new features are already available on the develop branch. Feel free to try them.
Could you please provide additional details? I'm unsure about what you're referring to. |
Some times, for example for push button or else, it would be interesting to set expire_after parameter on mqtt configuration, for sensor and binary_sensor; as it is possible to do in the configuration of zigbee2mqtt, for example: https://www.zigbee2mqtt.io/guide/configuration/devices-groups.html
real case example :
push button who send pressed time : 350ms, 1500ms, 5200ms, etc...
actually if i want to do the same function i must send a 0 (zero) value after few millisecond, so expire_after in HA save this action and is better for mqtt bandwidth :)
The text was updated successfully, but these errors were encountered: