OpenWebNet developing..?

[draghip]

Hi @spugna85,

thanks for looking into both issues!

F522 energy counters: I meant handling a counter reset correctly when it occurs, not sending a command from Domoticz to physically reset the device counters.

My preference would be to keep the total in Domoticz cumulative, preserving continuity in the consumption history without negative values or artificial spikes after a reset.

KW4691 setpoints: A global gateway setting would be sufficient for my installation: all four thermostats are KW4691, so I do not need per-thermostat configuration.

An optional dimension 7 mode, keeping the existing method as the default for compatibility with older installations, sounds good.

For completeness, my successful dimension 7 test was in heating/manual mode on zone 6, confirmed by both readback and the physical thermostat display. Cooling and automatic modes remain untested.

Thanks again for your help!

[spugna85]

Hi @draghip,

I’ve opened a pull request with the changes for both issues.

I don’t have KW4691 thermostats or F522 actuators in my installation, so I haven’t been able to test the changes on real hardware. Could you try them on your system and let me know whether both the energy counters and the optional dimension 7 setpoint mode work as expected?

Thanks for your help with testing!

[draghip]

Hi @spugna85,

thanks for implementing both changes!

I’m happy to test them with my F522 actuators and KW4691 thermostats. Could you share the PR link and the recommended way to obtain a test build?

I currently run Domoticz 2025.2, build 16818, using domoticz/domoticz:stable in Docker on a Raspberry Pi with IOTstack. I’d like to back up my installation and keep a way to restore the current version before testing.

I’ll check the F522 energy readings and the optional dimension 7 mode, confirming setpoint changes through both readback and the thermostat display.

Thanks again!