v0.44.44

Improvements

• When a bridge's connection is down, the tooltip on the bridge's connection status now says why, for example that the DNS lookup timed out or the device refused the connection, and what to check
• Routine start-up and restart messages from umh-core's internal components are now DEBUG instead of INFO, which makes state changes, warnings and errors easier to spot
• If umh-core cannot start its FSMv2 supervisor, the container now exits with code 1, so its restart policy can start it again. Before, it kept running without FSMv2
• USE_GATEKEEPER no longer has any effect and can be removed from your configuration. The useGatekeeper key in config.yaml is ignored

Fixes

• The historian status message now reads "connected to TimescaleDB" instead of "running (no health check)", and a degraded historian says whether TimescaleDB is unreachable or rejected the credentials or database name
• A bridge variable named historian is now always ignored, like location. Before, {{ .historian.* }} rendered that variable when no valid historian: section was configured. The bridge now fails with the error to add or fix the historian: section, which also says the variable was ignored