steinmn
steinmn
> On a secondary note, according to the analytics from [HA here](https://analytics.home-assistant.io/custom_integrations.json), we have **956 documented installs of zaptec**. Given that analytics is by default tuned off in HA and...
> @steinmn Do we want this in place before the pending 0.8.6 release? I don't think so. It's a lot of small changes which (hopefully) only impacts code quality stuff,...
More specifically, the _insert_statistics function is what we need to learn from: https://github.com/home-assistant/core/blob/dev/homeassistant/components/tibber/coordinator.py#L70
After trying out a test user that only had the User role, it seems like there isn't all that much to block, rather the question is if it is possible...
@sveinse Should we add a "Code Quality" label or something similar to distinguish this type of issue from the enhancements concerning user-facing functionality?
> The function "sub-issue" is also good thing to catch them under one (this?) umbrella. You need at least triage permissions for a repository to add sub-issues, so I don't...
There is a ChargerCurrentUserUuid-state (722) that might be useful, or the [chargehistory](https://docs.zaptec.com/reference/api_chargehistory_get)-api definitely has the information except we don't use that. Considering I've never used my rfid-tags and don't even...
Short answer: This is (most likely) not possible in the current integration, but you can probably achieve the same effect by disabling "Scheduled Charging" and create your own scheduling in...
Also doesn't really make sense to put much effort into this until Zaptec has decided what kind of push functionality to offer for smaller integrators when deprecating the installation/{id}/messagingConnectionDetails-api (ref...
Do you mean disabled as in disabled using entity_registry_enabled_default=False or by setting them as unavailable like we did with Stop/Resume charging? Afaik, we are only able to control entities with...