@Tagazok wrote:

Hi, I am trying to create a sensor template but when it loads, I have an error.
Here is my template:

- platform: template
  sensors:
    motion_delay_corridor:
      friendly_name: "Corridor Lighting motion delay"
      delay_off:
        seconds: 15
      value_template: >-
        {{ is_state('binary_sensor.presence_2', 'on) }}

And here is the error I get:

Invalid config for [sensor.template]: [delay_off] is an invalid option for [sensor.template]. Check: sensor.template->sensors->motion_delay_corridor->delay_off. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/template/

I even tried to copy/paste the template from the integration page and get the same error I tried to write the whole think by hand in case it was a special character when I copy/paste but nothing works.

I am using Hass.io 193 with HassOS 3.7

Posts: 2

Participants: 1

Read full topic

@nate_hd wrote:

I see that wink service definitions were moved. I’m assuming that is what caused the problem. Logs are showing a failure to start the service. I set up wink so long ago, I’m not even sure what I did. I don’t see wink in the integrations. Do I need to delete wink and start over. I’m not really sure where to change service definitions after reading the change summary.

Since I don’t post that often…thanks for all those that work on Home Assistant. It has been a fun couple of years keeping up with this very active development.

Posts: 1

Participants: 1

Read full topic

@Teleportist wrote:

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

Posts: 1

Participants: 1

Read full topic

@dontpanic wrote:

Hi,

I’m just trying to follow the initial installation instructions for the mQTT addon. I have installed the addon, and started it.The second part of the instructions for configuration are -

1. Navigate in your Home Assistant frontend to Configuration -> Integrations .
2. Use the Add button and search for MQTT
3. Configure the Broker, Port, Username, Password and Submit.

When I go to Configuration** -> **Integrations there is already MQTT: Mosquito Broker under “Configured”, so I cannot use the Add button, it says you can only have one. So, I select the existing one and under the blue header it says “This integration has no devices”, there seems to be no way that I can see to configure it.In the system options button it just pops up another window that doesn’t allow me to do anything.

Next I tried configuring the /configuration.yaml and adding the MQTT configs in there

mqtt:
broker: 192.168.88.66
username: myusername
password: mypassword
discovery: true
discovery_prefix: homeassistant
birth_message:
  topic: 'hass/status'
  payload: 'online'
will_message:
  topic: 'hass/status'
  payload: 'offline'

I did a reboot, and looked at the log file and I have this output -

2020-01-11 15:15:24 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=1 from 2020-01-04 08:25:49.190720)
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.config] Invalid config for [discovery]: expected a dictionary for dictionary value @ data[‘discovery’]. Got True. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/discovery/
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for discovery: Invalid config.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for broker: Integration not found.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for will_message: Integration not found.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for password: Integration not found.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for birth_message: Integration not found.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for username: Integration not found.
2020-01-11 15:15:31 ERROR (MainThread) [homeassistant.setup] Setup failed for discovery_prefix: Integration not found.
2020-01-11 15:15:34 ERROR (MainThread) [hbmqtt.broker] Broker startup failed: [Errno 98] error while attempting to bind on address (‘0.0.0.0’, 1883): address in use
2020-01-11 15:15:34 ERROR (MainThread) [homeassistant.components.mqtt.server] Error initializing MQTT server

A couple of questions -

1. do you configure the MQTT addon within the hassio web browser, or via the configuration.yaml?
2. I have 2 config files, one in /root/config and one in /config. I’m using the hassio installer on a pi3, which is the correct config file to use?
3. there is no mosquitto service running, should I see a separate service listed from ps?

Thanks for any suggestions

Posts: 1

Participants: 1

Read full topic

@Robkiller1 wrote:

Setup of platform wyzesense is taking longer than 60 seconds. Startup will proceed without waiting any longer

just started after restart any ideas? All my wyze stuff is error ed and not showing as you can tell from the error.

using PI4 hass.io version 103.6

2020-01-10 22:33:43 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-10 22:33:47 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for wyzesense 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-10 22:33:57 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of platform wyzesense is taking over 10 seconds.
2020-01-10 22:34:47 ERROR (MainThread) [homeassistant.components.binary_sensor] Setup of platform wyzesense is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2020-01-10 22:35:38 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/wyzesense/binary_sensor.py", line 94, in setup_platform
    result = ws.List()
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 507, in List
    sensors = self._GetSensors()
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 479, in _GetSensors
    self._DoCommand(Packet.GetSensorList(count), cmd_handler, timeout=self._CMD_TIMEOUT * count)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 384, in _DoCommand
    raise TimeoutError("_DoCommand")
TimeoutError: _DoCommand

Posts: 2

Participants: 2

Read full topic

@coza73 wrote:

Out of the blue I could not get to the frontend. It now continuously shows ‘loading data’

In the logs whenever I try and load the frontend I get the error:-

ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139961146590352] Unable to serialize to JSON: Out of range float values are not JSON compliant

It then lists all of my entities in the logs.

It was on version 0.103.6 when this happened. I have tried going back to various previous versions with no luck.
I am running the stock docker image.

I cannot list the full error and entity list because it exceeds the maximum character limit per post.

Posts: 1

Participants: 1

Read full topic

@turtleboy133 wrote:

Under the Z-Wave Network Management node list, one of the items is "Uknown Node 8 (Node:7 Probe). It keeps showing up even after a reboot. I triad manually setting is_failed: true via the Developer Tools and then selecting “Remove Failed Node” under the network management page. However, the node remains and it is listed as “Initializing (Probe)”. I’m confused about what to do to get this removed from the list. Could it be that this is an old Z-wave device that I no longer have?

Posts: 1

Participants: 1

Read full topic

@notspam wrote:

I can obtain values of a sensor using the REST API from the URL with the following format
URL=“http://HA:8123/api/states/sensor.some_sensor”

I have a ZHA thermostat that is recognized by HA as a DEVICE but it does not auto-populate the device “sensor” and “config values” i.e. the device is not recognized as an entity or sensor.

Under Device Management I can run ZHA commands to read and write values to my zha thermostat. What is the equivalent URL string I can use to issue the ZHA commands to read/write my values?

My device has the following format:
devices.clusters.attributes.values

Does the REST API allow me to send commands directly to devices?

Posts: 1

Participants: 1

Read full topic

@jjudson wrote:

I’m confused by this line in the Lovelace yaml setup:

<config>/ui-lovelace.yaml

Does ui-lovelace.yaml need to go in a “config” directory? If so, I looked all over my tree and couldn’t find one.

Please advise. Thanks!

Posts: 3

Participants: 2

Read full topic

@SylvainGa wrote:

So because I fiddled with it too much, I had three times my phone registered in Home Assistant and the log complained that it found duplicate device name Pixel 3 XL. There was actually three of them. They showed up in Developer Tools, in Entities, Integrations and Devices. Deleting the duplicates from there did nothing. They always came back. I believe it’s because of the Integration still had them and deleting it from there told me I needed to stop the Mobile App integration to remove them. The thing is, there is no ‘Mobile App’ integration category since each phone is listed individually (unlike a Hue hub) so I couldn’t actually stop it without causing other side effect.

So, to fix it, and this is where I’m asking if I did something wrong, I went into the .storage folder, stopped hassio, removed the duplicate entries from the following files (took a backup of each files first as well as a hassio snapshot, just in case) and restarted hassio

core.config_entries
core.device_registry
core.entity_registry
core.restore_state

The duplicates are now gone and the log is no longer complaining. The lone Pixel 3 XL is still talking to hassio from what I can see (battery level is following what my phone is showing).

So, did I do something that I’ll regret later on by causing inconsistencies or something else?

Thanks.

Posts: 2

Participants: 2

Read full topic

@SylvainGa wrote:

Hi, so this is my next step in home automation and need help again.

I have set up my thermostats (baseboard heating) to start at a specific time of day depending if it’s a weekday or weekend and if the person is present or not. This is working fine. Now I want to take it a step further.

I want to adjust the start time based on the outside temperature. Colder it is (living in Canada so it can get pretty cold), sooner it will start so by the time the person has to get up, the room will be at a comfortable level.

I haven’t used template enough do figure it out. I want to do something like this (in C syntax):

start_time_in_minutes + (outside_temp < 0 ? -outside_temp * 2 : 0)

So if start time is 6:00:00 (360 minutes from midnight) and the temperature is -15C, it will start at 5:30:00 (360 + (-15) * 2 = 330)

Can it be done?

Thanks

Posts: 9

Participants: 2

Read full topic

@jjudson wrote:

I’m still very new to this system, but HA really has me interested in expanding my hobby playtime into something new. So pardon if this is a very basic – or even ignorant – question.

I am thinking I’d like to build a front end set of browser-based tablet screens for my system, rather than use the Lovelace interface. Can this be accomplished solely using CSS or would I also need other programing and scripting knowledge to do so?

I learned basic CSS years ago – and have forgotten most of it. But if I can do this by learning CSS, I can focus on spending time doing that. If I need to know other scripting or programing languages to do this in conjunction or better altogether, what would be the best route?

Thanks ahead!

Posts: 3

Participants: 3

Read full topic

@namexless wrote:

Hello!

I would like to kindly ask for your assistance with the problem that I experienced today.
Configurator add-on have just stopped working for me. I don’t even know what was the reason and don’t have any clue where to look for possible solutions either.
Can you please help me with debugging it?

I tried:
-> rebooting host
-> restarting HA
-> uninstalling & installing add-on again

No errors in logs, just a couple of errors in chrome dev tools. Although I don’t understand them at all… (below)

My setup: RPi 4 + SSD + Raspbian + docker + hassio.

Link to HA log: https://pastebin.com/rXfaDCN1
Link to Configurator add-on log: https://pastebin.com/4C7JXgkx
Link to Chrome dev tools console log: https://pastebin.com/L6g1ZGs2

Posts: 5

Participants: 2

Read full topic

@metbril wrote:

I’m trying to use an advanced state filter with my entity filter card:

What I want is a sensor to show only when it is above or below a certain treshold. For example, I want to show the outdoor temperature in a “mobility” card when it lowers below 4 Celcius. This is the warn for slippery roads.

configuration.yaml

sensor:
  - platform: yr
    monitored_conditions:
      - symbol
      - temperature

lovelace

...
cards:
  - type: entity_filter
    entities:
      - sensor.yr_temperature
    state_filter:
      - value: "4"
        option: "<="
...

alternate syntaxes tried:

    state_filter:
      - value: '4'
        option: '<='

    state_filter:
      - value: 4
        option: <=

No matter what syntax I try for the state filter (with or without quotes), the sensor only shows when the string equivalent of the value exactly matches the temperature.

Is the option: actually working? Is the documentation outdated?

Any help is appreciated.

Posts: 3

Participants: 2

Read full topic

@ReDaLeRt wrote:

Hi.

I’m trying to manage all the alarm entities and my alarm device, from two different sources:

• Alarm card, in the front end (both home_alarm and alexa_guard ones)
• RF remotes, monitored from the binary_sensor.alarm_armar

This automation:

- alias: 'Gere o estado do alarme'
  trigger:
    - platform: state
      entity_id: binary_sensor.alarme_armar
    - platform: state
      entity_id: alarm_control_panel.home_alarm, alarm_control_panel.alexa_guard_9fc9e
  condition:
    condition: or
    conditions:
    - condition: template
      value_template: >
        {% set usefull_states = 'on', 'off' %}
        {{ states('binary_sensor.alarme_armar') in usefull_states }}
    - condition: template
      value_template: >
        {% set usefull_states = 'disarmed', 'armed_away', 'armed_night' %}
        {{ states('alarm_control_panel.home_alarm') in usefull_states }}
    - condition: template
      value_template: >
        {% set usefull_states = 'disarmed', 'armed_away' %}
        {{ states('alarm_control_panel.alexa_guard_9fc9e') in usefull_states }}
  action:
    - service_template: >
          {% if is_state('binary_sensor.alarme_armar', "on") and trigger.entity_id == binary_sensor.alarme_armar %}
            alarm_control_panel.alarm_arm_away
          {% elif is_state('binary_sensor.alarme_armar', "off") and trigger.entity_id == binary_sensor.alarme_armar %}
            alarm_control_panel.alarm_disarm
          {% else %}
             broadlink.send
          {% endif %}
      data_template: >
          {% if trigger.entity_id == binary_sensor.alarme_armar %}
            {{ entity_id:
               - alarm_control_panel.house_alarm
               - alarm_control_panel.alexa_guard_9fc9e }}
          {% else %}
            {{ host: !secret broadlink_host
               packet: !secret automation_alarm_rf_broadlink }}
          {% endif %}

Gets this error:

Invalid config for [automation]: expected a dictionary for dictionary value @ data['action'][0]['data_template']. Got None. (See /config/configuration.yaml, line 2584). Please check the docs at https://home-assistant.io/integrations/automation/

Could get some help, please?

Thanks.

Posts: 2

Participants: 2

Read full topic

@Ekstrom wrote:

Hi!

I need to add multiple conditions to one automation. If “device_tracker.Mua_iphone” and “device_tracker.Mark_iphone” is “away” (everybody are away) I want to play the sound fanfar.mp3. If Mua_iphone are “home” i want to play MUA.mp3. If device_tracker.Mark_iphone are “home” I want to play MARK.mp3.

This is my automation on the front door today:

- id: '1570641644419'
  alias: Automation_Front_Door
  trigger:
  - entity_id: binary_sensor.sensor_front_door
    from: 'off'
    platform: state
    to: 'on'
  condition: []
  action:
  - service: media_player.play_media
    data_template:
      entity_id: media_player.baa
      media_content_id: http://soundking.com/sounds/fanfar.mp3
      media_content_type: audio/mp3
  - service: media_player.volume_set
    data_template:
      entity_id: media_player.baa
      volume_level: 0.5

Posts: 4

Participants: 2

Read full topic

@silver323 wrote:

I’ve two picture glances in horizon stack. The first works great but the second won’t showing the image?? Who can help me in the right direction

type: horizontal-stack
cards:
  - type: picture-glance
    entity: person.dennis
    entities:
      - entity: device_tracker.gm1913
        icon: 'mdi:cellphone-android'
      - entity: sensor.battery_phone_dennis
        icon: 'mdi:battery'
    state_image:
      home: /local/person/Dennis.jpg
      not home: /local/person/Dennis.jpg
    title: Dennis
  - type: picture-glance
    entity: person.karin
    entities:
      - entity: device_tracker.galaxy_a50
        icon: 'mdi:cellphone-android'
    state_image:
      home: /local/person/Karin.jpg
      not home: /local/person/Karin.jpg
    title: Karin

Posts: 3

Participants: 2

Read full topic

@millercentral wrote:

I wonder if anyone with any JSON-based web API integration experience for HA might consider creating an integration for the TeslaFi.com website API documented here: https://teslafi.com/api.php

The API itself seems very simple - it returns a json blob with a bunch of data related to your vehicle, and can issue a few basic commands to the car.

Why is this interesting if there is already a Tesla car API integration? Two reasons: (1) the API returns not only car data, but some additional data derived by TeslaFi.com that is interesting, and more importantly (2) TeslaFi.com has some very good polling algorithms that when setup correctly don’t get in the way of the car sleeping or excessively drain the battery. Conversely, the existing Tesla integration seems to poll the car indiscriminately every 300 seconds (or what you set the poll interval to be) which can have a big impact on sleep states/battery.

Thanks!

Posts: 1

Participants: 1

Read full topic

@jeffkjolley wrote:

Hi all,
I’ve been experiencing some pretty bad delays and general instability on my Z-Wave network using the stock HA Z-Wave integration. Most of my Z-Wave devices are newer than the openzwave 1.4 device database. Anyway, my issues are starting to negatively impact my SAF (spouse approval factor). I guess I’m just looking for general advice from someone with maybe a bit more insight into what’s going on with HA Z-Wave development. Do you think I should take the time to switch my Z-Wave integration over to ZWave2MQTT with openzwave 1.6, or should I sit tight and wait to see what happens with QT-OpenZWave in the next month or two?

Any advice is appreciated.

-Jeff

Posts: 4

Participants: 4

Read full topic

@Bazmundi wrote:

I added a notification service as an action to an automation via the UI.

I get the following error upon saving of the automation:

Message malformed: expected dict for dictionary value @ data['action'][1]['data']

So by the UI it have entered:

Action Type: Call Service
Service: notify.notify
Service data: Zone 1 sprinkler turned off

YAML reads:

alias: ''
service: notify.notify
data: Zone 1 turned off

I have also tried:

alias: ''
service: notify.notify
data: "Zone 1 turned off"

alias: ''
service: notify.notify
data: [Zone 1 turned off]

alias: ''
service: notify.notify
data: ["Zone 1 turned off"]

When I try the following the automation editor saves BUT:

alias: ''
service: notify.notify
data: {{ "Zone 1 turned off" }}

BUT it actually saves:

alias: ''
service: notify.notify
data: '[object Object]': null

So, I assume my problem is formatting the data.

When the automation runs, no notification turns up in the notification panel.

I have also a ClickSend notify panel setup, so the help does not clarify how to send and sms, only how to setup ClickSend. I have recipient setup in the config in configuration.yaml so I an not expecting to have to put the phone number in the service data.

So, either of two things might be the problem. My data format or Clicksend setup.

I have seen this data problem in other attempts to configure other things so I am happy to start with sorting out that so, first things first. Any hints on how the data should be formatted please? Is there a help file perhaps that illuminates the matter?

Cheers,
Baz

Posts: 3

Participants: 2

Read full topic