@Djiest wrote:

I’m a newbee with templating and need some help to grasp the basic concepts.
I have a couple of sensors, as follows

When I test a template and loop over these sensors, some have the attribute date and some don’t, which results in outputting ‘None’. I can not make a distinction between the two

Window2869×462 15.2 KB

What am I doing wrong here?

Posts: 1

Participants: 1

Read full topic

@xp1ratex wrote:

Hi.

I get duplicated messages from my motionsensor in OZW log, any idea whats causing this?
I have no problem with my other fgms001.
Running Hassio 0.103.5 in ubuntu 18.10 docker, Aeotec Z-Stick Gen5 as z-wave controller.

2020-01-01 20:59:28.123 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Temperature: value=19.8C
2020-01-01 20:59:28.123 Detail, Node008, Refreshed Value: old value=20.9, new value=19.8, type=decimal
2020-01-01 20:59:28.123 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:28.124 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:28.175 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xc6, 0x28
2020-01-01 20:59:28.175 Detail,
2020-01-01 20:59:28.175 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Temperature: value=19.8C
2020-01-01 20:59:28.175 Detail, Node008, Refreshed Value: old value=19.8, new value=19.8, type=decimal
2020-01-01 20:59:28.175 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:28.175 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:28.214 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xc6, 0x28
2020-01-01 20:59:28.214 Detail,
2020-01-01 20:59:28.214 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Temperature: value=19.8C
2020-01-01 20:59:28.214 Detail, Node008, Refreshed Value: old value=19.8, new value=19.8, type=decimal
2020-01-01 20:59:28.214 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:28.214 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:28.533 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xc6, 0x28
2020-01-01 20:59:28.533 Detail,
2020-01-01 20:59:28.533 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Temperature: value=19.8C
2020-01-01 20:59:28.533 Detail, Node008, Refreshed Value: old value=19.8, new value=19.8, type=decimal
2020-01-01 20:59:28.533 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:28.533 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.156 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.156 Detail,
2020-01-01 20:59:32.156 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.156 Detail, Node008, Refreshed Value: old value=20, new value=19, type=decimal
2020-01-01 20:59:32.156 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.156 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.207 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.207 Detail,
2020-01-01 20:59:32.207 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.207 Detail, Node008, Refreshed Value: old value=19, new value=19, type=decimal
2020-01-01 20:59:32.207 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.207 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.246 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.246 Detail,
2020-01-01 20:59:32.246 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.246 Detail, Node008, Refreshed Value: old value=19, new value=19, type=decimal
2020-01-01 20:59:32.246 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.246 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.286 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.286 Detail,
2020-01-01 20:59:32.286 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.286 Detail, Node008, Refreshed Value: old value=19, new value=19, type=decimal
2020-01-01 20:59:32.286 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.287 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.444 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.444 Detail,
2020-01-01 20:59:32.444 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.444 Detail, Node008, Refreshed Value: old value=19, new value=19, type=decimal
2020-01-01 20:59:32.444 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.444 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:32.565 Detail, Node008,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x08, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x13, 0xd7
2020-01-01 20:59:32.565 Detail,
2020-01-01 20:59:32.565 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Luminance: value=19lux
2020-01-01 20:59:32.565 Detail, Node008, Refreshed Value: old value=19, new value=19, type=decimal
2020-01-01 20:59:32.565 Detail, Node008, Changes to this value are not verified
2020-01-01 20:59:32.565 Detail, Node008, Notification: ValueChanged
2020-01-01 20:59:57.300 Detail, Node008,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x08, 0x02, 0x84, 0x07, 0x7a

Posts: 1

Participants: 1

Read full topic

@SpikeyGG wrote:

I searched through the forum and found this post which sounds very similar to mine but it seems to be specific to the philips hue.

I am re-configuring my network trying to be as “IP-less” as possible – using my local DNS (pihole) servers to resolve all the devices in and around the house and writing rules on my router which are abstracted to use the local DNS names instead of hardcoded IPs. I’d like to do the same thing with Hassio but I’ve realized quickly that nearly all the components configuration.yaml entries require hardcoded IP addresses if you’re not going to use discovery (which I cannot because VLANs).

Recorder - When using DNS in the engine string it fails
“(MySQLdb._exceptions.OperationalError) (2005, “Unknown MySQL server host ‘logger-box’ (-3)”)
(Background on this error at: http://sqlalche.me/e/e3q8)”

Sonos - when I supply the hostnames, I get these warnings and no devices are found. When I use the IP addresses of the devices it works. The autodiscovery doesn’t work, even when I specify the interface_addr option with the hostname of the IP on hass.io that I want it to use. Everything must be IP addresses for it to work on my setup.

Chromecast - I’m unable to get the autodiscovery to find my device and I cannot supply a hostname, only a host’s IP address.

AsusWrt - using a hostname causes an “invalid config” error.

Pi-hole - config docs say it will default to pi.hole but that doesn’t work for me, nor can I force it to the pihole name that I actually use.

ZoneMinder - using a hostname here causes an “invalid config” error.

Envoy - It states that you can leave the ip_address option off and it’ll default to the envoy hostname which appers to be true but it still cannot find my envoy device (even though I can ping it from my hassio device’s ssh).

image738×47 8 KB

I’ve tried names in all the configuration “host” fields and they fail. I’m running hassio on a raspberry pi so it’s dockerized and I wonder if this is the problem. I can ssh into the device and resolve all my local hostnames to IPs (using ping and nslookup) so it seems like it should work but everything gives me errors when I try to use the names instead of IPs.

Thoughts?

Posts: 5

Participants: 4

Read full topic

@Nimesh_Panchal wrote:

Hello,

I’ve signed up for HA Cloud to link to my Alexa devices for voice control. Everything seems to be connected correctly, however Alexa won’t control any devices? If I ask to turn on or off lights, or scenes, she simply says the Device is not responding.

Even within the Alexa app on iOS, it says Device is unresponsive. Any help would be appreciated!

IMG_0A6FFAEA1125-11125×2436 306 KB

Posts: 1

Participants: 1

Read full topic

@rdlaner wrote:

Hey folks, I’m trying to set up an automation that is triggered by an MQTT topic and then sets the value of an input number slider based on data from the MQTT topic. The trigger seems to be working fine, but the action that is supposed to update the input number value is not doing anything. I tried using the template editor, but it doesn’t seem to work for automations.

I suspect that I’m not parsing the trigger payload correctly in the data_template. Any insight on what I may be doing wrong?

Here’s the yaml:

- alias: Kitchen_RGBW_Sub
  id: Kitchen_RGBW_Sub
  trigger:
    platform: mqtt
    topic: "stat/Lights/Kitchen_Cab/STATE"
  action:
    - service: input_number.set_value
      data_template:
        entity_id: input_number.red_slider
        value: "{{ trigger.payload.value_json.Color.split(',')[0] | int}}"
    - service: input_number.set_value
      data_template:
        entity_id: input_number.green_slider
        value: "{{ trigger.payload.value_json.Color.split(',')[1] | int }}"
    - service: input_number.set_value
      data_template:
        entity_id: input_number.blue_slider
        value: "{{ trigger.payload.value_json.Color.split(',')[2] | int }}"
    - service: input_number.set_value
      data_template:
        entity_id: input_number.white_slider
        value: "{{ trigger.payload.value_json.Channel[3] | int }}"

Posts: 1

Participants: 1

Read full topic

@Gladz0r wrote:

Hello there,
I want to use a button on my KNX installation switch.alarm_knop to trigger an Home Assistant automation (automation.alarm_niemand_thuis - that is my alarm with connected sensors) and turn off a group off lights light.alarmlichtuit.
This is working fine at the moment but my KNX installation deletes the value on the bus after one hour triggering automation id 14 and turning the alarm off.
I’m wondering if I can use the toggle function? But my knowledge of Yaml is not good enough to fix this.

The code that is now working until the KNX bus refreshes is:

- id: '13'
  alias: Slaapkamer Alarm en lichten Aan
  trigger:
  - entity_id: switch.alarm_knop
    platform: state
    to: 'on'
  action:
  - data:
      entity_id: automation.alarm_niemand_thuis
    service: automation.turn_on
  - data:
      entity_id: light.alarmlichtuit
    service: light.turn_off   
###################################################
- id: '14'
  alias: Slaapkamer Alarm en lichten Uit
  trigger:
  - entity_id: switch.alarm_knop
    platform: state
    to: 'off'
  action:
  - data:
      entity_id: automation.alarm_niemand_thuis
    service: automation.turn_off 

In my configuration.yaml

switch:
  - platform: knx
    name: Alarm Knop
    address: '1/1/35'
    state_address: '1/4/35'

Posts: 1

Participants: 1

Read full topic

@sretlow wrote:

I’ve been trying to make a group and other possible solutions which I’ve fou d on YouTube and here. Not succeeded.

What I want is to create one button to switch All lights of when I go to bed. Not toggle because some are possibly already off. Some with a solution or link to a solution?

Posts: 7

Participants: 4

Read full topic

@SylvainGa wrote:

I’m using hass.io and do have a full backup from earlier today (through hass.io snapshot). Is there a way to get the card back? I really don’t want to sets all the entities again

Thanks.

Posts: 3

Participants: 2

Read full topic

@chanrwm wrote:

Hi,

New to Home Assistant and am trying to get Google Assistant hooked up.

I followed the steps at:

I set my home assistant to be accessed externally w/ a self signed cert and set up several devices.
Created a new “Action” project on Google Assistant, with the “Fulfillment” URL and both API and service keys in my configuration.yaml.

When I try to link the account to Google Assistant, I can get to my HA server’s login screen, but when I click okay the account remained unlinked with no error messages from Google Home and nothing I can see from logs. I tried messing around with logging in with the normal auth and the legacy api password. Didn’t make a difference. I tried having the api_key and/or service_account. Made sure the project_id was correct. Tried with an entity_config and without. Any ideas on how I can figure out what is wrong?

homeassistant:
    unit_system: metric
    auth_providers:
    - type: homeassistant
    - type: legacy_api_password
      api_password: "password"

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
  base_url: URL
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

# For Monoprice Media Player
media_player:
  - platform: monoprice
    port: /dev/ttyUSB0
    zones:
      11:
        name: Bedroom
      12:
        name: Ensuite
      13:
        name: Living Room
      14:
        name: Kitchen
      15:
        name: Basement

    sources:
      1:
        name: Bluetooth
      5:
        name: Chromecast
        
# For Google Assistant
google_assistant:
  project_id: "project id"
  api_key: "key"
  report_state: true
  service_account: !include /config/key.json
  expose_by_default: true
  exposed_domains:
    - switch
    - group
    - light

Account_Linking486×735 20.7 KB

Action895×444 20.7 KB

Posts: 4

Participants: 2

Read full topic

@jriker1 wrote:

Just updated the alexa_media component. I’m continuously getting the below for each of my devices:

2020-01-01 16:27:26 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.john_alexa fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 459, in async_device_update
    await self.async_update()
  File "/config/custom_components/alexa_media/helpers.py", line 143, in wrapper
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/media_player.py", line 667, in async_update
    no_throttle=True)
  File "/config/custom_components/alexa_media/helpers.py", line 143, in wrapper
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/media_player.py", line 371, in refresh
    self._parent_clusters))
  File "/config/custom_components/alexa_media/media_player.py", line 370, in <lambda>
    ['media_player'][x].state == STATE_PLAYING),
KeyError: '0096d7adfa104b7abfd8817f78c06c49'

Any idea what’s going on?

Posts: 2

Participants: 2

Read full topic

@HipsterDufus wrote:

After spending way too much time building a floorplan dashboard, I think I have something that I’m reasonably happy with. But have run into a problem that I can’t figure out.

My floorplan looks like this, using a picture-element image:

ArgyleHouse1200×672 817 KB

I’ve been able to add various icons for the switches and lights, so that’s fine. My next useless task is to have rooms light up when a switch is on. I’m using this code:

          - entity: switch.dining_room_light_7
            image: /local/ArgyleHouse-dining2.png?v=1
            state_filter:
              'off': brightness(50%)
              'on': brightness(100%)
              style:
                left: 80%
                top: 10%
                width: 100%

The ArgyleHouse-dining2.png file is an exact copy of my picture-element background, with everything except the dining room cropped to transparent (can’t include it here, since it’s my first post).

The brightness works fine when the switch is toggled, so no problem there.

However, Lovelace insists on placing that cropped image in the extreme lower left of my background, almost as if I had something like top=90 and left=5. No matter what different values I put in for top and left, it doesn’t move.

I’ve tried using different images, including an image just of the dining room without the transparent part. I’ve cleared the cache in the browser and restarted HA several times. Hass.io is using current version.

Any ideas on other things I can try? It seems that it should just work, based on others’ experiences, but I’m stuck.

PS: This is my first post, so hope the inline images and code comes out OK.

Posts: 1

Participants: 1

Read full topic

@DrSpaldo wrote:

Recently @tom_l helped me in writing a switch for my Dyson fan. I have created a new topic as it is going down another path.

The switch he created was as follows:

switch:
  - platform: template
    switches:
      oscillation:
        friendly_name: Oscillation
        value_template: "{{ is_state('fan.bedroom', 'on') and is_state_attr('fan.bedroom', 'oscillating', true) }}"
        turn_on:
          service: fan.oscillate
          data:
            entity_id: fan.bedroom
            oscillating: true
        turn_off:
          service: fan.oscillate
          data:
            entity_id: fan.bedroom
            oscillating: false
        icon_template: >
          {% if is_state('fan.bedroom', 'on') and is_state_attr('fan.bedroom', 'oscillating', true) %}
            mdi:arrow-left-right-bold
          {% else %}
            mdi:minus-circle-outline
          {% endif %}

This works most of the time, however, it turns out that the sensor/state reports differently depending on the mode the fan is in. So if it is turned on with a manually selected speed, then:

fan.bedroom state is on
fan.bedroom auto_mode is false

If the fan is turned on and in auto mode:

fan.bedroom state is off
fan.bedroom auto_mode is true

If the fan is not on at all

fan.bedroom state is off
fan.bedroom auto_mode is false

So I think that the above code needs minor modification, however, I am just unsure how to add the OR statement or what is required to check two states to give the required answer. It looks like two sections need to be updated:

 value_template: "{{ is_state('fan.bedroom', 'on') and is_state_attr('fan.bedroom', 'oscillating', true) }}"

{% if is_state('fan.bedroom', 'on') and is_state_attr('fan.bedroom', 'oscillating', true) %}
            mdi:arrow-left-right-bold

So, finally, to my actual question How do I add into the above code to also check if the fan is in auto_mode as well, because this also indicates that it is turned on. Not just the state.

Hopefully this makes sense

Posts: 2

Participants: 2

Read full topic

@mikep wrote:

I’m using tasmota with hassio.
I have a switch and I get state of the switch on or off from 2 different mqtt messages and I was wondering how to update the switch state correctly. 1 of the mqtt messages come when the switch is changed and that message I have plugged into the configuration. but until the switch is changed the state is unknow. The second mqtt message comes every 60 seconds in a tele message with all the other switches. How can I get information from the tele message and update the switch state?

16:04:31 MQT: jacuzzi_Tub_Down/tele/SENSOR = {"Time":"2020-01-01T16:04:31","Switch1":"ON","Switch2":"OFF","Switch4":"ON","Switch5":"ON"}

Second question, where does Home Assistant save the auto detected sensor information? and how can I modifiy it?

Thanks

Posts: 1

Participants: 1

Read full topic

@TheStigh wrote:

Hi,

I have a sensor today where I get a long value in return.
I’ve used truncate earlier that works fine, but it takes the first X letters of the value.

Now I want to grab some text in the ‘middle’ and was hoping ‘slice’ would work, but no…

This is the current code:

  - platform: command_line
    name: NUC BIOS
    command: "cat /sys/class/dmi/id/bios_vendor"
    value_template: '{{value|truncate(18,True)}}'

The reason for value ‘18’ is to include the 18 periods after the truncated value.

How can I use my ‘value_template’ to get characters 7 to 15 to be the value of the sensor?

Posts: 3

Participants: 2

Read full topic

@halest wrote:

Hey,
Google wasn’t too helpful, so here’s my question for all of you lovely folks.
As far as I see it right now it is not possible in an automation condition to ask for an MQTT state, something along the lines of (and I’m completely making this up)

condition:
  - condition: template
    value_template: '{{ mqtt("my/topic") > 0 }}'

Am I correct in that assumption? I would guess I’d have to incorporate an input_number into that automation?

Best regards and happy new year
Halest

Posts: 4

Participants: 2

Read full topic

@ihavenoidea wrote:

Just installed Hass.io on a new Pi4. I’ve noticed the Updater icon at the top is Unavailable.

I’m new to HA so I’m not sure if this is expected or not.

Posts: 2

Participants: 2

Read full topic

@TheStigh wrote:

Hi all,

I use an automation to light up a Philips Hue bulb at night based on motion.
I use transition to dim the light when it goes off, and all works fine.

But when we wake up in the morning and use Google Home to say “Turn og the living room lights”, this particular bulb fires up with ‘brightness: 1’

Is it a way to set the ‘brightness’ back to 255 even if the bulb is off? Otherwise I have to remove the transition from the automation.

- alias: 13 - Skru av nattlys i stue etter 15 minutter
  id: Skru av nattlys i stue etter 15 minutter
  trigger:
  - platform: state
    entity_id: binary_sensor.stue_sensor_motion
    to: 'off'
    for:
      minutes: 15
  condition:
  - condition: time
    after: '01:00:00'
    before: '06:00:00'
  action:
  - service: light.turn_off
    entity_id: light.hue_c1_v_trapp
    data:
      transition: 60

Posts: 2

Participants: 2

Read full topic

@Carlos_Lara wrote:

Hi,

I am having the following warnings in my logs:

2020-01-02 03:28:22 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for circadian_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-01-02 03:28:22 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-01-02 03:28:41 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/22
2020-01-02 03:28:41 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/22’ from <Sensor name=“LF Flur EG Treppe” sensor=“None/GroupAddress(“2/5/22”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:43 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/7
2020-01-02 03:28:43 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/7’ from <Sensor name=“T Flur OG Treppe” sensor=“None/GroupAddress(“2/5/7”)/None/None” value=“None” unit=“°C”/>
2020-01-02 03:28:44 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/23
2020-01-02 03:28:44 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/23’ from <Sensor name=“LF Flur OG Treppe” sensor=“None/GroupAddress(“2/5/23”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:45 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/25
2020-01-02 03:28:45 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/25’ from <Sensor name=“LF Leo” sensor=“None/GroupAddress(“2/5/25”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:46 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/26
2020-01-02 03:28:46 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/26’ from <Sensor name=“LF Julian” sensor=“None/GroupAddress(“2/5/26”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:47 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/27
2020-01-02 03:28:47 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/27’ from <Sensor name=“LF Kinderbad” sensor=“None/GroupAddress(“2/5/27”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:48 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/29
2020-01-02 03:28:48 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/29’ from <Sensor name=“LF TV” sensor=“None/GroupAddress(“2/5/29”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:49 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/30
2020-01-02 03:28:49 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/30’ from <Sensor name=“LF Ankleide” sensor=“None/GroupAddress(“2/5/30”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:51 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/31
2020-01-02 03:28:51 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/31’ from <Sensor name=“LF Eltern” sensor=“None/GroupAddress(“2/5/31”)/None/None” value=“None” unit="%"/>
2020-01-02 03:28:53 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/5
2020-01-02 03:28:53 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/5’ from <Sensor name=“T WEK Wohnen” sensor=“None/GroupAddress(“2/5/5”)/None/None” value=“None” unit=“°C”/>
2020-01-02 03:28:54 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/20
2020-01-02 03:28:54 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/20’ from <Sensor name=“LF WEK Küche” sensor=“None/GroupAddress(“2/5/20”)//60.64” value=“60.64” unit="%"/>
2020-01-02 03:28:55 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time to GroupValueRead request for: 2/5/21
2020-01-02 03:28:55 WARNING (MainThread) [xknx.log] Could not sync group address ‘2/5/21’ from <Sensor name=“LF WEK Wohnen” sensor=“None/GroupAddress(“2/5/21”)/None/None” value=“None” unit="%"/>

This has been like this for about a week, and happens only when HA is restarted.

The circadian integration has been working great for the last couple of months, and I just installed HACS today, so would tend to disregard them as the root of the problem…

It woukd be nice if someone can help me to solve the problem.

Thanks!

Posts: 1

Participants: 1

Read full topic

@Meeseeks wrote:

The house I bought ended up having a boiler that’s way oversized for the three separate zones that they put in, so it short cycles a lot. To try and avoid that a little bit at least, I would like to open the basement zone (turn the heat on) whenever the main floor ecobee starts to kick in. I would like to use the homekit integration so that I don’t have to rely on ecobee’s cloud.

I’m not sure how to do this at all to be honest because I’m really new with Home Assistant coming from smartthings.

Basically, I think the easiest way to do this may be to set the basement to a highish temperature on a trigger when the main floor starts heating and then revert to the original settings after.

Posts: 1

Participants: 1

Read full topic

@tshin wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic