Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SYS] Multiple connections management #1947

Merged
merged 1 commit into from
May 20, 2024
Merged

Conversation

1technophile
Copy link
Owner

Description:

  • Enable the management of different connections at runtime with a set of certs for each (3 connections set of parameters can be stored)
  • Add the option to validate or not the mqtt server certificate, during onboarding and with MQTT
  • Add the capability to add the certificates during onboarding

Checklist:

  • The pull request is done against the latest development branch
  • Only one feature/fix was added per PR and the code change compiles without warnings
  • I accept the DCO.

@1technophile 1technophile force-pushed the improve-connections branch 2 times, most recently from 8abce82 to 8102379 Compare May 17, 2024 20:40
Enable the management of different connections at runtime with a set of certs for each
Add parameters to the WiFi Manager onboarding, client certificates, certificate validation
@1technophile 1technophile force-pushed the improve-connections branch from 8102379 to 53aa910 Compare May 18, 2024 10:51
@1technophile 1technophile merged commit f98474b into development May 20, 2024
144 checks passed
@1technophile 1technophile deleted the improve-connections branch May 20, 2024 14:30
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)
DigiH added a commit that referenced this pull request Jan 24, 2025
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