Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 107151 articles
Browse latest View live

Philips TV media player help please

$
0
0

@MarkR wrote:

Hello

I have a Philips Android 43pus7303_12 TV and it works as a media player for a camera stream fine over wifi, but not when I cable it up, it isn’t found by HA. Now I have no idea how this got added to HA as it isn’t listed in my media players. If I set the ip to the same as the wifi address all works fine.

It is shown as off unless something is streaming to it. I just haven’t a clue how it was added months ago :smiley: Any idea please?

when streaming I get

volume_level: 0
is_volume_muted: false
media_content_id: http://192.168.0.102:8123/api/hls/805950095ba4abd35289d3783820bca81314e111754ce12520a68f71b4a5cdd2/playlist.m3u8
media_duration: -1
media_position: 0.69093
media_position_updated_at: 2020-04-13T08:27:09.903902+00:00
app_id: CC1AD845
app_name: Default Media Receiver
entity_picture_local: null
friendly_name: 43PUS7303/12
supported_features: 21391

Posts: 1

Participants: 1

Read full topic


Nabu Casa GH Integration: PIN for garage door

$
0
0

@Sabellwind wrote:

I’ve just configured my Garage Door switch running on wemos D1 mini with ESPHome. It’s configured as a cover and device_class garage, yaml below:

esphome:
  name: esphome_garage_door
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: 
  password: 
  fast_connect: on
  
api:

ota:

web_server:
  port: 80

logger:

binary_sensor:
- platform: gpio
  pin:
    number: GPIO13
    mode: INPUT_PULLUP
    inverted: False
  name: "Garage Door Sensor"
  device_class: garage_door
  filters:
    - delayed_on: 20ms

switch:
- platform: gpio
  id: relay
  pin:
    number: GPIO5
    inverted: False
  restore_mode: ALWAYS_OFF

- platform: restart
  name: 'Garage Door REBOOT'

cover:
- platform: template
  name: "Garage Door"
  device_class: garage
  # icon: "mdi:garage"
  open_action:
    - switch.turn_off: relay
    - switch.turn_on: relay
    - delay: 0.1s
    - switch.turn_off: relay
  close_action:
    - switch.turn_off: relay
    - switch.turn_on: relay
    - delay: 0.1s
    - switch.turn_off: relay
  stop_action:
    - switch.turn_off: relay
    - switch.turn_on: relay
    - delay: 0.1s
    - switch.turn_off: relay
  optimistic: true
  assumed_state: true

status_led:
  id: status_light
  pin:
    number: GPIO2

I was starting to integrate with Google Assistant via Nabu Casa, so I’ve set a PIN and made sure that Disable Two Factor Authentication was turned off in the manage entities section.
While this was set, my GH would ask for my PIN and after me speaking it out, would just reply with ‘I’m sorry, I don’t understand’

Upon playing around with the PIN and the exposure, I’ve now lost the ability to enforce any 2FA on the garage door switch’s exposure.
image

Any idea what’s going on here? I’m going to remove the Garage Door exposure for now.

Cheers.

Posts: 1

Participants: 1

Read full topic

Sonoff Dual R2 shows only one switch out of two

$
0
0

@Hellsing wrote:

I have two Sonoff devices with Tasmota 8.1.0 firmware: Sonoff Dual R2 and Sonoff Basic. Using the auto discovery command “SetOption19 1” in the sonoff console, I see two devices in the Home Assistant, but Sonoff Dual R2 shows one instead of two switches! How do I fix this? MQTT
In Domoticz, Sonoff Dual R2 is displayed and works correctly.

Posts: 1

Participants: 1

Read full topic

Modbus TCP/IP - climate thermostat

$
0
0

@Dzaq wrote:

Hi All,
I tried to integrate HASS with soft PLC based on Codesys 3.5.
I would like to create interface in HASS for my automation system. I would like to use Modbus TCP/IP to send and receive data from PLC.
I managed to test modbus connection using “switch”, “sensor” form hass example .
I have problem with termostat for modbus communication. I am able to receive current temperature, current setpoint (in case of changeing register by e.g server) but I cannot send setpoint to my modbus server. My example is listed below.

climate:

  • platform: modbus
    scan_interval: 5
    name: termostat salon
    hub: hub1
    slave: 1
    data_type: uint //i’ve tried int - doesnt work
    data_count: 1
    scale: 1
    offset: 0
    precision: 1
    max_temp: 30
    min_temp: 15
    temp_step: 1
    target_temp_register: 15 // holding register 15
    current_temp_register: 16 // holding register 16

Anyone has similiar issue?

Posts: 1

Participants: 1

Read full topic

Help with music automation

$
0
0

@mattpitts74 wrote:

Hi Guys,

I’ve done this before but forgotten how I did it previously. I’m just trying to get a simple automation going that plays a specific playlist from my squeezebox server when I choose an input select.

I’ve tried variations on the following without any luck:

- id: '1586725533383'
  alias: Play radio four
  description: ''
  trigger:
  - entity_id: input_select.radio_select
    from: None
    platform: state
    to: Radio four
  condition: []
  action:
  - data:
      command: playlist play
      parameters: http://192.168.0.149/media/music/playlists/radiofour.m3u
    entity_id: media_player.kitchenplayer
    service: squeezebox.call_method

Any help with this would be much appreciated.

Posts: 1

Participants: 1

Read full topic

KAKU wall switch state

$
0
0

@Otopia wrote:

Hi everyone,

I’d like Home assistant to not remember the state of my KAKU AWST-8802 double wall switch.

I switched from domoticz to Home assistant. I use the wall switch to start four different light settings. To clarify:
Button left top: lights 100%
Button left bottom: lights 50%
Button right top: lights OFF
Button right bottom: lights 25%

The switch is not an actual rocker switch and doesn’t have a physical state. But when i press left bottom then the right bottom and when i then want to pres left bottom again it doesn’t react because HA thinks the left rocker is still in that position. I have to press the left top before i can press the left bottom again.

I’m using an event node in Node RED with a switch node and a call service node.

Maybe this is a NOOB question but i searched the forum and am still switching in my head from domoticz to Home assistant and i can’t figure it out. Thanks in advance for any help.

Posts: 4

Participants: 2

Read full topic

No Toggle Switch In all more-info popups

Scheduled extract and purge of database to external location?

$
0
0

@Piggyback wrote:

Hi,
First of all, I am by no means an expert in databases, so if the question is stupid, just let me know :slight_smile:

I have restricted logging for the recorder to avoid that my homeassistant database would grow too much to clog up/fill the system (I´m using Hassio on an RPI3+ wiht 64gb SD card)… Still I would like to learn about some tools and analytics around the database of home assistant, so I was thinking if the following would make sense :slight_smile:

  • No restriction on logging in the recorder
  • If the database size is above a certain size (e.g. 300 MB), then extract the database to a separate file
  • If writing successful, then purge the same records from the original database.
  • Move that separate file to another location (e.g dropbox)
  • Append the separate file in Dropbox to a masterfile in e.g. my Synology NAS or PC to one huge database which can be used for analytics

Like this the RPI has no overload of data and I could still have “infinite” history to analyse.
Would this be something unrealistic?
Thanks!

Posts: 1

Participants: 1

Read full topic


This entity does not have a unique ID, 0.108.3

$
0
0

@honikos wrote:

Hi there,
something has changed in latest hass.io updates. I have two sonoff-basic (tasmota, 8.x) garage-door opener solution (cover-template in configuration.yaml) . Worked like an charm. But since some days, I think it was update to 0.108.x I don’t get the sensor retain after hass - restarts. Read a lot here but I have no clue what to do. I know from tasmota doc’s that some sensors doesn’t work properly, but they did so far. So solution could be, to create an unique id to this entity, but is this possible for an cover which was created in configuration.yaml?
Any other idea?
Bildschirmfoto von 2020-04-13 09-04-36

thanks
Horst

Posts: 2

Participants: 2

Read full topic

After OS upgrade no access - deconz issue? tips welcome!

$
0
0

@stwillibrord wrote:

Hi,

After upgrading the OS to the latest version I cannot access the GUI (lovelace) anymore. When accessing the files the log shows the following:

2020-04-13 11:23:59 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=70 from 2020-04-13 09:15:17.046290)
2020-04-13 11:24:11 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.

2020-04-13 11:24:14 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 192.XXX.XXX.XX
2020-04-13 11:32:20 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 192.XXX.XXX.XX
2020-04-13 11:32:20 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.

Rebooted several times. Unsucessful
Removed cookies of the URL.Unsuccesful
Unplugged the deconz USB several times. rebooted after. Unsucessful

I’m relatively new to all this, if you need more info, please direct me to which folder I can get this info. Alternatively I did make a snapshot, but would like to learn how to roll back. thanks for your time.

Posts: 1

Participants: 1

Read full topic

Calling a script with parameters from automation

$
0
0

@Valen13776 wrote:

There is a script:

ifttt_script:
  alias: 'IFTTT sending mes'
  sequence:
    - service: persistent_notification.create
      data_template:
        title: 'IFTTT test'
        message: '{{ if_post }}'        

There is automation:

- alias: IFTTT Incoming connection
  trigger:
    platform: event
    event_type: ifttt_webhook_received
    event_data:
      action: call_service
  action:
    - service: script.turn_on
      entity_id: script.ifttt_script
      data_template:
        if_post: '{{ trigger.event.data.if_post }}'

After triggering automation in the logs:

Logger: homeassistant.components.automation
Source: helpers/script.py:802
Integration: Автоматизация (documentation, issues)
First occurred: 13:11:20 (2 occurrences)
Last logged: 13:15:40

IFTTT Incoming connection: Error executing script. Invalid data for call_service at pos 1: extra keys not allowed @ data['if_post']

I ask for help.
Thanks.

Posts: 2

Participants: 2

Read full topic

Settings auto generation

$
0
0

@maxyahontov wrote:

I have a couple of my software products and I want to integrate its settings into home assistant.
But I don’t want to develop separate integration for each software. Is there some kind of universal block that can receive settings list from the application (for example in JSON format), generate automatically UI for this list, and then send these settings back when the user changes something. The most common things that I want are switches, buttons, sliders that have a different range, dropdown lists.

Posts: 4

Participants: 3

Read full topic

Change HA Color Wheel to display temperature palette

$
0
0

@geoffmt wrote:

Hello there !

I am trying to achieve a new color wheel based on the original Home assistant color picker which would look like this basically :

I spent one whole day trying to copy the Home assistant color picker and modify it to change its behaviour.

I am using the Light Entity Card to implement this and i tried to modify the last bit of the code :

      <div class='light-entity-card__color-picker'>
        <ha-color-picker 
          id="${this.generateColorPickerId(t)}" 
          class='control color' 
          saturation-segments=${this._saturationSegments}
          hue-segments=${this._hueSegments}
          throttle=500 
          @colorselected=${e=>this.setColorPicker(e,t)}
        >
        </ha-color-picker>
      </div>

with my one personal tag for the color picker (ha-color-picker-temp) :

      <div class='light-entity-card__color-picker'>
        <ha-color-picker-temp
          id="${this.generateColorPickerId(t)}" 
          class='control color' 
          saturation-segments=${this._saturationSegments}
          hue-segments=${this._hueSegments}
          throttle=500 
          @colorselected=${e=>this.setColorPicker(e,t)}
        >
        </ha-color-picker-temp>
      </div>

This does not recognize my custom ha-color-picker-temp. :frowning:
To be able to use these tags, I made sure that I put the line customElements.define("ha-color-picker-temp", HaColorPickerTemp); at the end of my custom ha-color-picker.

I hope this is clear !
Do you guys have any idea on how to make this work ?

Thanks a lot if you take the time to help me !!

Posts: 1

Participants: 1

Read full topic

Unable to serialize to JSON

$
0
0

@Sonnstein wrote:

I have recently (after upgrade to 0.108) had a problem that the logfile grows extremely quickly. The following message is written to logfile at short intervals (approx. 20 MB per hour).

Does anyone have a similar problem? Any experience, what causes this behaviour?

Protokolldetails ( ERROR )

Logger: homeassistant.components.http.view
Source: components/http/view.py:120
Integration: http (documentation, issues)
First occurred: 13:25:56 (47 occurrences)
Last logged: 13:30:02

  • Unable to serialize to JSON: Object of type Template is not JSON serializable [<state sun.sun=above_horizon; … --> this message is going on for pages…

Posts: 3

Participants: 3

Read full topic

"Unable to set up dependencies of telegram" after upgrade to 108.3

$
0
0

@Bob_NL wrote:

After upgrading to 108.3, my Telegram component seems to have stopped working.
Logfile:

2020-04-13 11:00:04 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of telegram. Setup failed for dependencies: telegram_bot
2020-04-13 11:00:04 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform telegram.notify: Could not set up all dependencies.
2020-04-13 11:00:04 ERROR (MainThread) [homeassistant.components.notify] Unknown notification service specified
2020-04-13 13:40:54 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall script.manual_reboot (c:b3af184f0786481a8143401f38133a0a)>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 1240, in _safe_execute
    await self._execute_service(handler, service_call)
  File "/usr/src/homeassistant/homeassistant/core.py", line 1255, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 207, in service_handler
    await script.async_turn_on(variables=service.data, context=service.context)
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 284, in async_turn_on
    await self.script.async_run(kwargs.get(ATTR_VARIABLES), context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 802, in async_run
    await run.async_run()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 523, in async_run
    await self._async_run()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 540, in _async_run
    await self._async_step(log_exceptions=not propagate_exceptions)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 154, in _async_step
    self, f"_async_{cv.determine_script_action(self._action)}_step"
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 624, in _async_call_service_step
    *self._prep_call_service_step(), blocking=True, context=self._context
  File "/usr/src/homeassistant/homeassistant/core.py", line 1207, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Unable to find service notify/telegram

I use this component a lot but the above error originates from executing this script:

manual_reboot:
    sequence:
      - service: notify.telegram
        data:
          message: 'Manual reboot starting..' 
      - service: hassio.host_reboot

Config:

notify:
  - name: Telegram
    platform: telegram
    api_key: !secret telegram_api_key
    chat_id: !secret telegram_chat_id

I could not find any breaking changes on the Notify and/or Telegram component. Anyone else having issues?

Posts: 1

Participants: 1

Read full topic


Auto discovery not working MQTT Mosquitto broker

$
0
0

@MaRt6419 wrote:

I’m pretty new to MQTT and trying to enable auto discovery.

I already installed Mosquitto broker and zigbee2mqtt and paired a temperature sensor to test.
That all works fine but the auto discovery feature doesn’t seem to work and I cant find the device in the devices or entity tabs.

Is there something I am missing here?

Posts: 1

Participants: 1

Read full topic

DuckDNS down

Lovelace picture card not showing up anymore

$
0
0

@ThaNerd wrote:

I have the following code and it used to work until the last few updates.

          - type: horizontal-stack
            cards:
              - type: custom:card-modder
                card:
                  type: picture
                  image: /local/lovelace/remote/shield_logo.png
                style:
                  padding: 10px 10px 10px 10px
                  border-radius: 20px
                  background-color: rgba(56,60,69,1)
                  border: solid 3px rgba(118,185,0,1)
                  box-shadow: 3px 3px rgba(0,0,0,0.4)

error

Posts: 1

Participants: 1

Read full topic

Elapsed timer automation

$
0
0

@ner0tic wrote:

I’m trying to implement an elapsed timer of sorts. I searched the forums and the internerd and tried using what I found.
It it works manually, but my automation says it works, but doesn’t. Basically, I want to keep track of how long my inverter is receiving an input from an AC feed.

# sensors
sensor:
  # AC Input Amps
  - platform: mqtt
    name: magnum_inverter_AACin
    state_topic: "powerpi/inverter"
    value_template: "{{ value_json.data.AACin }}"
    json_attributes_topic: "powerpi/inverter"
    json_attributes_template: "{{ value_json.data.AACin | tojson }}" 
    unit_of_measurement: A

  - platform: template
    sensors:
      # Elapsed Time [HACK]
      magnum_inverter_ac_input_on_time:
        value_template: >-
          {{ (as_timestamp(now()) - state_attr('input_datetime.magnum_inverter_ac_input', 'timestamp'))| timestamp_custom('%H:%M:%S', false) }}

# input boolean
input_boolean:
  # Aux AC Input
  magnum_inverter_ac_input:
    name: Aux AC Input
    initial: false

# input datetime
input_datetime:
  # AC Input Elapsed Timer
  magnum_inverter_ac_input:
    has_date: true
    has_time: true

# automation
## AC Input ##################################################
  ## ON
  - alias: Start AC Input Boolean
    trigger:
      - platform: numeric_state
        entity_id: sensor.magnum_inverter_aacin
        above: 0
    action:
      service: input_boolean.turn_on
      data:
        entity_id: input_boolean.magnum_inverter_ac_input
  ## OFF
  - alias: Deavtivate AC Input Boolean
    trigger:
      - platform: numeric_state
        entity_id: sensor.magnum_inverter_aacin
        below: 0.1
    action:
      service: input_boolean.turn_off
      data:
        entity_id: input_boolean.magnum_inverter_ac_input
  ## Start Elapsed Timer
  - alias: Start AC Input Elapsed Timer
    trigger:
      platform: state
      entity_id: input_boolean.magnum_inverter_ac_input
      to: 'on'
    action:
      service: input_datetime.set_datetime
      data:
        entity_id: input_datetime.magnum_inverter_ac_input
        datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
  ## Update Elapsed Timer
  - alias: Update Magnum Elapsed Timer
    trigger:
      platform: time_pattern
      seconds: '*'
    condition:
      condition: state
      entity_id: input_boolean.magnum_inverter_ac_input
      state: 'on'
    action:
      service: homeassistant.update_entity
      entity_id:  sensor.magnum_inverter_ac_input_on_time

it all acts like it works, but even when I run it manually the input_datetime doesn’t seem to actually get updated so my elapsed timer increments from whenever I manually set the state

Posts: 1

Participants: 1

Read full topic

Update for sensor.shelly_total_power_consumption fails

$
0
0

@iz3man wrote:

2020-04-13 15:31:15 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.shelly_total_power_consumption fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 474, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/template/sensor.py", line 224, in async_update
    self._state = self._template.async_render()
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 221, in async_render
    return compiled.render(kwargs).strip()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/usr/local/lib/python3.7/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
TypeError: can only concatenate str (not "float") to str
2020-04-13 15:31:15 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.shelly_total_power fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 474, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/template/sensor.py", line 224, in async_update
    self._state = self._template.async_render()
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 221, in async_render
    return compiled.render(kwargs).strip()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/usr/local/lib/python3.7/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
TypeError: can only concatenate str (not "float") to str
2020-04-13 15:31:15 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.shelly_total_power_consumption fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 474, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/template/sensor.py", line 224, in async_update
    self._state = self._template.async_render()
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 221, in async_render
    return compiled.render(kwargs).strip()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/usr/local/lib/python3.7/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
TypeError: can only concatenate str (not "float") to str

This is what the two template sensors look like:

- platform: template
  sensors:
    shelly_total_power_consumption:
      friendly_name: 'Verbrauch Gesamt'
      unit_of_measurement: 'kWh'
      value_template: '{{ ((float(states.sensor.shelly_shem_3_dc4f227648a6_1_total_consumption.state) + float(states.sensor.shelly_shem_3_dc4f227648a6_2_total_consumption.state) + float(states.sensor.shelly_shem_3_dc4f227648a6_3_total_consumption.state)) | round(2) )}}'
                               
- platform: template
  sensors:
    shelly_total_power:
      friendly_name: 'Leistung Gesamt'
      unit_of_measurement: 'W'
      value_template: '{{ float(states.sensor.shelly_shem_3_dc4f227648a6_1_current_consumption.state) + float(states.sensor.shelly_shem_3_dc4f227648a6_2_current_consumption.state) + float(states.sensor.shelly_shem_3_dc4f227648a6_3_current_consumption.state | round(0) )}}'

Any idea what’s wrong? Thanks!!

Posts: 1

Participants: 1

Read full topic

Viewing all 107151 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>