The Wayback Machine - https://web.archive.org/web/20220607164441/https://github.com/topics/hass
Skip to content
#

hass

Here are 260 public repositories matching this topic...

vacuum-card
dbochicchio
dbochicchio commented Apr 27, 2022

Describe the solution you'd like
Combine both entity_id and attribute, so we could get (and transform) something from an entity where the primary attribute is not what we want, without creating a new sensor.

ie:

   - entity_id: sensor.deebot920_last_cleaning
     attribute: timestamp
     value_template: '{{ value | timestamp_custom("%Y/%m/%d %H:%M:%S") }}'
     subtitle: Last job
enhancement good first issue
derekoharrow
derekoharrow commented Nov 17, 2020

(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

help wanted good first issue
lesteenman
lesteenman commented Aug 24, 2017

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

purifier-card
petercpg
petercpg commented Sep 5, 2021

Is your feature request related to a problem? Please describe.

I have a Smartmi Air Purifier (zhimi.airpurifer.za1) which is not supported by official HA xiaomi_miio integration, https://github.com/syssi/xiaomi_airpurifier is used instead.

Some actions like changing fan levels requires two-step service calls:

  • Change preset_mode to Favorite, if it is in other states
  • Set desired
help wanted good first issue
legrego
legrego commented Jan 4, 2021

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

enhancement good first issue discuss

Improve this page

Add a description, image, and links to the hass topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the hass topic, visit your repo's landing page and select "manage topics."

Learn more