Krzysztof Białek

I'm using self-hosted vaultwarden. Can this be the reason? EDIT Problem solved by setting the environment as follows. All urls must be set one-by-one ``` ❯ goldwarden config get-environment {"api":"https://vault.xyz/api","identity":"https://vault.xyz/identity","notifications":"https://vault.xyz/notifications","vault":"https://vault.xyz"}...

This behavior comes out from a logger firmware limitation, which does not support a concept of client sessions. In other words, it is designed to handle communication from a single...

Does setting time-of-use work for you?

> Yes. time-of-use is working well. This means, that writing registers works well. Your inverter model stores the time in other Modbus registers. Gemini suggests this Register | Value |...

Looks promising. Try out this `ghcr.io/kbialek/deye-inverter-mqtt:2025.11.1-beta-1` image and let me know if it's working for you.

This version is a dirty hack 🙂 Thanks for checking it. Now when I know it's okay, I can make this feature configurable.

> [@kbialek](https://github.com/kbialek) SG01HP3 also uses registers 62-64 for storing date&time and I already have some code to support that, that makes the time setting feature more universal - allows to...

@daniel-deptula That is an awesome contribution! I'm publishing it as a beta image for testing here `ghcr.io/kbialek/deye-inverter-mqtt:2025.12.1-beta-1`. I've added DateTimeSensors for string and micro inverters, so I can test it...

@stevehof This enhancement is now included in `ghcr.io/kbialek/deye-inverter-mqtt:2025.10.2-beta-1` image. Please try it out and give me your feedback.