hass

Love your card, great work! One thing I would wish for:

To have in the status bar the option to not only call a service like today ("clean room X"), but to allow putting a clickable icon in there which will launch a new browser window with a pre-defined target. In essence mimicking what the famous "button card" offers:

• type: button
  tap_action:
  action: url
  url_path: IP

(1) The custom state strings are defined in the source code and outlined here - https://danobot.github.io/ec-docs/special/state-strings.

• control_states_on and control_states_off are defined, but not used in the source code, so do nothing.
• state_states_off is defined, but not used in the source code at all

(2) Service data is defined here - https://danobot.github.io/ec-docs/config-advance

As mentioned in an earlier issue by me, I think the ability to view the data frames that are sent and received by Bellows in Wireshark. @rcloran mentioned he was open to the idea. This is something that would come in useful e.g. in #43, where an unknown type is in the data frame that is received, which results in a crash.

Having only one antenna device, I can't debug with another device while u

Describe the solution you'd like
I use custom service with custom data for actions eg.

        actions:
          - name: Off
            icon: 'mdi:fan-off'
            service: input_select.select_option
            service_data:
              entity_id: input_select.mode_fan_salon_air_purifier
              option: Off

In this case i would like to be able to speci

Currently, this integration will publish the current state of all entities every n seconds, regardless of whether or not this entity underwent a state change.

The intent was to make visualizing this information easier in Kibana, as missing values would not render nicely in line or area charts.

Users who only want to publish state changes need to configure only_publish_changed: true.

K