@Dreamoffice wrote:

hello
i have setup a input_select to pick scenes

- alias: LichtWohnzimmer                            
  initial_state: true
  trigger:
  - platform: state
    entity_id:
    - input_select.szenen_wohnzimmer
  action:
  - service: scene.turn_on
    data_template:
      entity_id: >
        {% if trigger.entity_id == 'input_select.szenen_wohnzimmer' %}
          {% if trigger.to_state.state == 'Normal' %}
            scene.normal
          {% elif trigger.to_state.state == 'Abends' %}
            scene.abends
          {% elif trigger.to_state.state == 'Pink' %}
            scene.pink
          {% elif trigger.to_state.state == 'Hell' %}
            scene.hell
          {% elif trigger.to_state.state == 'Blau' %}
            scene.blau
          {% elif trigger.to_state.state == 'Frühling' %}
            scene.fruehling
          {% else %}
            scene.aus
          {% endif %}
        {% endif %}

this is working ok.
now i want to toggle through the input_select options with an Aqara switch. but this automation is not working.

- id: Aqara Schalter 2 linke Schaltflaeche kurz
  alias: Licht szenen togglen
  trigger:
  - platform: mqtt
    topic: zigbee2mqtt/xiaomi_schalter_wohnzimmer
  condition:
  - condition: template
    value_template: '{{ "left" == trigger.payload_json.click }}'
  action:
    service: input_select.select_option
    data_template:
      entity_id: >
        {% if is_state("input_select.szenen_wohnzimmer", "Normal" )%}
          'Abends'
        {% elif is_state("input_select.szenen_wohnzimmer", "Abends" )%}
          'Pink'
        {% elif is_state("input_select.szenen_wohnzimmer", "Pink" )%}
          'Hell'
        {% elif is_state("input_select.szenen_wohnzimmer", "Hell" )%}
          'Normal'
        {% endif %}

where is the mistake in this automation? is there another way to handle this?

Posts: 1

Participants: 1

Read full topic

@icemtel wrote:

Hey, can’t figure out why this simple automation won’t work.

- id: '1586808364588'
  alias: Set Alarm
  description: ''
  trigger:
  - platform: mqtt
    topic: hass/alarm/set
  condition: []
  action:
  - service: timer.start
    entity_id: timer.alarm_clock
    data_template:
      duration: '{{trigger.payload_json.value}}'

At first I tried to use data instead of data_template, because that’s what automation editor does, but that also doesn’t work.

Error message

Set Alarm: Error executing script. Invalid data for call_service at pos 1: offset {{trigger.payload_json.value}} should be format 'HH:MM' or 'HH:MM:SS' for dictionary value @ data['duration']

Payload example

{
    "value": 34853,
    "name": "BeforeAlarm",
    "count": 1
}

So it doesn’t parse '{{trigger.payload_json.value}}' into a numerical value? Can’t figure out why

Posts: 4

Participants: 2

Read full topic

@Skooby wrote:

Hi guys,

I currently have HA running on a windows pc with virtual box and its going great. I also have mosquitto MQTT running within HA. Recently my system crashed and my tasmota light switches were very sluggish when pressing the actual light switch buttons. This was because they couldnt connect to MQTT and were continually trying. As far as I can make out there is no way to stop this happening if MQTT goes down (was hoping there was an option for tasmota that stopped looking after so long). This got me looking at running an MQTT on a pi instead. I already have an MQTT running on a pi from another project. From reading about HA, to get it to use this pi MQTT all I have to do is go in to the configuration and add:
mqtt:
broker: CLOUDMQTT_SERVER
port: CLOUDMQTT_PORT
username: CLOUDMQTT_USER
password: CLOUDMQTT_PASSWORD

obviously I need to add my own details. It should then be a case of disabling the mosquitto HA MQTT and all should be good after changing all my tasmota devices to look at the correct ip. IS this correct? I am a little reluctant to just do it in case I completely screw it up so just wanting a sanity check on what I am saying.

Thanks

Posts: 1

Participants: 1

Read full topic

@kses wrote:

I really like the new improvements with cards filling out space. It works great execpt for one part where I have a horizontal stack that only has conditional stacks. When empty it results in an extra white space. Someone knows how to fix it?

This is the card that is empty in the picture.

          - type: horizontal-stack
            cards:
            - type: conditional
              conditions:
                - entity: binary_sensor.you_have_mail
                  state: 'on'
              card:
                type: entity-button
                entity: binary_sensor.you_have_mail
                icon: mdi:email
                name: You have mail

            - type: conditional
              conditions:
                - entity: group.all_plants
                  state: 'problem'
                - entity: sensor.all_plant_status_moisture
                  state: 'off'
              card:
                type: entity-button
                entity: group.all_plants
                icon: mdi:flower-tulip
                name: Check the flowers
                tap_action:
                  action: call-service
                  service: input_boolean.turn_on
                  service_data:
                    entity_id: input_boolean.mute_flowers

image1890×470 37 KB

Posts: 1

Participants: 1

Read full topic

@kokein wrote:

Hello,

Can’t handle this problem by myself. Maby some one can help here?

I have new “Wemos D1 mini v2” with ESP8266-12F on board and “Wemos DHT22 Shield”.
It should work “out of the box” but it does not.

I think the board hase 10kOhm pullUp resostor allready soldered?

I’ve cheked differet GPIO’s, all my solder joints, all connections,my device if flashed correctly.
I can find it on ESPHome, it is discovering DTH22, but on the end of line im getting this:

[20:08:27][W][dht:126]: Requesting data from DHT failed!
[20:08:27][W][dht:060]: Invalid readings! Please check your wiring (pull-up resistor, pin number) and consider manually specifying the DHT model using the model option.
[20:08:27][D][sensor:092]: ‘Temp_out’: Sending state nan °C with 1 decimals of accuracy
[20:08:27][D][sensor:092]: ‘Hum_out’: Sending state nan % with 0 decimals of accuracy

And non of found on the web solutions helped me ,it default send signal from dht22 by D4 line, I also tried to bypass D4 and and use direct solder. …and nope…

What I’m missing?
In HomeAssistant my entitie get: Unavailable

This is my code for ESPHome:

esphome:
  name: sensor_kkn
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: "My Wifi"
  password: "My Pass"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Sensor Kkn Fallback Hotspot"
    password: "9xw9e5w4Uj84"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

# Example configuration entry
sensor:
  - platform: dht
    pin: D1
    model: DHT22
    temperature:
      name: "Temp_out"
    humidity:
      name: "Hum_out"
    update_interval: 30s

And this is output log: (here is for D1 pin but i get this on all tested GPIOs)

[20:08:21][C][wifi:415]: WiFi:
[20:08:21][C][wifi:283]:   SSID: 'My WiFi'[redacted]
[20:08:21][C][wifi:284]:   IP Address: 192.168.0.158
[20:08:21][C][wifi:286]:   BSSID: 90:5C:44:A0:34:DC[redacted]
[20:08:21][C][wifi:287]:   Hostname: 'sensor_kkn'
[20:08:21][C][wifi:291]:   Signal strength: -60 dB ▂▄▆█
[20:08:21][C][wifi:295]:   Channel: 11
[20:08:21][C][wifi:296]:   Subnet: 255.255.255.0
[20:08:21][C][wifi:297]:   Gateway: 192.168.0.1
[20:08:21][C][wifi:298]:   DNS1: 62.179.1.63
[20:08:21][C][wifi:299]:   DNS2: 62.179.1.62
[20:08:22][C][logger:175]: Logger:
[20:08:22][C][logger:176]:   Level: DEBUG
[20:08:22][C][logger:177]:   Log Baud Rate: 115200
[20:08:22][C][logger:178]:   Hardware UART: UART0
[20:08:22][C][dht:017]: DHT:
[20:08:22][C][dht:018]:   Pin: GPIO16 (Mode: INPUT)
[20:08:22][C][dht:020]:   Auto-detected model: DHT22
[20:08:22][C][dht:027]:   Update Interval: 10.0s
[20:08:22][C][dht:029]:   Temperature 'Temp_out'
[20:08:22][C][dht:029]:     Unit of Measurement: '°C'
[20:08:22][C][dht:029]:     Accuracy Decimals: 1
[20:08:22][C][dht:029]:     Icon: 'mdi:thermometer'
[20:08:22][C][dht:030]:   Humidity 'Hum_out'
[20:08:22][C][dht:030]:     Unit of Measurement: '%'
[20:08:22][C][dht:030]:     Accuracy Decimals: 0
[20:08:22][C][dht:030]:     Icon: 'mdi:water-percent'
[20:08:22][C][captive_portal:169]: Captive Portal:
[20:08:22][C][ota:029]: Over-The-Air Updates:
[20:08:22][C][ota:030]:   Address: sensor_kkn.local:8266
[20:08:22][C][api:095]: API Server:
[20:08:22][C][api:096]:   Address: sensor_kkn.local:6053
[20:08:27][W][dht:126]: Requesting data from DHT failed!
[20:08:27][W][dht:060]: Invalid readings! Please check your wiring (pull-up resistor, pin number) and consider manually specifying the DHT model using the model option.
[20:08:27][D][sensor:092]: 'Temp_out': Sending state nan °C with 1 decimals of accuracy
[20:08:27][D][sensor:092]: 'Hum_out': Sending state nan % with 0 decimals of accuracy

Please give me some advice.

All the best!
Nick

Posts: 1

Participants: 1

Read full topic

@membersound wrote:

If I want to evaluate the response of a GET rest call, I have to create a sensor with platform: rest, correct?

If so: how can I evaluate that rest call only once a day?
In may case, I want to fetch the battery status of a device in my home from its rest endpoint. But it would be sufficient to fetch it only once every 24h (and not every 30s which is the default for a sensor).

Is the solution to add a scan_interval: 86400 to the sensor config?
And then create an automation on that sensor to check the state (of the response)?

Posts: 1

Participants: 1

Read full topic

@carltonb wrote:

Because I am now working from home I have created a time set up in lovelace which looks like this.

I have used the following to code as a sensor.

  - platform: worldclock
    name: New York
    time_zone: America/New_York
  - platform: worldclock
    name: Waukesha
    time_zone: America/Chicago
  - platform: worldclock
    name: Phoenix
    time_zone: America/Phoenix
  - platform: worldclock
    name: Los Angeles
    time_zone: America/Los_Angeles

and this is my lovelace

  - type: horizontal-stack
    title: Times
    cards:
      - type: glance
        entities:
          - sensor.new_york
          - sensor.waukesha
          - sensor.phoenix   
          - sensor.los_angeles

I have tried many methods on the forum to change these times to a 12 hr format in my template.
I can change them but they do not update, or my code changes all of them to the same time.
Here is a sample of what I have tried.

      simple_time_ny:
        friendly_name: 'New York Time'
        entity_id: sensor.new_york
        value_template: '{{ as_timestamp(now()) | timestamp_custom("%I:%M %p") }}'

Does any one have a solution to make all the times in three different time zones to go to a 12hr format and update.
Thanks,
carltonb

Posts: 1

Participants: 1

Read full topic

@membersound wrote:

I created a simply group to check if there is somebody at home, or nobody:

family:
  name: Family Devices
  entities:
    - device_tracker.husband
    - device_tracker.wife

I nobody is at home, the group switches to not_home. If at least one is at home, the group switches to home

So far so good, but how can I let the group be shown as on in the dashboard if anybody is at home? Because currently, the groups is shown as off.

Posts: 1

Participants: 1

Read full topic

@njsaunders wrote:

Hi -

I’m trying to write an automation to turn my Amazon FireTV Cube On and play a specific video on Netflix.

So far I’ve:

• Enabled ADB on the Cube
• Verified that I can ping it
• Installed adb-homeassistant in the virtualenv
• Added the following to configuration.yaml:

media_player:
  - platform: androidtv
    name: Fire TV Cube
    host: 192.168.0.17

If I go to the services page and run service androidtv.adb_command against the entity with data:

entity_id: media_player.fire_tv_cube
command: HOME

It returns to the home screen: All good: but thats about all I can get it to do.

I’d like to get it to play a video on Netflix. I’ve tried calling service media_player.play_media with data:

entity_id: media_player.fire_tv_cube
media_content_id: "netflix://title/80092835"
media_content_type: video

But nothing happens - No error messages, nothing.

Any help appreciated!

Thanks,

Neil

Posts: 1

Participants: 1

Read full topic

@Cheesenwine wrote:

I can’t find a list of different available data types for the template sensor. I have the following template derived from a Modbus output, but the result is an int/ whole number. Does anyone have a reference to all the different available data types to choose from?

      - name: SMA Solar Power
        hub: SB5
        unit_of_measurement: kW
        slave: 3
        register: 30775
        count: 2
        data_type: uint
        scale: 0.001
        precision: 3

  - platform: template
    sensors:
      sma_solar_power_filtered:
        friendly_name: "Solar Power"
        unit_of_measurement: 'kW'
        value_template: >-
          {% if (states('sensor.SMA_Solar_Power') | int >= 20000) %}
            0
          {% else %}
            {{(states('sensor.SMA_Solar_Power') | int)}}
          {% endif %}  

Posts: 1

Participants: 1

Read full topic

@bombleadam wrote:

Hi All,

New here. Just spend the easter weekend setting up HA. Got most things working but my Yamaha MusicCast only shows as an entity, not a device. When I view it, I just see “This entity does not have a unique ID, therefore its settings cannot be managed from the UI.”

Is that normal? I’ve read the musiccast integration and there are no options to set one. Any help or advice much appreciated. Config below.

#Yamaha
  - platform: yamaha_musiccast
    host: 192.168.1.129

Posts: 1

Participants: 1

Read full topic

@riggs498 wrote:

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

Posts: 1

Participants: 1

Read full topic

@riggs498 wrote:

Greetings,

I have had to move to hass.io since hassbian is no longer working. Attached to the bottom of the message is the XML file. I can not get cat filename to work. All I can get is command line error and no other message. Is there something special you have to do to get command line to work? Or is there another way I can get this XML file to load as sensors?

Any suggestions is welcome.

<?xml version="1.0" encoding="UTF-8" ?>
<solar>
	<solardata>
		<source url="http://www.hamqsl.com/solar.html">N0NBH</source>
		<updated> 14 Apr 2020 0019 GMT</updated>
		<solarflux>70</solarflux>
		<aindex> 5</aindex>
		<kindex> 1</kindex>
		<kindexnt>No Report</kindexnt>
		<xray>  n/a   </xray>
		<sunspots>0</sunspots>
		<heliumline> 91.8</heliumline>
		<protonflux>1.00E+05</protonflux>
		<electonflux>1.00e+05</electonflux>
		<aurora></aurora>
		<normalization></normalization>
		<latdegree>No Report</latdegree>
		<solarwind>372.0</solarwind>
		<magneticfield>  0.5</magneticfield>
		<calculatedconditions>
			<band name="80m-40m" time="day">Fair</band>
			<band name="30m-20m" time="day">Fair</band>
			<band name="17m-15m" time="day">Poor</band>
			<band name="12m-10m" time="day">Poor</band>
			<band name="80m-40m" time="night">Good</band>
			<band name="30m-20m" time="night">Fair</band>
			<band name="17m-15m" time="night">Poor</band>
			<band name="12m-10m" time="night">Poor</band>
		</calculatedconditions>
		<calculatedvhfconditions>
			<phenomenon name="vhf-aurora" location="northern_hemi">Band Closed</phenomenon>
			<phenomenon name="E-Skip" location="europe">Band Closed</phenomenon>
			<phenomenon name="E-Skip" location="north_america">Band Closed</phenomenon>
			<phenomenon name="E-Skip" location="europe_6m">Band Closed</phenomenon>
			<phenomenon name="E-Skip" location="europe_4m">Band Closed</phenomenon>
		</calculatedvhfconditions>
		<geomagfield>VR QUIET</geomagfield>
		<signalnoise>S0-S1</signalnoise>
		<fof2> 4.8</fof2>
		<muffactor> 3.07</muffactor>
		<muf>NoRpt</muf>
	</solardata>
</solar>

Thanks

Posts: 1

Participants: 1

Read full topic

@riggs498 wrote:

I made and arduino lighting detector that sends information down the usb port. It sends a 3 digit number starting with the middle around 512 then moves up and down. That is not the issue. I create the sensor. I can see it in the lovelace card. When I click on it. It will not give a history. It stops the system. It will not keep running. So then I tried to create it with a value_template.

- platform: serial
  baudrate: 115200
  serial_port: /dev/ttyACM0
  value_template: "{{ states('sensor.serial_sensor') | float }}"

This keeps telling me unknown on the data. I tried with out the float and still did the same thing. When lighting comes. I need to see the results on the graph to get this to do automations. But I have to see the numbers. There come in so fast that you can no see it on a bar graph. I need a line graph. But how can I get this to start displaying the numbers in a usable way to not keep the system from slowing down.

Any ideas welcome.

Thanks

Posts: 2

Participants: 2

Read full topic

@medichugh wrote:

Anyone who is running Hassio on Proxmox have the ProxmoxVE integration successfully running on your system? I have followed the install guide for the integration and get the entities (NAS temp, NAS cpu temp, and NAS fan speed) to show up in HA, but no data. Any thoughts or help would be greatly appreciated. Below is system info, config.yaml, and logviewer.

SYSTEM INFO:
|arch|x86_64|
|dev|false|
|docker|true|
|hassio|true|
|os_name|Linux|
|os_version|4.19.107|
|python_version|3.7.7|
|timezone|America/Chicago|
|version|0.108.3|
|virtualenv|false|

### Lovelace

|dashboards|2|
|mode|storage|
|resources|11|
|views|9|

My config.yaml:

proxmoxve:
  - host: !secret pve_host
    username: !secret pve_user
    password: !secret pve_pw
    port: !secret pve_port
    verify_ssl: false
    realm: pve
    nodes:
      - node: pve
        vms:
          - 100

HA logviewer ouputs the following:

2020-04-13 18:57:24 ERROR (SyncWorker_1) [homeassistant.components.command_line.sensor] Command failed: ssh root@192.168.1.163 ‘( sensors )’ > /tmp/temp_nas && cat /tmp/temp_nas | head -13 | tail -1 | cut -c15-22

2020-04-13 18:57:24 ERROR (SyncWorker_16) [homeassistant.components.command_line.sensor] Command failed: ssh root@192.168.1.163 ‘( sensors )’ > /tmp/fan_nas && cat /tmp/fan_nas | head -12 | tail -1 | cut -c13-17

2020-04-13 18:58:25 ERROR (SyncWorker_5) [homeassistant.components.command_line.sensor] Command failed: ssh root@192.168.1.163 ‘( sensors )’ > /tmp/cpu_nas && cat /tmp/cpu_nas | head -3 | tail -1 | cut -c15-22

Any help would be great.

Posts: 1

Participants: 1

Read full topic

@john_bernstein wrote:

Greetings HA folks,

I’m running HA 0.108.3 (after getting back to tinkering with it). I have a problem where HA and my Insteon Hub 2245 stop talking after an hour or two.

2020-04-05 21:06:00 ERROR (MainThread) [insteonplm] Reconnect to Hub (TimeoutError)e
2020-04-05 21:06:00 WARNING (MainThread) [insteonplm.plm] Lost connection to Insteon Modem: Truee

One remedy I’ve tried is re-starting HA, which does work. But about an hour or two the same lost connection message happens.

While looking through the HA logs, I also noticed several messages like the following:

e2020-03-29 18:36:49 WARNING (MainThread) [insteonplm.devices] Device 29.50.E1 did not respond to an ID requeste

None of the Insteon addresses are for devices that I have installed. Sadly, I know where they ARE installed: My Previous home.

Could these devices be causing me problems? My next question is how to remove them from the Hub? I’m sure a factory reset of the hub would work, but I don’t want to re-link 30+ devices to it.

I tried using insteonplm_interactive, but had no luck. I tried the del_all_link command like this:

insteonplm: del_all_link 1 2950e1
insteonplm: Starting the All-Linking process
Attempting to link the PLM to device 2950e1.
19 devices added to the All-Link Database

But the device apepars to remain in the Hub.

Interestingly, trying to use group 0 yields an error - looking at the code I can’t figure out why group 0 is an error:

insteonplm: del_all_link 0 2950e1
Group number not valid

I tried deleting th address from both group 0 and 1 because they were both listed in the hub’s aldb:

ALDB record: {'memory': 0x0001, 'inuse': 0x01, 'mode': R, 'highwater': 0x00, 'group': 0x01, 'address': 29.50.E1, 'data1': 0x00, 'data2': 0x00, 'data3': 0x00}
ALDB record: {'memory': 0x0000, 'inuse': 0x01, 'mode': C, 'highwater': 0x00, 'group': 0x00, 'address': 29.50.E1, 'data1': 0x03, 'data2': 0x42, 'data3': 0x43}

I would appreciate any help the HA community can offer.

Best regards,
John Bernstein

Posts: 1

Participants: 1

Read full topic

@chkaloon wrote:

I have an LG TV with a Roku Streaming Stick on HDMI 1. I can turn the TV on, I can switch to HDMI 1, and I can change the Roku input to Spotify. But I can’t seem to get Spotify to respond to a playlist request. The media player is actually the Roku, so are the media player commands going to the Roku and not to Spotify? If so, how to I get commands through to Spotify?

This is the service I am trying to call (After Spotify has been successfully started on the Roku):

entity_id: media_player.roku_streaming_stick
media_content_id: 'spotify:playlist:1dUfH0b38dD6oLC5VpzCk5'
media_content_type: playlist

Posts: 1

Participants: 1

Read full topic

@texanbull14 wrote:

My thermostat sits in the dining room on the first floor, so settings based on temperature are taken from the value there. However, there are many cases where I’d like to set the heat or air conditioning based on values in various rooms.

For example:

• During the peaks of summer and winter, our sunroom may be 10-15 degrees different than next to the dining room
• If I’m working in the basement, it can be up to 10 degrees cooler than the dining room
• At night we want to keep our kids rooms between 68-72 degrees, which does not usually align with the thermostat

I have temperature sensors in all of the rooms but do not use them for anything other than reporting at the moment. Is there any way to create an automation and/or controllable lovelace widget to set the thermostat actions based on another room’s temperature sensor value?

Posts: 2

Participants: 2

Read full topic

@oman wrote:

For some reason the climate component is missing when using the Dyson integration with my Dyson HP04 Pure Hot+Cool.

Fan and sensors are displaying as entities, and work but climate is nowhere to be seen.

I have spent hours looking into this and just can’t make sense of it.

My configuration.yaml looks like this:

# 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

homeassistant:
  customize:
    media_player.bedroom:
      device_class: tv

tplink:
sonos:
dyson:
  username: "xxxxxxxxx"
  password: "xxxxxxxxx"
  language: GB
  devices:
    - device_id: xxxxxxxxx
      device_ip: xxxxxxxxx     

homekit:
  filter:
    include_domains:
        - switch
        - media_player
        - fan
        - climate
  entity_config:
    media_player.bedroom:
      feature_list:
        - feature: play_pause
        - feature: toggle_mute

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

Thanks!

Posts: 1

Participants: 1

Read full topic

@cnschulz wrote:

Gday, I have what I assume is a fairly dumb question specifically regarding the IP Webcam integration however it covers similar integrations Im sure…

If I configure the ip webcam integration without sensor monitoring (video only) and the home assistant UI is not being used, is data still being streamed from the camera to HA?

My cameras will rarely be used and I want to make sure my network is nice and fast until I need to view the cams.

Cheers

Posts: 1

Participants: 1

Read full topic