* Emoncms API provides a Unit
The EmonCMS API has been amended to include a 'unit' as part of it's payload. By using this information, all the sensors can be created without the need for individual sensors to be setup by type.
The change is backward compatible so if a unit type has been specified in the configuration, this will be used by default.
If no unit is pecified either by the Home Assistant configuration, or the Emoncms API, then the default of W will be used as before.
* Update sensor.py
Check the 'unit' key is in the API call. Older systems may not have that key in the payload.
* Modified approach with new configuration item
* Removed new config item
Removed the configuration item. The integration attempts to get the unit from the API.
If this fails *or* the unit key of the API is blank, either the specified unit, or the default will be used.
If approved, documentation will be updated.
* Update homeassistant/components/emoncms/sensor.py
Co-Authored-By: springstan <46536646+springstan@users.noreply.github.com>
* Update homeassistant/components/emoncms/sensor.py
Co-Authored-By: springstan <46536646+springstan@users.noreply.github.com>
* Apply suggestions from code review
* Apply suggestions from code review v2
* Update homeassistant/components/emoncms/sensor.py
Co-Authored-By: springstan <46536646+springstan@users.noreply.github.com>
* Update sensor.py
Update `config_unit`
Co-authored-by: springstan <46536646+springstan@users.noreply.github.com>
* [soundtouch] workaround for API bug when removing multiple slaves from a zone at once
* [soundtouch] added additional attributes exposing multiroom zone info
* Fix update with slave entities
* Add zone attributes test
* Fix and clean up tests
* Fix typo
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Add edl21 component for SML-based smart meters
* edl21: Remove unused variable
* [edl21] Add 1 minute throttle to the sensor
* Update homeassistant/components/edl21/manifest.json
Fix documentation URL
Co-Authored-By: Paulus Schoutsen <paulus@home-assistant.io>
* edl21: Move imports to top
* edl21: Remove special case for STATE_UNKNOWN, which replicated default behavior
* edl21: Implement blacklist for and warn about unhandled OBIS values
* edl21: Make blacklist global
* edl21: Add filter to issues URL
Co-Authored-By: Paulus Schoutsen <paulus@home-assistant.io>
* edl21: Rename device to entity
* edl21: Don't schedule async_add_entities
* edl21: Use dispatcher, implement own throttling mechanism
* edl21: Simplify keeping track of known obis
* edl21: Use whitelist for state attributes
* edl21: Remove dispatcher on shutdown
* edl21: Convert state attributes to snakecase
* edl21: Annotate handle_telegram with @callback
* edl21: Call async_write_ha_state instead of schedule_update_ha_state
Co-authored-by: David Straub <straub@protonmail.com>
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* Allow string values on zwave.set_node_value
This allows for:
* Accessing longer value_ids. In some cases, value ids in z-wave nodes are very large (17 digits in my case). Passing them as int does not seem to work well (python probably truncates the number), but passing them as string works fine
* Changing color values, which are represented as hex string
reformat test
* update services.yaml with string set_node_value
The documentation for google_travel_time was at odds with the
implementation. The documentation stated a default scan time of
5 minutes, but the implementation was using Throttle which resulted
in the sensor updating at a maximum rate of one API call every
5 minutes. This was especially at odds with a given example at
the end of the documentation, which showed updating the sensor
every 2 minutes during commute times.
This change brings the implementation in line with the docs by
adopting the `SCAN_INTERVAL` constant set to the stated default
of 5 minutes and removing the Throttle.
* Update image_processing.py
Adds save timestamp file and adds last_detection attribute
* Update test_image_processing.py
Adds test
* Adds assert pil_img.save.call_args
* Test timestamp filename
* Add test bad data
* Update test_image_processing.py
* Fix bad image data test
* Update homeassistant/components/sighthound/image_processing.py
Co-Authored-By: Martin Hjelmare <marhje52@gmail.com>
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Reduce log level for initial error and bump library version
* Use new buienradar library version which reduces the log level
for some types of warnings.
* Initially logs at a lower level and only logs at WARN for repeated
errors.
This should serve to reduce confusion with users such as in
issue #32301.
* Fix linter error with new linter settings.
* Fix linter warning
* Update homeassistant/components/buienradar/util.py
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* code quality improvements
* code quality improvements and fixed tests
* explicitly set unique ids
* improve unique id creation
* remove entities from entity registry
* added test for removing entities from entity registry
* revert entity registry handling from sensor and test code
* check for entity registry removal in geolocation test case
* make import absolute; isort
* change quality scale
* add is_muted property and update tests
* black
* manually set is_muted on async_mute_volume calls to set state early
* combine two lines into one
* set is_muted to None when device is not on
* Flume Cleanups
* Sensors now show the name
* include_devices and exclude_devices are now available in the config.
* Address review items
* bump as 0.3.0 is published
