Aaron Bach

@shbatm Looks great! I don't have a flow meter, so I can't directly test this – have you confirmed?

We used to do this (mark sensors as `unavailable` if their underlying data didn't exist), but we switched to an `unknown` state instead because of https://github.com/bachya/ecowitt2mqtt/issues/293 (CC: @Anto79-ops). I suppose...

Thanks for the info, @FSeidinger. A couple of thoughts: 1. If you specify an MQTT topic and _don't_ enable Home Assistant MQTT Discovery, you'll get a payload that looks like...

The Docker image fails to build because piwheels.org doesn't have a `cryptography` wheel for this version yet (needed for speedy ARM builds). We're not in a rush; going to mark...

@alesoft73 @MaxCere We just released version 0.3.0 of `python-eufy-security` that should address international addresses dynamically; could you help us test?

I'm not sure this PR is useful (especially re: your comment about "at least some SoyeaLink devices"). What about using [supported brands](https://developers.home-assistant.io/docs/creating_integration_manifest?_highlight=brands#supported-brands) in the manifest?

Please set debug-level logs for `home assistant.components.lametric` and `demetriek`, run the service again, and post any relevant logs.

Check out these docs: https://www.home-assistant.io/integrations/logger/

Quick suggestion: instead of `homeassistant.components.demetriek`, just use `demetriek` (since that's the name of the library).

Thanks for checking for me, @Anto79-ops. FWIW, I just spun up a fresh HASS and connected my LaMetric Time to it. All of these service calls: ```yaml service: notify.lametric_time data:...