@Chronos wrote:

Hi Everyone,

After many days of trying to make my HA securely accessible from an external source I feel I"m almost there. I hope anyone here can help me with the final part!

Goal
I’m running Home Assistant 103.2 in Docker. My goal is to register whether people are home using the IOS app. Access to HA from outside of my house is bonus.

What I managed to do
I’ve followed the walk through below and managed to i) obtain an URL from duckdns that updates through DDNS ii) used it to gain a certificate from Let’s encrypt and iii) forwarded ports 443, 80 and the HA port to the NAS.

The duckdns URL returns webstation in https with the certificate and in http returns HA when the port is added

Problem
Using a reverse proxy routing HTTPS 443 to the local HA adress should finish it. The problem is that when i fill in the duckdns URL it returns “the domain name is already used, please use another name”. There is no other reverse proxy there, I tried restarting the NAS and cannot find any solution on the internet.

The strange thing is that when i put “www” in front of the URL in the reverse proxy the reverse proxy does accept the URL. When I enter https://www.domain.duckdns.org HA works with certificate! But only from my home, from another location the page is blocked indicating that the certificate is issued for a different domain.

Capture600×746 36.1 KB

My main question is if anyone has encountered (and solved!) the reverse proxy problem. I’m also very open to other ways to achieve my goal. I’ve also explored copying the certificates to the HA directory to invoke them directly from HA but as soon as I uncomment the SSL lines HA does not start at all anymore with no log to debug.

Posts: 1

Participants: 1

Read full topic

@ricarva wrote:

Hi, everyone

I’m a relative newcomer to Home Assistant in general, and Lovelace setup in particular.

I’ve come up with a problem I can’t really figure out: on a specific Lovelace view, my cards aren’t reflowing to fill the available screen real estate:

LovelacePane11584×789 32.3 KB

LovelacePane21584×788 36.2 KB

Given the 3 cards present in this view, shouldn’t Lovelace be rearranging them already?

Each card is a custom (to remove borders) stack-in-card, btw.

If anyone can point me in the right direction, I’d greatly appreciate it.

Cheers,

Posts: 1

Participants: 1

Read full topic

@Viktors_Linovs wrote:

Maybe it is solved question already, but is there any clever way or workaround?
I have this kind of template switch:

      template_light:
        friendly_name: Template light
        value_template: "{{ is_state('binary_sensor.light_sensor', 'on') }}"
        turn_on:
          - service: switch.toggle
            data:
              entity_id: switch.light_switch
        turn_off:
          - service: switch.toggle
            data:
              entity_id: switch.light_switch

Everything works fine, but when I hooked up several of these template switches to the google home and put them in the same room then when I want to disable all the light in the room then if any light was off at that moment, then it would be toggeled to on state.
This means to me that even though the light was off it recieved the switch.toggle command, which I do not want it to recieve. What should I do?

I get the same behaviour if I have this template switch in on state and just call service swtich.turn_on on this switch (from the developer tools menu) then it turns off even though it was on and should not react to this service (my logic tells me so).

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@sebaw wrote:

Hi guys,
question concerns Shelly 2.5 configured in Home Assistant using https://github.com/StyraHem/ShellyForHASS (both are up to date installed recently).

I’ve got double rocker switch for 2 lamps connected to Shelly 2.5 on my staircase - what I want to achieve is when I turn off the light, it actually switches off after few seconds delay and allows to climb the stairs with lights on (doesn’t matter if it’s triggered using physical rocker switch or via home assistant). I cannot find a way to replace automation with a device turn off action or another way to accomplish this.

Edit: this is obviously important in case of manual turn off, if turned off via the app, then I can do it easily few seconds later, but requires to have a phone in hand and an app turned on.

Posts: 1

Participants: 1

Read full topic

@DailyBombs wrote:

Hi there

I’ve followed this tutorial:

• I run Home Assistant Core on Ubuntu 18.04.
• I use DuckDNS and use that URL in Google Actions Console settings

Here is what I added to configuration.yaml:

http:
  base_url: !secret
  ssl_certificate: fullchain.pem
  ssl_key: privkey.pem


google_assistant:
  project_id: !secret
  service_account: !include SERVICE_ACCOUNT.JSON
  report_state: true
  exposed_domains:
    - switch
    - light

The device shows up in Google Home as “[test] My App” and it redirects me to my Home Assistant login screen. I can enter my username and password but after some seconds it throws me back to Google Home app (iphone) and I get the error message “An error has occurred” (something like that) and nothing more.

It seems like everything is working, but there is something wrong with the authentication. Don’t know why. Any ideas?

/ Oskar

Posts: 1

Participants: 1

Read full topic

@Phillip_Sperry wrote:

Is there a way to force a trigger to be re-evaluates?

The situation I have is that I have a trigger that when it’s “true” it fires an action to remediate what caused the trigger. The problem is that the remediation fails about 5% of the time and the trigger remains “true” So I use a time pattern trigger to fire the remediation every 5 minutes but that causes a lot more traffic on my network and fills up my logs.

I thought it might be more elegant if there was a way to make HA evaluate the trigger again and remediate if needed. Is this possible?

Posts: 1

Participants: 1

Read full topic

@Jonesie wrote:

I have recently torn down my Standard HA ZWave Integation network, and I installed the Mosquitto MQTT add-on and the zwave2mqtt addon. I’ve added a number of ZWave Switches and Dimmers, with interesting results.

One device works fine through HA and Lovelace. One.

All of the devices work fine if I interact them through the zwave2mqtt control panel. If I open the zwave2mqtt Control Panel, select ANY device, find the controls under the User section, it works, and it responds quickly.

The MQTT Integration sees all of the devices. I can click on a device and see it’s Entity (or entities, in some cases), but the entity state is often wrong. Attempting to change the entity state through the Configuration > Devices interface has no effect. The state switch in the UI will often toggle, then immediately toggle back.

In the zwave2mqtt Control Panel, I selected the single working device started Debug, then toggled the power state through Lovelace. Many messages scrolled by and the device responded quickly. If I choose any other device and attempt this, I get nothing on the Debug screen.

I also have some WiFi outlets flashed with Tasmota running on MQTT that work really well.

I am running HA via the image for the RPi3:
HA Core 0.108.1
HA OS 3.13
zwave2mqtt add-on 0.6.0
Mosquitto MQTT add-on 5.1
Z-Wave Adapter is a HUSBZB-1 connected to the RPi via an extension cable.
I am running the HA database on a separate MySQL server, so as to ease the load on the Pi and the SD card.

I’ve tried to do everything right. I’ve been using HA for a few months now, after moving off of Wink. I have a bunch of ZigBee devices that work very well, despite all of this Z-Wave non-sense.

I am very happy with how much easier the whole Z-Wave thing has been with zwave2mqtt, but this speed bump has got me puzzled. HASS restarts quickly, the devices join the ZWave network very quickly, it’s been a very pleasurable experience until the past few days.

I tried to do my research before posting this as a last resort. I have also tried to include as much information as possible, but please let me know if there is anything critical I omitted.

Thanks - Jonesie

Posts: 1

Participants: 1

Read full topic

@Guillaume_Corgnet wrote:

Hey guys,

I’m currently wondering how to best proceed with this.
I have Home Assistant running (hass.io) and I use NodeRed for all my automation. I also have a bunch of Phillips Hue lights and physical switches (Hue Dimmer Switch, Hue Tab, Hue Motion Sensor)

I use my lights in multiple ways. Some of the lights are on a timer (via Nodered), some I mostly turn on/off via a physical Dimmer Switch (straight through hue, no HA involved there). I even have some lights turned on/off via a 3rd party Z-Wave motion sensor (via Nodered/HA). FInally, I sometimes use my HA UI to toggle some lights (I have a floorplan view of my lights)

What I would like to do, is for my lights to use the built in Hue scenes (eg Concentrate, Energize, Relax, Read) depending on the time of the day. For exmaple, I’d like my lights to be brighter in the morning and more orange-ish in the evening, etc…
This is fairly easy to do with the Hue app but will not be picked up by Home Assistant and the Scene needs to be reset otherwise, if you simple “toggle” the light in HA, it will use the last scene, which makes sense but is not what I want.
I also know I never managed to change the Scene on the Hue bulbs while they were toggled off, so have an automation in the middle of the night that changes from evening Scene to morning Scene is not really workable.

Now, I could probably add a whole bunch of logic in HA/Nodered to cover all my cases (toggles through UI, toggles through motion sensor, case for when the light is already on but it’s time to change scene, etc…) but this will result in a lot of brittle, duplicated logic, I’m afraid…
There is also the case where I simply use the Hue Dimmer Switch, for which HA will have no involvement, so I’d need to configure this in Hue too, I guess…

Has anyone come up with a clever solution to manage this particular problem?
I guess I’d love to be able to set some blanket rules, per light group that says that if the lights are ever on (regardless of how they got toggled), this is how the should be (Hue scene, or color + brightness)…

I would appreciate any comment, advice, thoughts…

Cheers,

Guillaume

Posts: 1

Participants: 1

Read full topic

@fender4645 wrote:

Sorry if the title is confusing. What I’m simply trying to do is create a notification that will tell me which sensors are “on”. I have a group called “windows_doors” with all of my window and door sensors specified. I’m testing this out by just calling the “notify.<my_mobile_app>” service. Here’s the jinja template code I have for the Service Data:

message: >
  {% if is_state('group.windows_doors', 'on') %}
  The following windows are open: 
    {% for window in expand('group.windows_doors') %} {% if window.state == 'on' %} {{ window.name }}
      {% endif %}
    {% endfor %}
  {% endif %}

The logic seems to work however the text has a line break for every entity that doesn’t match the “on” condition. So for example, I’ll get a notification that looks like:

Kitchen Window


Bathroom Window
Master Window





Laundry Window

How do I prevent it from showing a blank line for the entities that don’t match the condition? Ideally, I’d like for the notification to just be:

Kitchen Window, Bathroom Window, Master Window, Laundry Window.

I see how I can use the “loop.first” and “loop.last” to add or not add the commas. As you can tell, I have zero experience with Jinja. Thanks for the help!

Posts: 11

Participants: 6

Read full topic

@Technicolor wrote:

Hello.
I would like to control the bottom valve of my hot-tub.
Then the valve is closed I can will the hottub and when the valve is open I empty the hottub.

So how this works. The valve is connected to two relays that are controlled by raspberry pi, that HA runs on. To close the valve I turn on relay 1 for 30 seconds, to open the valve I turn on relay 2 for 30 seconds.
If (by accident) I turn on both relays, I risk ruining the valve.

Do you have any suggestions on how to safely implement this in HA.
So if the “open” button has been pressed (relay 1), can I somehow make sure the relay 2 is Blocked during these 30 seconds.
Regards
Technicolor

Posts: 2

Participants: 2

Read full topic

@SnapETom wrote:

I have about a dozen Jasco/GE light switches connected to a Aeotec USB Z-Stick on a Raspberry Pi 3b+. For a while, they were working great with Homeassistant. After several breaking changes, I just decided to completely reinstall HA and do things the “right way” using the ZWave option on the configuration menu.

I’ve ran into an issue where I can’t add more than 7 devices. Things that were well in range before now cannot be added.

When I click Add Node, journalctl reports:

Apr 24 01:55:29 pibox hass[1148]: 2020-04-24 01:55:29 INFO (SyncWorker_9) [homeassistant.components.zwave] Z-Wave add_node have been initialized
Apr 24 02:02:02 pibox hass[1148]: 2020-04-24 02:02:02 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1594965840] Connection closed by client
Apr 24 02:03:19 pibox hass[1148]: 2020-04-24 02:03:19 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error in data received
Apr 24 02:03:19 pibox hass[1148]: Traceback (most recent call last):
Apr 24 02:03:19 pibox hass[1148]:   File "/usr/local/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
Apr 24 02:03:19 pibox hass[1148]:     ssldata, appdata = self._sslpipe.feed_ssldata(data)
Apr 24 02:03:19 pibox hass[1148]:   File "/usr/local/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
Apr 24 02:03:19 pibox hass[1148]:     self._sslobj.unwrap()
Apr 24 02:03:19 pibox hass[1148]:   File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
Apr 24 02:03:19 pibox hass[1148]:     return self._sslobj.shutdown()
Apr 24 02:03:19 pibox hass[1148]: ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
Apr 24 02:03:19 pibox hass[1148]: 2020-04-24 02:03:19 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1594612784] Connection closed by client

And OZW_Log reports:

2020-04-24 01:55:29.021 Detail, Queuing (Controller) Add Device
2020-04-24 01:55:29.022 Info, Add Device
2020-04-24 01:55:29.022 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x3a, 0x4b
2020-04-24 01:55:29.022 Detail, Notification: ControllerCommand - Starting
2020-04-24 01:55:29.023 Detail,
2020-04-24 01:55:29.023 Info, contrlr, Sending (Command) message (Callback ID=0x3a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x3a, 0x4b
2020-04-24 01:55:29.027 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x3a, 0x01, 0x00, 0x00, 0x89
2020-04-24 01:55:29.027 Detail,
2020-04-24 01:55:29.027 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-24 01:55:29.028 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-04-24 01:55:29.028 Detail, Node001,   Expected callbackId was received
2020-04-24 01:55:29.028 Detail, Node001,   Expected reply was received
2020-04-24 01:55:29.028 Detail, Node001,   Message transaction complete
2020-04-24 01:55:29.028 Detail,
2020-04-24 01:55:29.028 Detail, contrlr, Removing current message
2020-04-24 01:55:29.028 Detail, Notification: ControllerCommand - Waiting
2020-04-24 01:55:29.031 Info, WriteNextMsg Controller nothing to do

And nothing. This timeout actually puts either homeassistant or OpenZWave into this blocked state. If I try to turn things on and off, I can see OpenZWave keep sending out commands, but nothing actually happens to the lights.

2020-04-24 02:05:55.869 Info, Node007, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2020-04-24 02:05:55.869 Info, Node007, SwitchBinary::Set - Setting node 7 to Off
2020-04-24 02:05:55.869 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x25, 0x01, 0x00, 0x25, 0x3d, 0xde
2020-04-24 02:05:55.869 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x3e, 0xdc

Any idea what’s going on? This is quite frustrating because everything was working fine for years, so I doubt it’s a signal strength issue.

Raspbian Buster
Raspberry Pi 3b+
Python 3.7.3
HA running in a virtual environment

Posts: 1

Participants: 1

Read full topic

@Greytooth wrote:

I’m trying to do an automation in which a double click on a Fibaro Dimmer 2 S2 should open or close a cover depending on it’s current position. Obviously that could be solved with two separate automations, but I would prefer only one and want to use a service template to check the current position of the cover and then select the appropriate service call.

The logic is that when attribute “current_position” is 100 the double click should call the service cover.close_cover and any other value should generate a call to the service cover.open_cover.

This is my code

- alias: Matplats dimmer S2 Double click up/down
  initial_state: on
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.fibaro_system_fgd212_dimmer_2_3
      scene_id: 24
  action:
    - service_template: >-
      {% if (states.cover.qubino_goap_zmnhod1_flush_shutter_dc_level_4.attributes.current_position)|int == 100) %}
        cover.close_cover
      {% else %}
        cover.open_cover
      {% endif %}
      entity_id: 
        - cover.qubino_goap_zmnhod1_flush_shutter_dc_level_4

But this only generates the error message
“Error loading /config/configuration.yaml: while scanning for the next token found character ‘%’ that cannot start any token in “/config/automations/covers.yaml”, line 365, column 8”

I can’t figure out what’s wrong, can anyone help me please?

Posts: 1

Participants: 1

Read full topic

@une18 wrote:

I am using Ubuntu - Docker - HA

Samba share is up and running as HA add-on. I can see HA files from the computer. I would like to see more files and folders. I installed Plex and it is up and running. I have created folders /music /movies etc, but how to access them by my windows computer. How can I upload the files to the server. Where to start and how to?

1. edit Samba share in HA to show other folders
2. Install some solution in Docker for fileshare. (tried, but got confused, because port 8080 is already in use by Pi-Hole.

Posts: 3

Participants: 2

Read full topic

@palengh wrote:

The {{ state_attr('sun.sun', 'elevation') }} is doing the job, but on cloudy days this value needs adjustments. {{ states.sensor.yr_cloudiness.state }} (now it’s 80,6% cloudiness).

I can use a sensor to measure the light, but I’d rather put cloudiness into account in this matter, and that is way more fun .

How can I tweak the above: '-4.0' value via a formula/template?

This is what I want:
IF cloudy
THEN change the value of elevation to fire the trigger earlier
…since it’s darker when it’s cloudy

- platform: numeric_state
  entity_id: sun.sun
  value_template: '{{ state.attributes.elevation }}'
  above: '-4.0'

Posts: 8

Participants: 2

Read full topic

@Freddy94 wrote:

Hi!

I’m trying to make an home button, which includes turning on specific lights and heating my house by my thermostats from Netatmo. However, the lights should only turn on after sunset. I think the only option for this to work is to make two scenes: one for the thermostats and one for the lights, and then combine these into one scene.

And here is my problem: it won’t work! When I activate the scene, nothing happens, although the two scenes works individually. Has anyone experienced the same problem?

The scene config is this:

- id: '1587665066579'
  name: Ankomst 2
  entities:
    scene.lys_ved_ankomst_2:
      entity_id:
      - light.entre
      - light.kokken
      friendly_name: 'Lys ved ankomst 2 '
      id: '1587664880677'
      state: scening
    scene.termostater_ved_ankomst:
      entity_id:
      - climate.netatmo_gang
      - climate.netatmo_kokken
      - climate.netatmo_kontor
      - climate.netatmo_sovevaerelse
      - climate.netatmo_stue
      friendly_name: Termostater ved ankomst
      id: '1587316917480'
      state: scening
  

- id: '1587316917480'
  name: Termostater ved ankomst
  entities:
    climate.netatmo_gang:
      battery_level: 90
      current_temperature: 19.5
      friendly_name: Netatmo Gang
      hvac_action: idle
      hvac_modes:
      - auto
      - heat
      max_temp: 35
      min_temp: 7
      preset_mode: Schedule
      preset_modes:
      - away
      - boost
      - Frost Guard
      - Schedule
      state: auto
      supported_features: 17
      target_temp_step: 0.5
      temperature: 16
    climate.netatmo_kokken:
      battery_level: 91
      current_temperature: 20
      friendly_name: Netatmo Køkken
      hvac_action: idle
      hvac_modes:
      - auto
      - heat
      max_temp: 35
      min_temp: 7
      preset_mode: Schedule
      preset_modes:
      - away
      - boost
      - Frost Guard
      - Schedule
      state: auto
      supported_features: 17
      target_temp_step: 0.5
      temperature: 16
    climate.netatmo_kontor:
      battery_level: 89
      current_temperature: 19
      friendly_name: Netatmo Kontor
      hvac_action: idle
      hvac_modes:
      - auto
      - heat
      max_temp: 35
      min_temp: 7
      preset_mode: Schedule
      preset_modes:
      - away
      - boost
      - Frost Guard
      - Schedule
      state: auto
      supported_features: 17
      target_temp_step: 0.5
      temperature: 16
    climate.netatmo_sovevaerelse:
      battery_level: 91
      current_temperature: 19.5
      friendly_name: Netatmo Soveværelse
      hvac_action: idle
      hvac_modes:
      - auto
      - heat
      max_temp: 35
      min_temp: 7
      preset_mode: Schedule
      preset_modes:
      - away
      - boost
      - Frost Guard
      - Schedule
      state: auto
      supported_features: 17
      target_temp_step: 0.5
      temperature: 16
    climate.netatmo_stue:
      battery_level: 90
      current_temperature: 21
      friendly_name: Netatmo Stue
      hvac_action: idle
      hvac_modes:
      - auto
      - heat
      max_temp: 35
      min_temp: 7
      preset_mode: Schedule
      preset_modes:
      - away
      - boost
      - Frost Guard
      - Schedule
      state: auto
      supported_features: 17
      target_temp_step: 0.5
      temperature: 20

- id: '1587664880677'
  name: 'Lys ved ankomst 2 '
  entities:
    light.entre:
      brightness: 254
      friendly_name: Entré
      state: 'on'
      supported_features: 41
    light.kokken:
      brightness: 254
      effect: none
      effect_list:
      - colorloop
      - random
      friendly_name: Køkken
      hs_color:
      - 255.059
      - 100
      max_mireds: 500
      min_mireds: 153
      rgb_color:
      - 64
      - 0
      - 255
      state: 'on'
      supported_features: 63
      xy_color:
      - 0.158
      - 0.05

Posts: 7

Participants: 2

Read full topic

@a94marbo wrote:

I am trying to do many things at the same time here.

I am trying to:

• use the button card in Lovelace to activate a service to call…
• a pop-up card using browser_mod in order open the custom xiaomi-vacuum-map-card…
• In order to controll my vacuum.

The custom xiaomi-vacuum-map-card work on its own in a sepate view.

Lovelace complains about the intendension of the row defining the zones:, but I doubt that´s the error…

          - type: button
            name: Open Vacuum card
            icon: mdi:robot-vacuum
            style:
              height: 100%
              left: 50%
              top: 50%
              width: 100%
            tap_action:
              action: call-service
              service: browser_mod.popup
              service_data:
                title: Vacuum control
                card:
                  type: 'custom:xiaomi-vacuum-map-card'
                  entity: vacuum.xiaomi_vacuum_cleaner
	                style:
                    border-radius: 20px
                    --ha-card-border-radius: 20px
                    --ha-card-background: red
	                map_image: /local/overvaning_big.png
	                calibration_points:
                    - map:
                        x: 1800
                        'y': 1261
                      vacuum:
                        x: 25500
                        'y': 25500
                    - map:
                        x: 300
                        'y': 710
                      vacuum:
                        x: 36000
                        'y': 21200
                    - map:
                        x: 2155
                        'y': 100
                      vacuum:
                        x: 23200
                        'y': 18000
                  zones:
                      - - - 21680
                          - 22903
			  - 25020
                          - 26321
                     - - - 25140
  		         - 22670
		         - 27950
		         - 26141
	            - - - 28070
	                - 22483
                        - 31420
			- 25915
		   - - - 23131
		       - 21247
		       - 31500
		       - 22240
		  - - - 31646
		      - 17100
		      - 36950
		      - 25560
                 - - - 29000
	             - 17270
	             - 31540
	             - 20674
	        - - - 21804
	            - 17720
	            - 24840
	            - 21110
                deviceID:
                  - desktop_home
                  - dashboard

Posts: 1

Participants: 1

Read full topic

@johanb7 wrote:

Hi All,

I created the following Automation but the action (push) is still send even if the state is None:

   alias: Send push if today is Restafval
   description: ''
   trigger:
   - platform: template
     value_template: '{{ is_state(''sensor.afvalinfo_today'', ''restafval'') }}'
   - at: '11:50'
     platform: time
   condition: []
   action:
   - data:
       message: Grijze container buitenzetten
       title: Alert
    service: notify.mobile_app_PHONE

I’ve also tried:
value_template: '"{% if is_state(''sensor.afvalinfo_today'', ''restafval'') %}true{%endif%}"'

But that isn’t working also.
Regards,
Johan

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

using the Waqi integration with this config:

  - platform: waqi
    token: !secret waqi_token
    locations:
      - Groenborgerlaan, Antwerpen

which is supposed to be a specific station location, the integration creates sensors for all Antwerpen stations…

Schermafbeelding 2020-04-24 om 12.14.231264×560 54.8 KB

which is somewhat unexpected. Anyone here with a way to only use the station as setup in the config?

all my other stations are listed as per config, and only those:

  - platform: waqi
    token: !secret waqi_token
    locations:
      - Vennekenstraat, Huijbergen
      - Station Ossendrecht, Brabant
      - Station Moerdijk, Brabant
      - Station Woensdrecht, Brabant
      - Zevenbergen, Brabant
      - Klundert, Brabant
      - Schiedamsevest, Rotterdam

Schermafbeelding 2020-04-24 om 12.16.481216×488 48.7 KB

remarkable is they don’t use the country in the sensor name, while the Antwerpen sensors all do.
thanks for having a look

Posts: 3

Participants: 2

Read full topic

@jksukino wrote:

Hey all. When I try to write an automation through the frontend I get the following error:
Failed to call service automation/reload. extra keys not allowed @ data['below'] humidity

I try to set up an automation to notify me when the humidity is too low. See picture how I set it up. The automation passes without errors If I leave the part on the screenshot out.

humidity not working1153×508 25.7 KB

.

This is my sensor:

- platform: template
  sensors:
    humidity_thermostat_bedroom:
      friendly_name: 'Bedroom Thermostat'
      unit_of_measurement: '%'
      icon_template: 'mdi:humidity'
      entity_id: "climate.tado_smart_radiator_thermostat_va0320XXXXXX"
      value_template: '{{  states.climate.tado_smart_radiator_thermostat_va0320XXXXXX.attributes.current_humidity  }}'

Posts: 1

Participants: 1

Read full topic

@benmprojects wrote:

Hi I migrated from Tasmota to ESPHome successfully with the config below.

substitutions:
  device_name: esphome_kitchen_switch
  friendly_name: "Kitchen Switch"

#################################
esphome:
  name: kitchen_light
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: "Home"
  password: "Ret5aM321"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Kitchen Light Fallback Hotspot"
    password: "jtkuxZPPTp3Y"

#################################

status_led:
  pin:
    number: GPIO4
    inverted: True

output:
  # Top (or only) button
  - platform: gpio
    pin: GPIO13
    id: relay1


light:
  # Top (or only) button
  - platform: binary
    name: "${friendly_name} Top"
    output: relay1
    id: light1


# Buttons
binary_sensor:
  # Top (or only) button
  - platform: gpio
    pin:
      number: GPIO16
      mode: INPUT_PULLUP
      inverted: True
    name: "${friendly_name} Top Button"
    #toggle relay on push
    on_press:
      - light.toggle: light1


switch:
- platform: restart
  name: "${friendly_name} REBOOT"

Now I want to update the config with ota: api: and webserver: as per below

substitutions:
  device_name: esphome_kitchen_switch
  friendly_name: "Kitchen Switch"

#################################
esphome:
  name: kitchen_light
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: "Home"
  password: "Ret5aM321"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Kitchen Light Fallback Hotspot"
    password: "jtkuxZPPTp3Y"

web_server:
  port: 80

ota:

api:

# Enable logging
logger:
#  level: WARN
  level: DEBUG
#  level: VERY_VERBOSEWARN

#################################

status_led:
  pin:
    number: GPIO4
    inverted: True

output:
  # Top (or only) button
  - platform: gpio
    pin: GPIO13
    id: relay1


light:
  # Top (or only) button
  - platform: binary
    name: "${friendly_name} Top"
    output: relay1
    id: light1


# Buttons
binary_sensor:
  # Top (or only) button
  - platform: gpio
    pin:
      number: GPIO16
      mode: INPUT_PULLUP
      inverted: True
    name: "${friendly_name} Top Button"
    #toggle relay on push
    on_press:
      - light.toggle: light1


switch:
- platform: restart
  name: "${friendly_name} REBOOT"

But I receive the error below.

========================= [SUCCESS] Took 4.07 seconds =========================
INFO Successfully compiled program.
INFO Resolving IP address of kitchen_light.local
INFO  -> 192.168.1.23
ERROR Connecting to kitchen_light.local:8266 failed: [Errno 111] Connection refused

any Ideas?

Thanks,

Ben

Posts: 1

Participants: 1

Read full topic