aschamberger

# As there is currently no proper way to semantically model entities in ETS 
# I assume everybody has some kind of group address configuration scheme
# (there are "functions" but as far as I can see they are not really usable 
# at the moment and also not "migratable" from an existing GA structure).
#
# I want to have the single source ETS with rule based imports and no manual 
# edits of them within Hass. With rerunning the rules after an ETS export
# you have all additions (or deletions?) reflected without adding anything 
# in two places. At least in my configuration I can always assume there is 
# at least one leading group address in order to define an entity.

elupus

blueprint:
  name: IKEA Symfonisk Rotary Dimmer
  description: Use symfonisk as knx relative dimmer
  domain: automation
  input:
    rotary_device:
      name: Source device
      selector:
        device:
          integration: zha

numberoverzero

import asyncio
missing = object()


class Value:
    '''
    Simple class that enables `await value.wait_for(foo)` to wait until the
    variable is set to the expected value, without blocking the event loop.

    Loosely modeled after asyncio.Event and asyncio.Condition