[DISC] battery_ok discovery differentiation #1958
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DigiH
force-pushed
the
battery_ok
branch
2 times, most recently
from
65251b9 to
882b569
Compare
|
The one issue remaining, not quite breaking, but slightly confusing, is that previous wrong battery_ok sensor % discoveries do not get overwritten by the new binary_sensor battery_ok discovery, but they exist alongside each other until the sensor % discovery entry is manually deleted, or the whole MQTT integration device is being deleted and discovered afresh. Still very much worth it for proper battery_ok discovery in my opinion. |
Differentiation between 0%-100% float battery_ok devices' discovery and binary_sensor devices battery_ok
|
Thanks |
DigiH
pushed a commit
that referenced
this pull request
Jan 24, 2025
Enable the management of different connections at runtime with a set of certs for each. Add parameters to the WiFi Manager onboarding, client certificates, and certificate validation [SYS] Fix wrong connection index record during onboarding (#1961) and no connection validation if CNT_DEFAULT_INDEX is different than 0 [DISC] always auto-discover Presence/Tracker timeout (#1959) auto-discover Presence/Tracker timeout even when HASS presence is not active Also inject an additional placeholder rssi key and value into the BM2 voltage connection message to avoid the message being registered as a device tracker AWAY https://community.openmqttgateway.com/t/bm2-home-and-away/3315 [DISC] battery_ok discovery differentiation (#1958) Differentiation between 0%-100% float battery_ok devices' discovery and binary_sensor devices battery_ok [DISC] Consistent upper case discovery property names (#1957) And property name change of 'light' and 'lux' to Illuminance [DISC] Nexa additional auto-discovery properties (#1953) (#1955) * [DISC] Nexa additional discovery properties (#1953) * State as binary_sensor ON/OFF * Alphabetical sorting [BOARD][BREAKING] Change of partition for esp32dev-pilight (#1952) [SYS] Add connection fallback capability (#1950) This feature enable to rotate among the connection parameters index to find a valid one when the current MQTT connection is not working [SYS] Change log level when publication is canceled (#1949)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Differentiation between 0%-100% float battery_ok devices' discovery and binary_sensor devices battery_ok
battery_ok binary_sensor
battery_ok float
Checklist: