@straydog wrote:

‘’’
Running on RPI4 created from HA image hassos_rpi4-64-3.11.img.

Really appreciate help with this error.

Error has been appering for at least 10 releases, last good one @ R 0.95.
Appers for multiple manual integrations i.e. cover, xiaomi etc.

config file:

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: example.duckdns.org:8123

Text to speech

tts:

• platform: google_translate

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

xiaomi_aqara:
discovery_retry: 10
interface: !secret xiaomi_gateway
gateways:
- mac: !secret xiaomi_mac
key: !secret xiaomi_key
‘’’

‘’’
Log file:(Top of 32K file)

Unable to add log, please request. Thx
‘’’

Posts: 1

Participants: 1

Read full topic

@poudenes wrote:

Hi All,

Can someone tell me what to do?
Always worked and since 0.107.4 I get those errors:

2020-03-21 20:39:56 ERROR (SyncWorker_7) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xac5af130>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:40:34 ERROR (SyncWorker_18) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae24f850>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:40:58 ERROR (SyncWorker_14) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xad350850>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:41:30 ERROR (SyncWorker_14) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae0be4d0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:41:44 ERROR (SyncWorker_11) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xad611670>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:44:42 ERROR (SyncWorker_2) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection

2020-03-21 20:49:16 ERROR (SyncWorker_10) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae099f50>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:49:52 ERROR (SyncWorker_10) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xaf8a9730>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:54:29 ERROR (SyncWorker_11) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae116b30>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:57:30 ERROR (SyncWorker_15) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae1d24b0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:00 ERROR (SyncWorker_1) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae6475b0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:10 ERROR (SyncWorker_19) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xac7f67f0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:20 ERROR (SyncWorker_1) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xafd79030>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:30 ERROR (SyncWorker_15) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xad358f50>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:40 ERROR (SyncWorker_10) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae248370>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:58:50 ERROR (SyncWorker_3) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae4a8810>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:59:00 ERROR (SyncWorker_15) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xaf8e0730>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:59:10 ERROR (SyncWorker_5) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection

2020-03-21 20:59:20 ERROR (SyncWorker_4) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection

2020-03-21 20:59:30 ERROR (SyncWorker_14) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xac69c290>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 20:59:40 ERROR (SyncWorker_17) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xac5afed0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:03:18 ERROR (SyncWorker_1) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xafd8de70>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:07:56 ERROR (SyncWorker_11) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae2d4c90>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:12:32 ERROR (SyncWorker_5) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/ssh.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /ssh.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xaec15d70>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:12:42 ERROR (SyncWorker_15) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae2ea3b0>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:15:02 ERROR (SyncWorker_15) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/www.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /www.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xae1a3f70>, 'Connection to DOMAINNAME.COM timed out. (connect timeout=10)'))

2020-03-21 21:16:38 ERROR (SyncWorker_1) [homeassistant.components.rest.sensor] Error fetching data: http://DOMAINNAME.COM/vmail.json failed with HTTPConnectionPool(host='DOMAINNAME.COM', port=80): Max retries exceeded with url: /vmail.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection

Posts: 1

Participants: 1

Read full topic

@mortenmoulder wrote:

I am experiencing quite an annoying problem. I am trying to add my first REST sensor, and I simply cannot get it to work. My configuration.yaml file looks like this:

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

http:
  base_url: ......
  ......
...
...
...
sensor:
  - platform: rest
    resource: http://192.168.1.100:1234/calendar/GetEvents?take=5
    name: Calendar Events

If I try to curl the URL, it works fine. Check configuration: All good. Restarted HA: All good.

If I go to Configuration -> Entities, I cannot find it. I can’t find it under Developer Tools -> States either.

I simply cannot find it anywhere. I don’t have a lot of stuff in my Home Assistant environment, so I would easily be able to spot it under another name, but it’s not there.

What have I done wrong?

Posts: 4

Participants: 1

Read full topic

@gliena wrote:

Hello,

I am struggling to get my dimmer lights to work with my Siemens Logo. I was able to make it work with my non dimmable lights but here…

  - platform: template
    lights:
      living_room:
        friendly_name: "Living Room"
        level_template: "{{ states('sensor.sensorlivingroom') / 10 }}"
        value_template: "{{ states('sensor.sensorlivingroom') | int > 0 }}"
        turn_on:
          - service: modbus.write_register
            data:
              hub: hub1
              unit: 1
              address: 50
              value: 50
        turn_off:
          - service: modbus.write_register
            data:
              hub: hub1
              unit: 1
              address: 50
              value: 0
        set_level:
          - service: modbus.write_register
            data:
              hub: hub1
              unit: 1
              address: 50
              value: "{{ brigthness | int }}"

What are my issues:

• I can’t see the state of my lights level and value

• Turning off and turning on doesn’t work

If in run the service in the developer tools it works fine:

image1005×621 27.8 KB

value_template works fine in developer tools events.

I’ve been at it for hours so am grateful for any piece of advice.
thanks,

Posts: 5

Participants: 2

Read full topic

@Griesi wrote:

Hello all,

how should I do my automation to use my script? Or any other solution to do this? The entity_id should come from a group like group.light_floor_1 or group.cover_floor_1

  light_random_on_test:
    sequence:
      - delay: "00:00:{{ range(3, 15) | random }}"
      - service: light.turn_on
        data_template:
          entity_id: "{{ eid }}"
          
  cover_random_down_test:
    sequence:
      - delay: "00:00:{{ range(5, 25) | random }}"
      - service: cover.set_cover_position
        data_template:
          entity_id: "{{ eid }}"
          position: "{{ range(10, 23) | random }}"

Posts: 3

Participants: 2

Read full topic

@RandomHassUser wrote:

If I create an intermediate hass script that calls a python_script, the lovelace ui will allow me to call it via call-service, for example:

tap_action:
  action: call-service
  service: script.hass_script_intermediary

Is there a way I can call the python_script directly from lovelace? Lovelace doesn’t seem to show or allow them under entities.

Being able to call python_scripts directly would save a lot of time not having to create intermediary scripts for each python call. This example below will not work:

tap_action:
  action: call-service
  service: python_script.endpoint
    action: [payload]

Is there a different action to call a python_script, or does this functionality not exist in lovelace?

Posts: 3

Participants: 2

Read full topic

@Klagio wrote:

Hi, when I issue a command (RF switches from Broadlink) from the Broadlink app is normally very fast.

When I issue the same command from HASSIO the command is executed with huuuge delay, like 10-20 seconds, is random

Nothing in log, all other functions in HASSIO are same speed as always (fast).

Anyone else experiencing this? Any hints?

Posts: 1

Participants: 1

Read full topic

@The_Penguin wrote:

Hi all. I was reasonably happy with my layout both the Web interface and the mobile app.
Since the last upgrade that deprecated view and control from groups, it’s a hideous mess. I used to have items in the default view group show up at the top. Now, my groups are all still there, but there are 100s of entities at the top of the page. Even things that I don’t want to see ever are showing up (media player stuff etc.) And there are groups I didn’t configure showing up. And groups like group.all_lights that are set to hidden in customize.yaml are appearing.
So, I need to fix this. What’s the best way to go about it? I’ve never done any Lovelace config, should I scrap groups and custom configure Lovelace? Are there any guides to configuring the look and feel?

Also, I really want to get rid of, and never see again a bunch of entities. ANY media player. TV, Amazon Echo, Roku, Sonos. Just a personal preference, I don’t want them in HA. I have them set to ignore in the discovery section, but they insist on showing up.

Thanks!

ugly1141×562 131 KB

Posts: 1

Participants: 1

Read full topic

@seandavidson wrote:

Not sure if I missed something during updates but I can’t see to keep my icons from changing to the old ones. I have customize.yaml in my Configuration.yaml but it states I don’t. Below is my config setup. I can attache the entire if that helps.

default_config:
  customize: !include customize.yaml

Posts: 1

Participants: 1

Read full topic

@BENEKK wrote:

Hello to everyone! This is my first post

My setup looks like this: serveral z-wave devices connected to Vera Plus Controller and integrated into Home Assistant (v 0.107.4) with homebridge to HomeKit.

Everything works fine except Fibaro Dimmer 2. No metter if I turn it on via HA or HK - it always go to 100% brightness instead of previous brightness. Via Vera UI it works flawless. Is it possible to fix it? I know that I can set up the initial brithness level, but I would like not to do that.

Thanks,
Adam

Posts: 2

Participants: 2

Read full topic

@fufs wrote:

Hi,

I’m trying to setup MQTT with Home assistant, but it doesn’t want to work. I’m running Mosquitto broker (not add-on) with configured SSL/TLS, but with require_certificate set to false, since I want encryption, but not necesserily having to hand out certificate files to each client. I have also set a username and password authentication. I have tested this with a mobile app and two devices, and all checks out good (I can publish something on one device and the other device that is subscribed to that topic receives the message).

In Home Assistant I have added this code to configuration.yaml

mqtt:
  broker: 192.168.0.245
  port: 8883
  username: !secret MQTT_user
  password: !secret MQTT_passwd
  tls_insecure: true

and respectively username and password to the secrets.yaml file.

Now here comes the weird part. In the mosquitto log I can see

New connection from 192.168.0.245 on port 8883.,

but when I try to publish something from the MQTT tab in the Developer Tools the value doesn’t change. The same goes, when I try to subscribe to a topic. When I publish to it from another device, Home assistant doesn’t see any changes. I can confirm that the message has been in fact published with the second device.

I also tried to add a binary sensor to confirm, that there is something work with this added to configuration.yaml

binary_sensor:
  - platform: mqtt
    name: "Test Sensor"
    state_topic: "Test/toggle"
    payload_on: "ON"
    payload_off: "OFF"
    unique_id: test_binary

but had no luck either.

I’m running Home Assistant 0.107.3 with Hass.io as a Docker Container on a Raspberry Pi 3 B+. My Python version is 3.7.6, not sure that it would change anything. The MQTT broker is running on the same machine. What am I doing wrong?

Posts: 2

Participants: 1

Read full topic

@Eldudemeister wrote:

Hi, trying to cast a view other than my default view to my google home hub. I’ve set up a Lovelace panel for my tablet which is called Tablet but when I try and cast it, it say view not found. I’ve checked the raw config and the view path is tablet but it doesn’t seem to work when I try and call it?

Posts: 1

Participants: 1

Read full topic

@InacioSung wrote:

Hello, I am new here. Having trouble to set a script using broadlink.send service. This what I wrote in script.yaml:

temp_up:
sequence:
- service: broadlink.send
data:
host: 192.168.0.3
packet: “JgBYAAABJpEUNRQRFBAUERQRExEUERM2ExEUNRQ1FBETERQ1FDUUERM2FBAUNRQRFBAUERQREzYTERQ1FBETNhM2EzYTNhMRFAAFZAABJUkTAAw9AAEmSBQADQU=”

After that I check it and resta HA. But I do not know how to set it later. Could anyone help me?

Thanks in advance.

Posts: 6

Participants: 3

Read full topic

@Etienne_Vella wrote:

Hi,

I have a sounder working with 433MHZ and i managed to integrate it with rf bridge flashed with tasmota using button 4. Through the console of the rf bridge if i paste the command cmnd/RF_Bridge/RfKey4 the sounder would be activated.

I’ve configured mosquito to be integrated with Rf Bridge and senors which are using 433mhz are being correctly sent to home assistant.

So far so good.

The issue that i’m having when i try to trigger RfKey 4. This command isn’t being sent to my RF Bridge, and I can confirm it from the console of the RF Bridge. I’m using the following code in the automation section.

action:
  - service: mqtt.publish
    data:
      topic: cmnd/RF_Bridge/RfKey4
      payload: " "

Any Ideas whats the issues. The receiving part form the RF Bridge to Home Assistant is OK the issue is send from Home Assistant to RF Bridge.

Thanks,

Kindest Regards,
Etienne

Posts: 2

Participants: 2

Read full topic

@NChaos wrote:

Heya everyone,

as my first integration without UI-support I wanted to hook webhooks to change the source and powerstate of my TV using the hdmi_cec integration.

The “CEC Scanner” addon gave me:

[16:55:58] INFO: Starting CEC client scan...
opening a connection to the CEC adapter...
requesting CEC bus information ...
CEC bus information
===================
device #0: TV
address:       0.0.0.0
active source: no
vendor:        Sony
osd string:    TV
CEC version:   1.4
power status:  on
language:      deu
device #1: Recorder 1
address:       2.0.0.0
active source: no
vendor:        Pulse Eight
osd string:    CECTester
CEC version:   1.4
power status:  on
language:      eng
currently active source: unknown (-1)

My configuration.yaml contains this:

<auto generated stuff>
#integrations
hdmi_cec:
  devices:
    TV: 0.0.0.0
    Raspi: 2.0.0.0
    PC: 0.1.0.0

Now I want to call this to change to hdmi1 on the TV:

data:
  device: 0.1.0.0
service: hdmi_cec.select_device

Curiously, requesting anything with “0.” at the start does nothing while any other address changes the TV to hdmi2, the Raspi running HassOS.

Can someone tell me how to find the proper addresses to access the TV’s ports?
Thanks in advance for your help.

Posts: 1

Participants: 1

Read full topic

@A320Peter wrote:

I have several temperature sensors all around and I want an automation to send a notification in case any of these sensors report unusually high temperature. Some of my temperature sensors report the temperature in their state while others in attribute. I came up with a loop to go through all the sensors and check if any of them has ‘temperature’ in name or attribute. If any of them exceeds the threshold the automation is triggered and a notification to be sent.

To check the sensors I iterate through all the sensors with a for loop:

- alias: Unusually High Temperature Warning
  trigger:
    platform: template
    value_template: >-
          {%- set threshold = 40 -%}
          {%- for item in states.sensor %}
            {% if (item.attributes.temperature is defined and item.attributes['temperature']|int > threshold) or ("temperature" in item.entity_id|lower and ((item.state|int > threshold and item.state|int != 0))) or ("temperature" in item.name|lower and ((item.state|int > threshold and item.state|int != 0))) -%}
              {{ true }}
            {% endif %}
          {%- endfor -%}
  action:
  - service: notify.ios_xxx
    data:
        title: "Smart Home"
        message: "A sensor reports high temperature."

After saving and reloading automations CPU usage goes constantly above 30% and the entire Home Assistant system slows down and reacts with like 10-20 seconds delay. It seems the loop is killing the system. As soon as I remove the code and reload automations everything goes back to normal.

My question is why this is not working if a template trigger should only check for trigger condition if a sensor is changing it’s state?

I have another similar automation based on a suggestion from this forum, checking for dead nodes in z-wave network and this one works perfectly without any problem:

- alias: Z wave dead node detection and notification
  trigger:
    platform: template
    value_template: >
      {%- for state in states.zwave -%}
        {%- if state.state == "dead" or (state.attributes.is_failed is defined and state.attributes['is_failed'] == true) -%}
          {{ true }}
        {%- endif -%}
      {%- endfor -%}
  action:
    - service: notify.ios_xxx
      data_template:
        title: Smart Home
        message: "Dead nodes found"
        data:
          subtitle: "Z-wave Malfunction"

I created my temperature check automation based on this, but it doesn’t work properly as I mentioned before. Thanks for help!

Posts: 3

Participants: 2

Read full topic

@Ruald wrote:

I’m using Hassio and HA for several years. Today I needed to do a fresh install of my intel-nuc. I’ve backuped every config yaml in a Git repo.

So I installed a fresh Ubuntu 18.04 on the Nuc. After that I followed the steps on this manual:

sudo add-apt-repository universe

sudo -i
apt-get update
apt-get install -y software-properties-common apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
systemctl disable ModemManager
systemctl stop ModemManager
curl -fsSL get.docker.com | sh

curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s -- -m intel-nuc

After that I’ve created a Portainer docker container to see the Hassio containers and there logs etc.

The problem is that the supervisor is running great. The Home assistant is also running but when I go to ipadres:8123 of my server I see no result. When I look at the logs of the server with a lot of these errors.

2020-03-22 18:21:09 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 275, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp\_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method

I’ve googled and tried a lot but no solution. So of the suggestion comes about https of SSL errors, but I’m running with default config with no SSL of something.

Anyone a solution?

Posts: 2

Participants: 1

Read full topic

@tiebe111 wrote:

Hey there,

I’m using evohome and would like to do the following:

When I change the temperature on a thermostat, I want to set it back to 16 degrees after 2 hours.

Is this possible?

Thanks,

Tiebe

Posts: 1

Participants: 1

Read full topic

@soulman wrote:

Could anyone tell me which of these serial ports is the build in bluetooth on Asus Tinkerboard?

* serial:
  * /dev/ttyS3
  * /dev/ttyS2
  * /dev/ttyACM0
  * /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.07__Embed_with_CMSIS-DAP_L4200202-if00
  * /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.07__Embed_with_CMSIS-DAP_L4200202-if03
  * /dev/ttyS0
  * /dev/ttyS1
  * /dev/ttyACM1

Posts: 1

Participants: 1

Read full topic

@D34DC3N73R wrote:

I have an automation that dims lights in my living room when content is playing on my living room nvidia shield, and brightens lights when the state is paused, idle, or standby. This works great in plex. But the device state when using emby is reported as “paused”, even when the app is just opened and continues to stay that way even content is playing in the app. I have a thread on the emby forums, but don’t know much about how the device state is set, why it works in plex, and why it doesn’t in emby. Any tips or links to device state documentation would be appreciated.

Posts: 9

Participants: 2

Read full topic