Franck Nijhof
Franck Nijhof
@Gamester17 Depends on the definition. For 1.0 is has been determined that we won't be splitting the core integrations. 1.0 would be about the stability of the internal APIs of...
Aren't those not just sensors? Things like brushes and current cleaning method? Changing/resetting them can be provided via services.
Closing PR as the parent PR has been closed.
New parent PR
I'm sorry, I have to agree with @pvizeli, @OnFreund. While a separation of states/config would help in maintaining a configuration in a version control system, it is still not meant...
If the goal is just history tracking, that is technically already possible. But sure, splitting that would make it better. So that leaves us with the sole reasons to do...
You don't have to repeat yourself on every response. I was just giving my opinion on the matter. I don't underestimate the forums, we have some fine stats now based...
So isn't the thing you are looking for: Audit logging?
I cannot find the public repository providing this custom integration, could you point me to it?
> The integration is not yet published. I cannot review or approve this PR without a actual integration 🤷