Daniel M

@2x4ever do you by coincidence have a HA bluetooth proxy running and could extract some HA logs from the device that would include the manufacturer data? This might help identifying...

seems there is an issue with the velux.reboot_gateway service as manually rebooting the gateway and restart HA will fix the issue. There is a new version of pyvlx [0.2.22](https://github.com/Julius2342/pyvlx/releases/tag/0.2.22) available...

there are multiple variations using esphome and a esp32 https://github.com/vekexasia/comfoair-esp32 https://github.com/felixstorm/esphome-custom-components/ https://github.com/yoziru/esphome-zehnder-comfoair https://github.com/dan-s-github/zehnder-comfoair-can

It seems to have resolved by itself today

created a pr to address this issue #64

I also migrated to the [spacerokk](https://github.com/spacerokk/bar-card) fork but have an issue with the entity name on the card  before the 'name_attr' was actually evaluated ``` entities: - entity: sensor.weatherflow_forecast_0...

Unfortunately the way the repo was forked does not allow to create issues there. At least I couldn't find where to create issues on the forked repo

Fixed my issue by using the `custom:config-template-card`  Posting here in case someone else faces a similar issue. ``` ... - type: custom:config-template-card entities: - sensor.weatherflow_forecast_0 - sensor.weatherflow_forecast_1 - sensor.weatherflow_forecast_2...