Implement checking of registers being enabled before using them

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[jipem01]

Hello Vincent,

I'm afraid that the approach of systematic check if enable register is set could be a bit dangerous. I've idebtified at least one register on Nobis stove where enable register is at 0 but the functionnalitie is present for nobis stove (wood_real_power). With my previous pr, if we have a doubt on the usage of enable register (wich is not clear yet following our exchanges...) we can just indicate no enable_register name and then we just ignore the "enable register check". I think you should add a way to activate or deactivate the enable register check for each entity declaration.

[vincentwolsink]

Hi, yes you mentioned that in your PR. We can always add an ‘force_enable’ flag to the entities description if needed. But maybe that specific register will go to 1 when you burned wood once. Since the naming of the enable registers is standardized the need to specify them manually only adds complexity, and the way I did it I can also use the check in other places like inside the climate code. With the current sensors the override flag was not needed yet, so I didn’t add it yet. Prefer to keep the code lean if possible 🙂

[jipem01]

I think the flag is at 0 when burning pellet and 0 when burning wood (hybrid stove).But still too hot to test!The real wood power register is still displaying the last wood power (3)I agree to keep the code as lean as possible!