luar123

The problem described by @eschwim is fixed with #47 in 2.3.0. However, the home-assistant integration still uses 2.1.3 and does not react on any server update/connect/disconnect events. I will send...

HA will switch to 2.3.0 in 2022.11, this will fix the initial issue. To fix the remaining issues I made a new PR https://github.com/home-assistant/core/pull/80846 If you want to get this...

Please merge #80288 first, only the last two commits belong to this PR. Made this a draft because I am still waiting for a upstream bug fix and although everything...

Also in #129 is some discussion about entities and devices.

Thanks for the feedback. I am now using these three functions to get the `area_id` of an entity, the area name, and all entities filtered by class or domain for...

Thanks, that is exactly how I am using it. `@pyscript_compile` is a very good idea, makes `get_entities_for_area` cleaner: ``` @pyscript_compile def get_entities_for_area(area_id, domain=None, device_class=None): entities=homeassistant.helpers.entity_registry.async_entries_for_area(entreg, area_id) entities.extend([e for x in...

Yes, we have a custom measurement system which adds all the additional information (Measurement setup, device, biasing, etc.) after the option line. Something like: ``` # GHz S MA R...

This could be changed for future measurements, but the code I am working on needs to handle old files as well. Anyway, I will I just read the comments separately...

This is a snapcast and HA issue: As stated in the first posts the dynamic groups are pretty useless, as they can change. Also a client can be in one...

@carlos-sarmiento: Here you go: https://github.com/luar123/snapcast_custom_component