Markus

can confirm this ```yaml securityContext: readOnlyRootFilesystem: true allowPrivilegeEscalation: false capabilities: add: ["NET_RAW"] ``` did not work in my kubeadm v1.24.2 cluster and ```yaml podSecurityContext: sysctls: - name: net.ipv4.ping_group_range value: "0...

Hi have seen the same behaviour for a change from 2.10.0 to 2.11.1. stuck in `waiting for quorum` until manual intervention.

may this helps as base: https://github.com/SmartEVSE/smartevse/pull/33/commits/aed6ccbbc5874c5bd411822326e6e05316b8c092 I Impediment a simple lock that can be enabled and disabled via Modbus. In my use case I have connected a raspberry pi via...

physically not much, both are a Induktor electrical. but in the code for the SOLENOID does send pulses, which is bad for the relay. and my code Introduces new checks...

ok noted, used to the rebase force push workflow from work.

will create a PR for ESPhome on the weekend to decouple MQTT entity discovery from IP / device discovery on the MQTT Component as an option, but the code here...

@emontnemery there are 2 ways to connect ESPHome to Home Assistant. 1. via Home Assistant MQTT entity discovery e.g. https://www.home-assistant.io/integrations/switch.mqtt/ which is not touched in this PR 2. via ESPHome...

Have added the MQTT device discovery protocoll to the ESPHome docs: https://github.com/esphome/esphome-docs/pull/3809 https://deploy-preview-3809--esphome.netlify.app/components/mqtt#mqtt-device-discovery

position feedback and control: #57

openTelemetry is only supported by v3 and the chart handles this here: https://github.com/traefik/traefik-helm-chart/blob/1f042ea9a0d354ebc00707bfd4e4f534a2a41859/traefik/templates/_podtemplate.tpl#L307-L310 https://github.com/traefik/traefik-helm-chart/blob/1f042ea9a0d354ebc00707bfd4e4f534a2a41859/traefik/templates/_podtemplate.tpl#L366-L369