@Jiran wrote:

Hello. Please help. I tried to read many posts before but seems like nobody discussed about such way before.

Facts:
10 rooms
10 temperature sensors - 1 in every room (Philips HUE motion sensor with temp ability)
10 thermoelectric actuators (installed on floor heating valves) - single for every room
1 electric heater
1 fireplace (with water heating)

Idea:
In every room is a temperature sensor. Using HA GUI we can decide what is desired temperature in this room. Based on this (real temperature over or under) switch (tasmota) for thermoelectric actuator will turn On or OFF the floor water heating into this room.
Only selected rooms has right to decide whether heating in house will be Enabled or Disabled. Let´s call them Room1, Room2 and Room3.
In those rooms are temp sensors A, B and C.

Solution:
I think I could use standard Generic Thermostat for all rooms to open/close thermoelectric actuators of floor heating into those rooms.
BUT how to create the part where some of those rooms are able to decide if heater will turn on?
To create automation? Or is there some other tool?
I thought I could check state of all those valve switches which belongs to the rooms 1,2 and3 which has right to Enable/Disable heating. If any of those switches will be in state ON= turn heating ON. If none of those switches will be in status ON then turn heating OFF. How to do it?

This picture shows what I need. Just to TURN ON/OFF heater (in fact some automation switch because heater in my concept means to tun on electric heater (switch tasmota) and repositioning of water circuit valve (switch tasmota) or choosing heating from fireplace if water collected in tank is over 50°C - another 2switches) - but this is another automation

Heating control.jpg1063×734 65.2 KB

Posts: 9

Participants: 3

Read full topic

@michael3 wrote:

Hi All!

I’m new! Hey! haha

1. I’m currently integrating my August Home. I have both the locks and doorbell. However, only one of my locks (front) is connected by a wifi bridge, which is the doorbell. I want home assistant to connect to my other lock (back) via bluetooth and integrate with the standard button config.
2. How do I make it refresh the camera more regularly?

I’m stuck, how do I do it???

Appreciate all your help!

Posts: 1

Participants: 1

Read full topic

@merwone wrote:

Hi all,

I need some help to have schedy appdaemon scheduling my heating working.
Below my schedy.yaml:

# Schedy thermostats
schedy_heating:
  module: hass_apps_loader
  class: SchedyApp
  actor_type: thermostat

  schedule_snippets:
    appartment:
# At given times the themperature should be 22 degree celsius
    - { v: 21, start: "06:30", end: "08:00", weekdays: "1-5", weeks: "1-9, 44-52" }
    - { v: 21, start: "16:30", end: "23:00", weekdays: "1-5", weeks: "1-9, 44-52" }
    - { v: 21, start: "07:00", end: "23:00", weekdays: "6-7", weeks: "1-9, 44-52" }
# On all other times the temperature should be 19 degree celsius
    - { v: 19, weekdays: "1-7", weeks: "1-13, 40-52" }

  schedule_prepend:
  - x: "Mark(OFF, Mark.OVERLAY) if not is_empty(filter_entities('binary_sensor', window_room=room_name, state='on')) else Skip()"
  schedule_append:
  - v: "OFF"

  rooms:
    living:
      actors:
        climate.living:
      watched_entities:
      - binary_sensor.rf_terrace
      schedule:
      - x: "IncludeSchedule(schedule_snippets['appartment'])"
      rescheduling_delay: 60

In home assistant, my climate.living:

hvac_modes:
  - heat
  - 'off'
current_temperature: 18
min_temp: 5
max_temp: 22
temperature: 19
hvac_action: heating
preset_mode: null
preset_modes:
  - none
  - away
friendly_name: thermostat
supported_features: 17

The link between my schedy.yaml and my climate.living works as coded. In order for my heating to work accordingly however there is a dependency with 3 other entities, i.e.:

Climate.living state triggered from off to heat:

• switch.easyplus + switch.boiler if state = on do nothing, otherwise turn_on

• input_number.setpoint_living set_state = climate.living; attribute temperature, e.g. 21

In my opinion the way forward would be through python_script or ideally directly through schedy app.

Looking forward for ideas.

Posts: 2

Participants: 2

Read full topic

@jonerik wrote:

Hi,

So after hours of tryning, I’m realizing that I need some more knowledge and input. Because I’m stuck.
Through Tibber (my powercompany) I get readings on prices(in local currency) and the price level (cheap, normal, expensive, very expensive) etc. Through HA, I have it as local sensors, and zwave connection to the thermostats and a third party Adax Heater integration to control the heaters.

Idea:
Adjust down the thermostats to energy heat (since this is 4 degrees lower than normal consumption) and turn of a group of heaters when the power is expensive, and when it goes back to normal - set the mode to regular heat and turn on the heaters.

The purpose for this is to do two things;
A) Create a SWITCH that could trigger this on demand
B) An automated activity that monitors the development, and does the changes automatically within a timespan.
Both will also send a notification to my phone / power app.

So I’m trying to solve the SWITCH first

input_boolean.yaml

#Intput_Boolean Power switch
  kjell_mode:
    name: Kjell mode aktivert
    initial: off

Switch.yaml

#Switch.yaml Powersaving mode
  - platform: template
    switches:
     kjell_mode:
      value_template: '{{ states("input_boolean.kjell_mode") }}'
      friendly_name: 'Kjell-mode'
      turn_on:
        - service: input_boolean.turn_on
          entity_id: input_boolean.kjell_mode
        - service: climate.set_present_mode
          data:
            entity_id: group.climate_termostater
            preset_mode: none
        - service: climate.set_hvac_mode
          entity_id: group.climate_panelovn
          data: 
            hvac_modes: off 
        - service: notify.tibber
        #Notification enabled
          data:
            title: "Kjell-mode er aktivert"
            message: "Strømmen er dyr, Kjell-mode er aktivert til strømmen normaliserer seg."
      turn_off:
        - service: input_boolean.turn_off
          entity_id: input_boolean.kjell_mode
        - service: climate.set_present_mode
          entity_id: group.climate_termostater
          data:
            preset_mode: none
        - service: climate.set_hvac_mode
          entity_id: group.climate_panelovn
          data: 
            hvac_modes: heat 
        - service: notify.tibber
          #Notification disabled
          data:
            title: "Kjell-mode er deaktivert"
            message: "Da vi tilbake til normalen igjen. Få kasta litt mer penger ut av vinduet. "

This is the Groups.yaml

# Groups.yaml
  climate_panelovn:
    name: Adax Panelovner
    entities:
       ## Panelovn Kontor
       #- climate.adax_82165
       ## Panelovn Gjesterom
       - climate.adax_86969 
       ## Panelovn Soverom: Ludvig
       #- climate.adax_83216
       ## Panelovn Hovedsoverom
       - climate.adax_84604 
  climate_termostater:
    name: HeatIt Thermostater
    entities:
      - climate.thermofloor_as_heatit_thermostat_tf_021_heating
      - climate.thermofloor_as_heatit_thermostat_tf_021_heating_2
      - climate.thermofloor_as_heatit_thermostat_tf_021_heating_3
      - climate.thermofloor_as_heatit_thermostat_tf_021_heating_4

So where I have trouble is to activate the switch from Lovelace. The error is the following:

What am I doing wrong? And do you need any more documentation to help me out?

Posts: 2

Participants: 2

Read full topic

@Loader23 wrote:

Hi,

I am having this block in an automation and just want to know if there are simpler ways to achieve the same result or if I have it done all right:

  action:
  - service: light.turn_on
    entity_id: light.light_1
    data_template:
      hs_color:
        - 120
        - 100
      brightness: 255
      transition: 1
  - delay: 00:00:01
  - service: light.turn_on
    entity_id: light.light_1
    data_template:
      hs_color:
        - 240
        - 100
      brightness: 255
      transition: 1
  - delay: 00:00:01
  - service: light.turn_on
    entity_id: light.light_1
    data_template:
      hs_color:
        - 0
        - 100
      brightness: 255
      transition: 1
  - delay: 00:00:03
  - service: light.turn_on
    entity_id: light.light_1
    data_template:
      hs_color:
        - 44.941
        - 100
      brightness: 115
      transition: 1
  - service: light.turn_off
    entity_id: light.light_1

Posts: 3

Participants: 2

Read full topic

@trondat wrote:

Hi,

Every morning i activate the scene “Morgen” so that lights etc come on. I also want to add some more logic to this and have written an automation that should trigger when scene “morgen” is activated. The problem is that the automation is never triggered. I have tried with the condition commented away, but still no luck.

alias: 'Turn on lights when Morgen'
    trigger:
       platform: event
       event_type: call_service
       event_data:
         service_data:
           entity_id: scene.morgen
         domain: scene
         service: turn_on
    condition:
       condition: numeric_state
       entity_id: sensor.sensative_strips_comfort_luminance
       below: 10
    action:
       - service: light.turn_on
         data:
           entity_id: light.stuevinduer
           brightness: 70
       - service: light.turn_on
         data: 
           entity_id: light.spisestuebord       
           brightness: 183
           rgb_color: [255,163,74]    

Does anyone have some pointers to what is wrong here ?

Posts: 2

Participants: 2

Read full topic

@Tom7320 wrote:

Hi

I’m quite new to HA, tried to read the documentation but did not fully understand it to be honest. But I managed to control and automate my shutters which I am a little proud of…

Now I would like to save the shutter’s position in the evening, close them all and restore the saved position in the morning. Is that possible? How do I do that?

THX for help and your ideas!

Posts: 1

Participants: 1

Read full topic

@Malvazar wrote:

Hello I’m very new to Home Assistant, so I’m still learning all the things. The first thing I noticed however is the weather card on the overview screen is incorrect. Everything from the temperature, condition, forecast, just everything. Any advice on this would be great.

Posts: 3

Participants: 3

Read full topic

@yuvalfer wrote:

Hi,

I’m, trying to configure a already working KNX configuration.
using different tests I was able to configure all my lights.
With the shutters, it’s more complicated, according to the XKNX documentation I need to configure different address for the shutters, how can I find the current KNX configuration?

Thanks

Posts: 1

Participants: 1

Read full topic

@GiulioG wrote:

Since a week i’m starting to use Home Assistant,

I was waiting for a new release and now i have installed hassio
System HassOS 1.12

I’m encontered some problems that don’t seem fixed in the new realise

1. IFTTT with Webhooks
   autentication fail

I use:

https://xxxxxxxx.duckdns.org:8123/api/services/script/turn_on?api_password=XXXXX

in this new realise i saw that there is a Long-Lived Access Tokens,
can I use it with IFTTT?

if yes, in whitch way?

---

2. device_tracker
   I tryied

mqtt:
  broker: !secret mqtt_host
  port: !secret mqtt_ssl_port
  username: !secret mqtt_username
  password: !secret mqtt_password

device_tracker:
  - platform: owntracks
    max_gps_accuracy: 100

but i receive a configuration error on device_tracker

---

Roomba work but stay always connected h24 and the Clean green led is always on

there is a way solve this? or a workaround?

4. travel time

I’m using “waze” and “here”

If i put in the config the option

name:

they stop work, without the option name: they work but
when configured more than one they are not correctly identified
and sometimes the time is excenged beetwen one to another

There is someone with these issue?

There is a way to resolve them?

Thanks

Giulio

Posts: 1

Participants: 1

Read full topic

@klogg wrote:

What is the idea behind this toast message?

I have a ‘remote’ wall panel and if I refresh my main PC after changing my Lovelace config this toast pops up on the panel.

Is there ever a time I wouldn’t want to refresh every screen?
It’s going to happen eventually whether I like it or not

Posts: 2

Participants: 2

Read full topic

@robi wrote:

Hello community!

I searched all over the forum an the internet and didn’t find any normal IR-controlled AC devices to be integrated as standard “climate” units.

Using a simple IR blaster the devices can be controlled using JSON strinks like this, usinng IRhvac command:

'IRhvac {"Vendor":"GREE","Model":1,"Power":"on","Mode":"heat","Celsius":"on","Temp":21,"FanSpeed":"auto","SwingV":"auto","Turbo":"off","Light":"on"}'

The IR blaster uning Tasmota firmware can be easily integrated in Home Assistant like this, as a switch, to just turn on and off the AC:

  - platform: mqtt
    name: "Room1"
    command_topic: "cmnd/ir-room1/backlog"
    payload_on: 'IRhvac {"Vendor":"GREE","Model":1,"Power":"on","Mode":"heat","Celsius":"on","Temp":21,"FanSpeed":"auto","SwingV":"auto","Turbo":"off","Light":"on"}'
    payload_off: 'IRhvac {"Vendor":"GREE","Model":1,"Power":"off","Mode":"off","Celsius":"on","Temp":21,"FanSpeed":"auto","SwingV":"auto","Turbo":"off","Light":"off"}'

But, that’s not very useful if one wants to modify AC parameters.

Is there a way to crate an abstraction layer between an climate.mqtt device and the payloads required to be sent?

I’m thinking about some virtual device with different topics as a standard climate.mqtt, but these topics would point to some sort of script or or function which would concatenate the json string based on the required values, and then send them by mqtt to the real IR blaster topic as a normal IRhvac command. Does such an “mqtt topic catcher” exist?

Can you please point me in the right direction? How to do that?

Posts: 1

Participants: 1

Read full topic

@Vendo232 wrote:

Team

I would like to simply turn ON and OFF my WLED strip in automation calling for specific effect.
turn on Rainbow for 1 min for example

9 Rainbow Displays rainbow colors along the whole strip

So to turn ON Rainbow

action:
    service: mqtt.publish
    data_template:
      topic: [Device Topic.. XYZ ]/Segment/switch/set
      payload: on
      topic: [Device Topic.. XYZ ]/Segment/fx/set
      payload: 9

and to turn OFF

action:
    service: mqtt.publish
    data_template:
      topic: [Device Topic.. XYZ ]/Segment/switch/set
      payload: off

Do I have it right?

How would you setup “RANDOM” effect to be turned ON?

Posts: 1

Participants: 1

Read full topic

@DaveUK83 wrote:

Hi everyone, very new to HA, but slowly getting there by watching videos and some superb topics on the forum!

One thing I do seem to be struggling with is trying to fill the white space with cards on a new tab I added.
The default Home tab seems to make use of all the space available, however i’m stuggling to re-create that. This is what mine currently looks like:

hue.png1448×613 43.3 KB

So far, I’ve had to use two horizontal-stack otherwise having 5 cards next to each other makes it very very small. This is my current code for the top horizontal-stack (The second horizontal-stack is virtually identical)

title: Ceiling Lights
type: horizontal-stack
cards:
  - type: 'custom:light-entity-card'
    entity: light.hue_color_spot_2_2
    header: Hue 1
    persist_features: true
    group: false
    color_temp: false
    effects_list: false
  - type: 'custom:light-entity-card'
    entity: light.hue_color_spot_1_2
    header: Hue 2
    persist_features: true
    group: false
    color_temp: false
    effects_list: false
  - type: 'custom:light-entity-card'
    entity: light.hue_color_spot_5_2
    header: Hue 3
    persist_features: true
    group: false
    color_temp: false
    effects_list: false

Any help greatly appreicated.

Posts: 1

Participants: 1

Read full topic

@suckafish715 wrote:

Hi there

I recently bought a bunch of globe suite smart light blub from Costco. I couldn’t figure out how to add them into home assistant.

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@dm82m wrote:

Hey guys,

Situation: I have a heating system that talks with the cloud portal they provide. There are no API/Rest/… services provided; only an ugly UI. I wrote a python script with mechanicalsoup to access this portal; read some values and return them as json. This result looks like:

{"Heizung": {"Aussentemperatur_Aktuell": "4,2 \u00b0C", "Aussentemperatur_Minimum": "2,5 \u00b0C", "Aussentemperatur_Maximum": "17 \u00b0C", "Warmwassertemperatur_Aktuell": "55,5 \u00b0C", "Vorlauftemperatur_Aktuell_HZK1": "29,7 \u00b0C", "Istleistung_Aktuell_WE0": "0 %", "Kesseltemperatur_Aktuell_WE0": "45,1 \u00b0C", "Anlagendruck_VPT_Aktuell_WE0": "1,9 bar", "Weichentemperatur_Aktuell": "53,2 \u00b0C"}}

My main goal now would be to integrate these values into Home Assistant and for that I created the following configuration entry:

sensor
  - platform: command_line
    name: heating
    value_template: '{{ value_json["Heizung"] }}'
    json_attributes:
      - Aussentemperatur_Aktuell
      - Aussentemperatur_Minimum
      - Aussentemperatur_Maximum
      - Warmwassertemperatur_Aktuell
      - Vorlauftemperatur_Aktuell_HZK1
      - Istleistung_Aktuell_WE0
      - Kesseltemperatur_Aktuell_WE0
      - Anlagendruck_VPT_Aktuell_WE0
      - Weichentemperatur_Aktuell
    command: 'python3 /home/homeassistant/.homeassistant/scripts/wem_status.py'
    scan_interval: 600

The script is executed, returns the json but what I get in Home assistant is:

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 408, in _async_add_entity
    await entity.async_update_ha_state()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 275, in async_update_ha_state
    self._async_write_ha_state()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 394, in _async_write_ha_state
    self.entity_id, state, attr, self.force_update, self._context
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/core.py", line 988, in async_set
    state = State(entity_id, new_state, attributes, last_changed, None, context)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/core.py", line 733, in __init__
    ).format(entity_id)
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity id: sensor.heating. State max length is 255 characters.

I hope that someone could point me into the right direction.

Thanks!
Dirk

Posts: 6

Participants: 2

Read full topic

@DaveUK83 wrote:

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

Posts: 1

Participants: 1

Read full topic

@Loeffen wrote:

I came across Frencks site and perfect description for connecting a traditional doorbell with home assistant. After waiting a few weeks for alieexpres delivery, I have now gained my first experience with ESPHome (and ESP-01S).

The connection with home assistant and ESPHome was successful and with the setup as shown on the photo I can operate the doorbell chime via home assistant. Hoera !
The problem now is that the bell cannot be operated with the push button. I have tried everything but unfortunately so far without result. So in the depicted setup esphome works but the push button does not work

20191106_132337.jpg4608×2592 484 KB

Hope someone can help
Thanks
Leon

Posts: 5

Participants: 3

Read full topic

@gsmckenzie wrote:

Hello all,

I have been redoing my installation moving all my sensors to Zigbee2MQTT to avoid my reliance on third party hubs. Everything has gone nicely, but my integration with InfluxDB is not quite working as I would like.

I am trying to bring in additional tags, AREA would be nice and getting friendly_name_str to work. I think it is probably tags_attributes: that I need modify in my InfluxDB section of configuration.yaml, but can’t find where this is documented and which attributes you can add.

Has anyone already wrestled with this? Or am i going to have to create a continuous query in Influx to create room specific graphs in Grafana?

Posts: 6

Participants: 2

Read full topic

@rriva wrote:

Hi there,
I’m new to this section and to HomeAssistant in general.
I have a working instance of HassIO with some integrations working fine but:

I’ve just bought two more Broadlink RM Mini 3 and I can’t let it works.

I live in an house with three floors, and have an air conditioner on each floor.
I want to control all air conditioners from HassIO sending commands from broadlink devices but only the first one is working.

The following is my configuration:

switch:
#switch 101:
  - platform: broadlink
    host: 192.168.234.101
    mac: '78:0F:77:XX:XX:XX'
    friendly_name: "Broadlink 1"
    timeout: 15
    retry: 5
    type: rm_mini

#switch 102:
  - platform: broadlink
    host: 192.168.234.102
    mac: '24:DF:A7:XX:XX:XX'
    friendly_name: "Broadlink 2"
    timeout: 15
    retry: 5
    type: rm_mini

#switch 103:
  - platform: broadlink
    host: 192.168.234.103
    mac: '24:DF:A7:XX:XX:XX'
    friendly_name: "Broadlink 3"
    timeout: 15
    retry: 5
    type: rm_mini

smartir: 
climate:
  - platform: smartir
    name: HiSenseSala
    device_code: 9001
    controller_data: 192.168.234.101
    temperature_sensor: sensor.temperature_158d00044a439c
    humidity_sensor: sensor.humidity_158d00044a439c

  - platform: smartir
    name: HiSenseNotte
    device_code: 9001
    controller_data: 192.168.234.102
    temperature_sensor: sensor.temperature_158d00044a4387
    humidity_sensor: sensor.humidity_158d00044a4387
    
  - platform: smartir
    name: HiSenseMansarda
    device_code: 9001
    controller_data: 192.168.234.103
    temperature_sensor: sensor.temperature_158d00044a43da
    humidity_sensor: sensor.humidity_158d00044a43da

As you can see I’ve just tried to have a single “switch:” declaration with the three “platform” or three “switch” changing the switch numbers, but nothing changes.
I’ve also tried to create a switches folder, include it in configurations and created three different yaml files for the switches (in this case nothing works).

I’ve notice that only the one with IP 192.168.234.101 works fine, even if is the second in the configurations.

It will be possible an incompatibility ? all are Broadlink RM Mini 3 but with different MAC type (ad you can see from configuration), but on the Smartphone Broadlink app all works fine.

What I’m doing wrong ?

TIA
Riccardo

Posts: 1

Participants: 1

Read full topic