Skip to content

Add DISCOVERY_DIAGNOSTIC environment variable - #34

Open
jcsanyi wants to merge 1 commit into
theengs:mainfrom
jcsanyi:discovery-diagnostic
Open

Add DISCOVERY_DIAGNOSTIC environment variable#34
jcsanyi wants to merge 1 commit into
theengs:mainfrom
jcsanyi:discovery-diagnostic

Conversation

@jcsanyi

@jcsanyi jcsanyi commented Aug 15, 2026

Copy link
Copy Markdown
  • added DISCOVERY_DIAGNOSTIC environment variable to start.sh, validated like the other booleans
  • added it to the README examples and examples/docker-compose.yml

This sets discovery_diagnostic, the option added in theengs/gateway#325, which marks battery, voltage and RSSI entities with Home Assistant's diagnostic entity category so they group separately from a device's main readings. Without this there's no way to reach it from Docker except the undocumented PARAMS passthrough.

It defaults to false, matching the gateway's own default for minimal disruption to existing installations. The documented examples set it to true on purpose, to encourage usage of the option on new installs.

Nothing breaks if this is released early, but it does document an option that won't actually exist until a gateway version that supports discovery_diagnostic is released. Should be merged around the same time that the TheengsGateway==1.7.5 pin is bumped to a version with this support.

[tested on amd64 against a build of theengs/gateway#325 with start.sh pulled in from this branch: works as expected with the variable unset, set to an invalid value, and correctly set to true/false]

Theengs Gateway can mark battery, voltage and RSSI entities with Home
Assistant's diagnostic entity category, but start.sh regenerates
theengsgw.conf from a fixed set of keys on every start, so the option
was unreachable from Docker except through the PARAMS passthrough.

Validated like the other boolean variables and defaulting to false,
matching the gateway's own default. The key is ignored by gateway
versions that don't know it, so this is inert until the pinned version
supports the option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant