@arc2v wrote:

Hi all,
I use an ASUS router which has its own ddns client and encryption certs from LetsEncrypt.

I would like to open up Home Assistant to the outside world and was looking over the various steps.

Since the router is just going to port forward 443 to the HA server, do I copy the router cert to HA, or does the HA server need its own certificate?

Thanks.

Posts: 1

Participants: 1

Read full topic

@Matt_Barnes wrote:

So I have had three power cuts over the past month and its really annoying as it means Hassio on Pi 3+ stops working.

I need to physically unplug the Pi then plug it in and it starts again. I normally work on my setup while at work using Duckdns. I have the pi connected to a unifi switch and have the unifi app but as far as I know I cannot do anything to resolve this issue remotely. Is there anything that can be done, or anything I can do while at home to prevent it happening next power cut?

Surely a power cut shouldnt cause HA to shut down and not restart when power back on?

Posts: 12

Participants: 4

Read full topic

@papasierra wrote:

I’m annoyed I can’t work this out, but I have been trying to get the confirmation pop-up to work for the entity button card. This is what I think the instructions on https://www.home-assistant.io/lovelace/entity-button/ are instructing:

type: entity-button
tap_action:
  action: toggle
  confirmation: true
show_icon: true
show_name: true
entity: switch.swimming_pool_light
name: Light

But I am getting an error message:
Expected a value of type {action,navigation_path,url_path,service,service_data} | undefinedfortap_action.confirmationbut receivedtrue.

Thank you for any advice on this.

Posts: 3

Participants: 2

Read full topic

@dklundvall wrote:

I’ve been having trouble connecting my IKEA lights, and Aqara temperature sensor. When initiating a search through the phoscon app it reports nothing was found, however the nodes and endpoints do show up in the deconz GUI, although without the attribute dropdown menu with the device specific controls. Trying to fetch the simple descriptors does not work. I’ve posted an issue about it on their git but with no response, it has a more detailed description of my problem, hoping someone here has an idea of what I should try?

Git Issue

I’m using the ConBee II with an extension cable on Ubuntu 18.04 atm, started trying on a raspberry pi but thought troubleshooting with deconz GUI would be easier from a laptop.

Posts: 4

Participants: 2

Read full topic

@makani47 wrote:

I am running home assistant in Docker using a docker-compose file and the official Home Assistant image found here. I’m trying to integrate my Honeywell Total Connect alarm panel. It works in my old installation of hassbian on my RPI, but not in Docker. The issue is:

If you have issues running this component, you may require libxml2-dev and libxmlsec1-dev packages. To install these on Hassbian, run the command apt install libxml2-dev libxmlsec1-dev with sudo.

I’m not sure of a way around that except maybe use Hassio if it has an add-on, however I can’t find a good way to setup Hassio in docker-compose. I have about 30 other images using docker-compose and want to keep Home Assistant with it as well.

Posts: 3

Participants: 2

Read full topic

@Mave922 wrote:

I have a 433mhz water sensor that I have working with Sonoff RF Bridge(Tasmota) and MQTT. The water detection alert works fine, but the water sensor doesn’t send a signal when there is no longer water. I tried setting up an automation to clear the status, but it isn’t working. Any thoughts?

Sensor:

- platform: mqtt
  state_topic: "tele/RF_Bridge/RESULT"
  name: 'Basement Water Sensor'
  value_template: '{{value_json.RfReceived.Data}}'
  payload_on: '6EEC0C'
  payload_on: '6EEC0Coff'
  device_class: Moisture
  qos: 1

Automation to clear sensor:

- alias: Reset basement water detecotr
  initial_state: 'on'
  trigger:
  - platform: state
    entity_id: binary_sensor.basement_water_sensor
    from: 'off'
    to: 'on'
    for: "01:00:00"
  action:
  - service: mqtt.publish
    data:
      topic: tele/RF_Bridge/RESULT
      payload: 6EEC0Coff

Posts: 6

Participants: 5

Read full topic

@scubieman wrote:

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

Posts: 1

Participants: 1

Read full topic

@andyng wrote:

Hello,

I am having the problem when config Home Assistant.
I run HA on Odroid box. The lovelace UI always shows the timestamp of the sensor using UTC.

Here is the detail info:

{{ utcnow() }}
{{ now() }}
{{ utcnow().astimezone() }}
{{ now().astimezone() }}
{{ utcnow().tzinfo }}
{{ now().tzinfo }}
{{ now().astimezone().tzinfo }}

Return:

2019-11-07 15:53:46.504967+00:00
2019-11-07 09:53:46.505081-06:00
2019-11-07 09:53:46.505217-06:00
2019-11-07 09:53:46.505550-06:00
UTC
America/Regina
CST

Linux said:

timedatectl status

Return:

      Local time: Thu 2019-11-07 09:52:56 CST
  Universal time: Thu 2019-11-07 15:52:56 UTC
        RTC time: Thu 2019-11-07 15:52:57
       Time zone: America/Regina (CST, -0600)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

I have a door sensor, and creat a query to grab last changed status:

- platform: sql
  scan_interval: 2
  queries:
    - name: living to garage door last opened
      query: "select last_changed from states where entity_id = 'binary_sensor.0x00158d000275ef5d_contact' and state = 'on' order by last_changed desc;"
      column: 'last_changed'
      value_template: "{{ as_timestamp(value) | timestamp_local }}"    

But it always show UTC time on Lovelace UI.
I tested in Developer tool > Template

{{ as_timestamp( states.binary_sensor['0x00158d000275ef5d_contact'].last_updated) | timestamp_local }}

And it returns the correct time with local time zone.

In configuration.yaml file, I already set the time zone:

time_zone: America/Regina

Am I missing something? Thank you

Posts: 9

Participants: 2

Read full topic

@jkbrowne wrote:

Hey guys,

Just some quick background. Among other things, I’m using HA as a hub for all of my AV equipment. I have my infrared and network commands set up to control all of the equipment via a combination of itach and shell_command configuration settings. And I built a stand-alone web UI on top of the HA API so I have a nice responsive interface for it all. All of that is working fine.

I wanted to take it to the next level and add Alexa control so I could use voice commands to do things like turn on the TVs, adjust volume, etc. I set up the Alexa Smart home skill and lambda (on my own, not via Nabu Casa) and was able to make some the commands work by configuring them and exposing them to Alexa as switches. I realized the volume control would need to use the StepSpeaker interface so I decided to build my own custom component for each TV as a media_player component which would allow for the power and volume commands. I have it mostly working but I noticed that when I say “Alexa, volume up 20 on the Kitchen TV” it only adjusts the volume a-few steps, not 20 like I asked. I dug into the code for the Alexa Smart Home skill and, if I’m reading this correctly, it appears it just does a loop for each “step” and asynchronously calls the volume up/down method on the media_player device. This essentially is sending the volume step commands way too quickly to be processed by the itach device so only some of them get interpreted. This explains the behavior I’m seeing and I confirmed it via logging. I would imagine this would be a problem for other devices besides itach also. Has anyone run into this? Seems like either 1) there needs to be a delay option for the Alexa Smart Home StepSpeaker implementation so some processing time can be inserted between the volume steps. Or 2), the step value (integer) that was specified in your voice command should be passed as data into the media_player implementation so it can be handled appropriately. A basic loop to hammer the device X number of times doesn’t seem like a good solution for the volume commands, not in my opinion anyway. Code for the handlers.py file in the Alexa Smart Home interface is below, notice the for loop. Feedback would be welcome.

@HANDLERS.register(("Alexa.StepSpeaker", "AdjustVolume"))
async def async_api_adjust_volume_step(hass, config, directive, context):
    """Process an adjust volume step request."""
    # media_player volume up/down service does not support specifying steps
    # each component handles it differently e.g. via config.
    # This workaround will simply call the volume up/Volume down the amount of steps asked for
    # When no steps are called in the request, Alexa sends a default of 10 steps which for most
    # purposes is too high. The default  is set 1 in this case.
    entity = directive.entity
    volume_int = int(directive.payload["volumeSteps"])
    is_default = bool(directive.payload["volumeStepsDefault"])
    default_steps = 1

    if volume_int < 0:
        service_volume = SERVICE_VOLUME_DOWN
        if is_default:
            volume_int = -default_steps
    else:
        service_volume = SERVICE_VOLUME_UP
        if is_default:
            volume_int = default_steps

    data = {ATTR_ENTITY_ID: entity.entity_id}

    for _ in range(0, abs(volume_int)):
        await hass.services.async_call(
            entity.domain, service_volume, data, blocking=False, context=context
        )

    return directive.response()

Posts: 1

Participants: 1

Read full topic

@jim1977 wrote:

Hello!
I’ve currently got an ever expanding file in this format which is a constant print out from a serial port.
This is one line:

{'FW': '0308', 'SOC': '999', 'Relay': 'OFF', 'PID': '0x203', 'H10': '3', 'BMV': '700', 'TTG': '1692', 'H12': '0', 'H18': '690', 'I': '-6216', 'H11': '0', 'Alarm': 'OFF', 'CE': '-143', 'H17': '578', 'P': '-73', 'AR': '0', 'V': '11759', 'H8': '15632', 'H9': '93', 'H2': '-145', 'H3': '-62393', 'H1': '-68223', 'H6': '-478196', 'H7': '4', 'H4': '3', 'H5': '0'}

As I think the lines dont always get printed in complete sections. Hassio file sensor has problems setting sensors up on boot.

I need to read and print complete lines of this to a file, maybe once every 10 seconds. So HA has a chance to read and setup file sensors.

Can anyone supply me with a script that can do this?

The current serial printed script resides at:

/usr/share/hassio/homeassistant/vedirect-bmv/bmv700.txt

The new parsed file can also print to this folder.

Any help greatly appreciated!

Posts: 1

Participants: 1

Read full topic

@skonaguy wrote:

I have been having lots of issues since upgrading to 101 from ~86. recorder, history, and logger have all stopped working. My home-assistant_v2.db is also almost 11 GB! I’ve tried to purge it but recorder won’t set itself up. Nor will history or logger. I’ve renamed the …db to …db.bak so that it effectively does not exist yet HA does not fix itself and create a new one on restart. I’m on debian and apt-get says sqlite3 is good when i try to install it.

I’m thinking maybe uninstall sqlite and reinstall but that is a bit drastic and may break HA in other ways.

Advice?

Here is my HA log

Setup failed for history: Could not set up all dependencies.

9:06 PM setup.py (ERROR)

Unable to set up dependencies of history. Setup failed for dependencies: recorder

9:06 PM setup.py (ERROR)

Setup failed for recorder: Integration failed to initialize.

9:06 PM setup.py (ERROR)

Error during connection setup: No module named ‘_sqlite3’ (retrying in 3 seconds)

9:06 PM components/recorder/init.py (ERROR) - message first occured at 9:05 PM and shows up 10 times

Setup of recorder is taking over 10 seconds.

9:06 PM util/async_.py (WARNING)

Posts: 2

Participants: 2

Read full topic

@rontaylor wrote:

I am very new to this but so far this is what I have.

On a RPi 3, with a 32GB SD card I am running Home Assistant 0.101.3, a USB Z-Wave gen 5 stick, a ZW120 door/window sensor, a ZW100 Multisensor 6 and a couple of ZW098 LED Bulbs.

This is what I have so far.

image.png1917×937 400 KB

I like the default overview and want to use it until I learn more and then maybe step up to doing my own Lovelace. My coding skills were OK at best way back when … some 40 years ago.

All I want to achieve is to learn how to turn the “22” to “Open” and “23” to “Closed” so that it’s more readable to others.

Can someone show me how it’s done please.

I have tried various things in my configuration.yaml file but generally seem to stuff it up.
I did read somewhere about changing device classes to a door class and tried that in customisation but when looking at that entity there was a device class but no door class so ???

Anyway any simple way would be most appreciated.

Posts: 5

Participants: 4

Read full topic

@Matt_Barnes wrote:

So yesterday I could not duckdns into HA. Thought I had had a power cut, got home, had not had power cut.

I can SSH into Hassio using Termius, cannot connect for some reason using terminal on mac though

I can connect to the pi though and view the folders and log and have tried hassio hassos restart which seemed to work fine.

The app also does not work.

On safari using duckdns I get “unable to connect try again”
On the App it says connection error

IP address is still the same, I have powered it off, restarted using SSH but can still not get into it other than through SSH on terminus.

The log looks fine (to a newbie). What has happened?

2019-11-08 07:40:49 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for huesensor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_pauselounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_playlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_fflounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_rwlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_bbconelounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_bbctwolounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_skyatlanticlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_skyonelounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_skynewslounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_skyf1lounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_chuplounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_chdnlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_selectlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_uplounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_downlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_leftlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_rightlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_ilounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_dismisslounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_sidebarlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_homelounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_tvguidelounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_skylounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:52 WARNING (MainThread) [homeassistant.components.template.switch] Template sensor skyq_recordlounge has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.
2019-11-08 07:40:55 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for skyq which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-11-08 07:40:55 WARNING (SyncWorker_9) [custom_components.skyq.media_player] True
2019-11-08 07:40:56 WARNING (MainThread) [homeassistant.setup] Setup of person is taking over 10 seconds.

I am running HA on a Pi and have been for about 9 months.
I have basically no knowledge of SSH so any commands that might help would be great.

ps, when I try and access via Terminal on Mac I get the below:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for hassio.local. has changed,
and the key for the corresponding IP address 192.168.1.117
is unchanged.

Now I haven’t used Terminal for ages so this might not be a new issue but a little concerning, and no knowledge on how to fix it.

Thanks in advance

Posts: 4

Participants: 1

Read full topic

@weado wrote:

Hello,
I did an automation to my light turn on 5 minutes before my alarm clock ring.
My automation work well, but my light, turn on, but without apply my config, and in my case the bightness (my light turn on at most). You can find my automation bellow :

- alias: morning_alarm
  trigger:
    - platform: template
      value_template: '{{states.sensor.heure_alarme.state == states.sensor.galaxy_s8_alarm_sensor.state}}'
  action:
    - service: light.turn_on
      entity_id: light.led_salon
      data:
        brightness: 50

Do you have an idea? My light is a Z-wave FDG-212

Posts: 4

Participants: 2

Read full topic

@kaciker wrote:

I’ve developer account in NEST (Work with NEST) , but after 31/8/19 we can’t write in NEST, only read. Because NEST was sold to google and google don’t aloww to collect your own data, and less to write on NEST… So my integration in Hassio only alowed me to show info but not change it.
Making a integration in IFTTT (Webhook and NEST) now is possible to send instructions to NEST

You need a developer account with api Key in Home assistant, and api key in IFTTT for NEST as well

Posts: 1

Participants: 1

Read full topic

@Jiran wrote:

Hello is it possible to show switch state in opposite way (talking about tasmota switch)? If tasmota is ON to show OFF in HA and vice versa.

Thanks

Posts: 8

Participants: 2

Read full topic

@ravet007 wrote:

I need some help, I have the Aqara hub V2 (With the alarm) and several Sonoff door/window sensors. The Rf bridge has been Tasmotised and I have set them up in Home assistant and homekit. I want the door window sensors to trigger the Aqara gateway alarm through an automation at night (11 pm to 6 am). I tried doing this in the home app but could not. I tried to add the aqara hub to home assistant, but that didn’t work either. Any ideas? Thanks is advance.
Maybe there is a way to create a ZigBee switch (sensor), link all sonoff sensors to trigger the ZigBee Switch and that in turn could trigger the alarm?
I’m lost an maybe even overthinking this one.

Posts: 9

Participants: 3

Read full topic

@Mariusthvdb wrote:

Just accidentally notice a ‘?’ in the text stops tts from playing on:

only pronounces Are you happy…

this is the script I use for the message:

script:
  intercom_text_message:
    alias: 'Intercom text message'
    sequence:
      - condition: template
        value_template: >
          {{ is_state('input_boolean.announce_intercom', 'on') }}
      - service: media_player.volume_set
        data_template:
          entity_id: >
            {{states('sensor.intercom')}}
          volume_level: >
            {{  states('input_number.intercom_volume')|float }}
#            # {{ states('sensor.intercom_volume')|float  }}
      - service: tts.google_say
        data_template:
          language: >
            {{states('input_select.intercom_language')|lower}}
          entity_id: >
            {{states('sensor.intercom')}}
          message: >
            {{states('input_text.message')}}

seems a bug?
my message logging system shows the complete input_text.message, so I know that isn’t truncated in any way.

so far, only the ? stops the speech, tried a few others (/,>,!,*) and they all are either pronounced, or ignored)

Posts: 7

Participants: 5

Read full topic

@maurizio53 wrote:

Can somebody help me to understand in simple words what has changed about mqtt in the latest release? I upgraded to 0.101.3 but my HA doesn’t run anymore…
I get tons of error about all entries in my configuration and i only disabled api_password before upgrading.
Downgrading to the previous all turned back to work again

Posts: 11

Participants: 4

Read full topic

@fjnieto wrote:

Hello! I would like to customize the user view so that they cannot access all the devices. How can I do it?

Posts: 2

Participants: 2

Read full topic