Hey all…
I’m using Clouflare to passthrough traffic to my domain and to my HomeAssistant subdomain.

I’ve configured HomeAssistant HTTP part this way:

http:
    ip_ban_enabled: true
    login_attempts_threshold: 5
    use_x_forwarded_for: true
    trusted_proxies:
      - !secret traefik_ip
      - !secret router_ip
   # Cloudflare Servers:
      - 173.245.48.0/20
      - 103.21.244.0/22
      - 103.22.200.0/22
      - 103.31.4.0/22
      - 141.101.64.0/18
      - 108.162.192.0/18
      - 190.93.240.0/20
      - 188.114.96.0/20
      - 197.234.240.0/22
      - 198.41.128.0/17
      - 162.158.0.0/15
      - 104.16.0.0/12
      - 172.64.0.0/13
      - 131.0.72.0/22

Yet - when accessing HomeAssistant (through Cloudflare) I see this:

Refresh token for https://hass.myhost.com/
Created at April 15, 2020, 11:32 AM
Last used at September 14, 2020, 12:55 PM from 172.68.xx.xx

As far as I understand - 172.64.0.0/13 subnet should cover my case (172.68.xx.xx)

I also have a docker container for whoami where I’m seeing this:

X-Forwarded-For: 31.154.xx.xx, 172.68.xx.xx
...
X-Real-Ip: 172.68.xx.xx

So the X-Forwarded-For does forward the right data, but for some reason HomeAssistant doesn’t work with it.

How to troubleshoot this? Do I have some wrong configuration?

Thanks

1 post - 1 participant

Read full topic

Hi All,

I’ve been running the new QT-Openzwave addon and beta Z-Wave Integrations with Mosquitto broker
Current (Ver: 5.1) for over a month, with only the dimming issue, which was fixed in 0.114. Suddenly, without any updates or changes, I’ve lost all my node devices / entities; the addon is now crashing and I can’t connect OZWAdmin (Ver: 0.1.74).

I’m confirmed:

• The dongle is still working, via the Simplicity Studio Z-Wave controller;
• HA can still see the dongle port and;
• HA still includes the device and entities for the dongle.

I’ve tried removing the addon and integration, restarting HA and reinstalled them, but the addon still crashes. I’ve also tried going back to a earlier snapshot prior to the issue, and the addon still crashes.

I’ve included the addon logs from a fresh host restart below.

Any fixes, tips or ideas would be appriciated?

HA: 0.114.4
Installation Type: Home Assistant Supervised
Supervisor: 243
Host: Ubuntu 20.04.1 LTS - unsupported.
Docker: 19.03.12
USB/Z-wave Dongle: AeoTec ZW090-C

Thanks in advance.

Neil

‘’’
[20200913 21:55:11.073 BST] [ozw.nodes] [debug]: Removing Node QVariant(int, 41) 0
[20200913 21:55:11.073 BST] [ozw.notifications] [debug]: Notification pvt_nodeRemoved 42 Thread: 0x7fec4754bd48
[20200913 21:55:11.073 BST] [ozw.nodes] [debug]: Removing Node QVariant(int, 42) 0
[20200913 21:55:11.073 BST] [ozw.notifications] [debug]: Notification pvt_nodeRemoved 43 Thread: 0x7fec4754bd48
[20200913 21:55:11.073 BST] [ozw.nodes] [debug]: Removing Node QVariant(int, 43) 0
[20200913 21:55:11.073 BST] [ozw.notifications] [debug]: Notification pvt_nodeRemoved 44 Thread: 0x7fec4754bd48
[20200913 21:55:11.073 BST] [ozw.nodes] [debug]: Removing Node QVariant(int, 44) 0
[20200913 21:55:11.073 BST] [ozw.notifications] [debug]: Notification pvt_nodeRemoved 45 Thread: 0x7fec4754bd48
[20200913 21:55:11.073 BST] [ozw.nodes] [debug]: Removing Node QVariant(int, 45) 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 ***************************************************************************
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 ********************* Cumulative Network Statistics *********************
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 *** General
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Driver run time: . . . 0 days, 0 hours, 9 minutes
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Frames processed: . . . . . . . . . . . . . . . . . . . . 91
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Total messages successfully received: . . . . . . . . . . 91
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Total Messages successfully sent: . . . . . . . . . . . . 111
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 ACKs received from controller: . . . . . . . . . . . . . 66
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 *** Errors
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Unsolicited messages received while waiting for ACK: . . 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Reads aborted due to timeouts: . . . . . . . . . . . . . 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Bad checksum errors: . . . . . . . . . . . . . . . . . . 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 CANs received from controller: . . . . . . . . . . . . . 45
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 NAKs received from controller: . . . . . . . . . . . . . 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Out of frame data flow errors: . . . . . . . . . . . . . 0
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Messages retransmitted: . . . . . . . . . . . . . . . . . 5
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 Messages dropped and not delivered: . . . . . . . . . . . 42
[20200913 21:55:11.074 BST] [ozw.library] [debug]: Always - Node: 0 ***************************************************************************
[20200913 21:55:11.074 BST] [ozw.library] [info]: Info - Node: 0 Saving Cache
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 1 Cache Save for Node 1 as its QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 2 Skipping Cache Save for Node 2 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 3 Skipping Cache Save for Node 3 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 4 Skipping Cache Save for Node 4 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 5 Skipping Cache Save for Node 5 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 6 Skipping Cache Save for Node 6 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 7 Skipping Cache Save for Node 7 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 8 Skipping Cache Save for Node 8 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 9 Skipping Cache Save for Node 9 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 10 Skipping Cache Save for Node 10 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 11 Skipping Cache Save for Node 11 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 12 Skipping Cache Save for Node 12 as its not past QueryStage_CacheLoad
[20200913 21:55:11.075 BST] [ozw.library] [info]: Info - Node: 13 Skipping Cache Save for Node 13 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 14 Skipping Cache Save for Node 14 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 15 Skipping Cache Save for Node 15 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 16 Skipping Cache Save for Node 16 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 17 Skipping Cache Save for Node 17 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 18 Skipping Cache Save for Node 18 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 19 Skipping Cache Save for Node 19 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 20 Skipping Cache Save for Node 20 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 21 Skipping Cache Save for Node 21 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 23 Skipping Cache Save for Node 23 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 24 Skipping Cache Save for Node 24 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 25 Skipping Cache Save for Node 25 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 27 Skipping Cache Save for Node 27 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 28 Skipping Cache Save for Node 28 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 29 Skipping Cache Save for Node 29 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 30 Skipping Cache Save for Node 30 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 31 Skipping Cache Save for Node 31 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 32 Skipping Cache Save for Node 32 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 33 Skipping Cache Save for Node 33 as its not past QueryStage_CacheLoad
[20200913 21:55:11.076 BST] [ozw.library] [info]: Info - Node: 36 Skipping Cache Save for Node 36 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 38 Skipping Cache Save for Node 38 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 39 Skipping Cache Save for Node 39 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 40 Skipping Cache Save for Node 40 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 41 Skipping Cache Save for Node 41 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 42 Skipping Cache Save for Node 42 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 43 Skipping Cache Save for Node 43 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 44 Skipping Cache Save for Node 44 as its not past QueryStage_CacheLoad
[20200913 21:55:11.077 BST] [ozw.library] [info]: Info - Node: 45 Skipping Cache Save for Node 45 as its not past QueryStage_CacheLoad
[20200913 21:55:11.079 BST] [ozw.library] [info]: Info - Node: 0 Stopping DNSThread
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Detail - Node: 19 Removing current message
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.208 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.209 BST] [ozw.library] [debug]: Debug - Node: 0 Value Deleted
[20200913 21:55:11.211 BST] [ozw.library] [info]: Info - Node: 0 mgr, Driver for controller /dev/serial/by-id/usb-0658_0200-if00 removed
[20200913 21:55:11.211 BST] [ozw.manager] [debug]: Driver Removed for “/dev/serial/by-id/usb-0658_0200-if00”
[20200913 21:55:11.211 BST] [ozw.manager] [debug]: OZW Serial Port Closed
[20200913 21:55:11.211 BST] [ozw.daemon] [info]: Shutting Down “ozwdaemon” Version: “0.1.0”
[20200913 21:55:11.212 BST] [ozw.daemon] [info]: OpenZWave Version: “1.6.1210”
[20200913 21:55:11.212 BST] [ozw.daemon] [info]: QT-OpenZWave Version: “1.2.0”
[20200913 21:55:11.212 BST] [ozw.daemon] [info]: QT Version: 5.12.5
In exit
[cont-finish.d] executing container finish scripts…
[cont-finish.d] mqtt.sh: executing…
1600030511: mosquitto version 1.6.8 terminating
1600030511: Saving in-memory database to /data/mosquitto.db.
[21:55:11] INFO: Ensure upstream MQTT server has the correct OZW status
[cont-finish.d] mqtt.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
‘’’

1 post - 1 participant

Read full topic

Hi,

i’m a Newbie with Home Assistiant.
I want switch on a light,
when sun elevation is under -3,5, but only, if time is between 16:30 and 22:00 and somebody is at home.

The light should always switch off at 22:00 or elevation is higher as… or nobody at home.

My automation looks like that:

- alias: 'Licht2 an'
  trigger:
    platform: template
    value_template: >
      {% set an = "16:30" %}
      {% set aus = "21:59" %}
      {{ as_timestamp(now().date())+((an.split(":")[0] | int) *60*60)+((an.split(":")[1] | int) *60)
         < as_timestamp(now())
         < as_timestamp(now().date())+((aus.split(":")[0] | int) *60*60)+((aus.split(":")[1] | int) *60)
       }}
  condition:
    condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.elevation
        below: -3.5
      - condition: numeric_state
        entity_id: sensor.people_home
        above: 0
  action:
    service: switch.turn_on
    entity_id: switch.shelly1

- alias: 'Licht aus'
  trigger:
    - platform: time
      at: "22:00:00"
    - platform: numeric_state
      entity_id: sensor.elevation
      above: 10
    - platform: numeric_state
      entity_id: sensor.people_home
      below: 1
  action:
    service: switch.turn_off
    entity_id: switch.shelly1

It works !?
Is there a better solution for that?

Thanks

1 post - 1 participant

Read full topic

Hello!
I created a MQTT switch for the Shelly1. But everytime I reboot the Home Assistant Host- the Shelly 1 toggles. Is it a bug? Or have I missed something in my configruation?

Thanks for your help!

switch:
  - platform: mqtt
    name: "Garagentor"
    state_topic: "shellies/shelly1-xxx/relay/0"
    command_topic: "shellies/shelly1-xxx/relay/0/command"
    payload_on: "on"
    payload_off: "off"
    state_on: "on"
    state_off: "off"
    optimistic: false
    qos: 0
    retain: true

1 post - 1 participant

Read full topic

Hear me out, please.
I’m thinking of an automation for a person with hearing problems. I wanted to create automation with sonoff switch, which on the top of each hour turn light on and of (e.g. if its 2, then two times, 3 - 3 times and so on). I know I could write a lengthy code for each hour, but perhaps there is a shortcut for that. Any thoughts? Thank you

1 post - 1 participant

Read full topic

I asked for some help on the forums with this, and it was suggested I post in the forums as it may be a little complex. Hoping someone can help get me started!

In short, I currently have a device configured like this (topic, etc has been simplified for clarity):

- platform: mqtt
  name: "My Device"
  state_topic: "things/my-device/mode/read"
  state_on: "3"
  state_off: "4"
  command_topic: "things/my-device/mode/write"
  payload_on: "{\"value\":\"3\"}"
  payload_off: "{\"value\":\"4\"}"
  value_template: "{{ value_json.value }}"

This works great. Toggling the switch writes either {"value":"3"} or {"value":"4"} to the command topic as it should, and the state is shown correctly.

However, the device actually has 2 switches (we’ll call them A and B), not one, and they are both reported by same MQTT topic. The values are:

Value |  A  |  B
------|-----|---
1     | on  | off
2     | off | on
3     | on  | on
4     | off | off

Until now, I’ve only been interested in toggling both switches together, so switching the mode value from 3 to 4 worked fine. But now I’d like to toggle them independently.

I think what I need is a template switch, but I’m unclear how to combine that with MQTT. Again, I think the way it should work is that I make two switches - A and B.

A would be configured such that it is on if value is 1 or 3, else off. B would be configured to be on if value is 2 or 4. Then the payload_on and payload_off fields for each switch would need to check the value of the other switch and set the appropriate value. Am I on the right lines?

Any help would be appreciated!

1 post - 1 participant

Read full topic

I have the dialogflow integration working from the google actions test console, but when I speak to a google home device, there is no sign that my intents are being recognized. E.g., I enter “Home temperature?” in the console, I can see it calling my webhook and matching my intent script, and responding with “The temperature is 72 degrees.”

But when I say: “Hey Google, Home temperature” to my google home device, it says my nest device is not registered, or something like that. I.e., it is what it would say if I did not have smart home action intents registered with google.

I am unable to find anything in the docs or by web searches which says what, if anything, I am supposed to do to get google assistant to recognize my custom intents.

Does anyone have this working? The Smart Home integration is not supposed to require a lead in, like “Hey Google, Ask whoever, Home temperature”, Right? That is only for “conversation mode” integrations, correct? Please any advice for what I am missing or how I can troubleshoot this!

Thanks! Dick

1 post - 1 participant

Read full topic

Anyone have any thoughts on how to fix?

I dont see any obvious errors in the file like missing { etc but I am a dabbler...

Running in docker(portainer) on a synology NAS, node-red, HACS.

Manually tried to remove the sonos-alarm integration after it didnt delete through the UI.

Also been having trouble with it taking 30+mins to restart HA with it throwing an error about trying to start the recorder integration but I havent been able to find any reference to that integration anywhere to know where its coming from. At the moment it isnt getting that far.



Thanks



ERROR (SyncWorker_0) [homeassistant.util.json] Could not parse JSON content: /config/.storage/core.config_entries

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/util/json.py", line 32, in load_json

return json.loads(fdesc.read()) # type: ignore

File "/usr/local/lib/python3.8/json/__init__.py", line 357, in loads

return _default_decoder.decode(s)

File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode

obj, end = self.raw_decode(s, idx=_w(s, 0).end())

File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode

raise JSONDecodeError("Expecting value", s, err.value) from None

json.decoder.JSONDecodeError: Expecting value: line 313 column 9 (char 11908)

1 post - 1 participant

Read full topic

Hi there, newbie here.

So I have an Annke 4CH NVR (N44WBF0) and after a lot of searching I managed to get a live stream from the NVR and played it successfully via ffplay:

.\ffplay -headers "Authorization: Basic [base64user:pass]=" -i "http://[nvr_address]/livestream/21?action=play&media=video_audio_data/track=video"

This plays successfully via ffplay and was also able to stream it from ffmpeg to VLC. The problem I have is when adding it to Home Assistant.This is what I have:

camera:

  - platform: ffmpeg

    input: "-headers 'Authorization: Basic YWRtaW46NjQ1NjU=' -i 'http://[nvr_address]/livestream/21?action=play&media=video_audio_data/track=video'"

    name: "Test"

And this is the result (log output):
av.error.FileNotFoundError: [Errno 2] No such file or directory: "'http://[nvr_address]/livestream/21?action=play&media=video_audio_data/track=video'"

If I try without the -header argument, I obviously get the 401 Not authorized error.
Server returned 401 Unauthorized (authorization failed): 'http://[nvr_address]/livestream/21?action=play&media=video_audio_data/track=video'

So the question is, how can I pass the -header Authorization argument to be able to authenticate and then get the stream going?

Cheers!

1 post - 1 participant

Read full topic

I have a few Curtain Motors from Aqara, model ZNCLDJ11LM. Previously I had it configured to work zigbee2mqtt and it was working pretty good. But due to issues with reliability on z2m side, I decided to switch to ZHA build in HA. These motors have paired successfully, mostly I can control motor, but…

1. It has created 4 different entities, where “switch” and “cover” entities are mostly doing same, but both are a little buggy
   

   Screenshot 2020-09-14 at 16.34.12924×504 12.7 KB

2. Only on start cover entity showed status open or close, after this, it only shows opening/closing (so that it is at the operation of opening/closing curtain)
   

   Screenshot 2020-09-14 at 16.35.55816×652 21.6 KB
   
   I can properly set new position using slider, but it is not being updated properly if I just use the close/open option

3. On the cover entity, we have 3 buttons, but because status is not being updated it is mostly stuck that the stop button works when close/open buttons are active randomly

4. Limits look like are set properly and direction of movement also. I can properly set a new position using the slider, but it is not being updated properly if I just use the close/open button.

5. For now mostly on/off switch is working correctly. It is being updated if I only use this button. I can toggle curtain state without a problem, but I have one automation that only opens the window at 40%.

I can help to debug it if you want. My Zigbee coordinator is flashed Sonoff Zigbee bridge

1 post - 1 participant

Read full topic

Hi all,

I have 2 eufycam 2’s but was interested if it is possible to have the cameras in Home Assistant?

I do not see any integrations from Home Assistant.

1 post - 1 participant

Read full topic

Hi there,

I manage to add the HA integration of IPMA (Portuguese weather) but when I add two configs In integrations, one for hourly and another one for daily, i only get one entity to use (the last one). How can I user daily/hourly in different cards?

Thanks.
Pedro.

1 post - 1 participant

Read full topic

I’m looking at migrating from Hubitat and am wondering how to create virtual devices, or replicate the end result. For a specific example I have a ZWave outlet that I use to control a space heater and a corresponding automation to allow me to turn it on, and keep it on via Google Assistant.

• Craft Room Heater - Outlet is the actual ZWave+ outlet, it is not exposed to Google
• Craft Room Heater is a virtual switch, it is exposed to Google

Here is the Hubitat rule:

The result/goal of the rule is:

• I can say “OK Google turn on the Craft Room heater” which results in Assistant turning on the virtual switch which triggers the rule to turn on the actual outlet
• After 30 minutes turn off the virtual switch, notify me that the heater is turning off in 1 minute, wait 1 minute, turn off the real outlet
• If I say “OK Google turn on the Craft Room heater” the virtual switch gets turned back on canceling the wait and resetting the 30 minute timer
• If I say “OK Google turn off the Craft Room heater” at any time, the actual outlet gets turned off and the whole wait gets cancelled.

The delay and notify I get how to do. I’m not sure how to emulate the virtual switch that turns off 1 minute before the real switch.

1 post - 1 participant

Read full topic

Hi, I try the service vacuum.clean_spot and I don’t understand how it work,

it set a spot in the middle of my map but how can I tell where I want it to go ?

1 post - 1 participant

Read full topic

I’ve been an IFTTT user for a couple of years, mainly for the integration that it offers for my Google Home devices (i.e. voice controlling my HA devices), but don’t want to move to an IFTTT subscription. I currently run Home Assistant 0.65.0 in a Docker container on a Lubuntu VM.
Having taken some first steps trying to integrate Home Assistant with Google Assistant/Google Home a couple of years ago, I couldn’t get it to work reliably (hence why I ended up using IFTTT). I was wondering if newer versions of Home Assistant offered better/easier integration with Google Assistant/Google Home?
I’ve avoided any upgrades to Home Assistant so far as I don’t want to spend hours/days dealing with backwards compatibility issues with my HA config (and I already have it doing everything I need anyway). However if a newer release would offer an easy path to Google integration I think now might be the time to take the plunge.
I was wondering if anyone could advise:

1. Does the current HA release offer significantly better or easier Google integration than v0.65.0?
2. How straightforward would the HA upgrade process be from 0.65.0 to current version?

1 post - 1 participant

Read full topic

I’m seeing an error in my logs when I try to use the “profile” attribute when setting a scene for a group of hue lights. I’m wondering if this is a bug or if I should be doing something differently.

Background
I would like to use my custom light_profiles.csv so that when the scene activates it uses a specific x,y, brightness setting for all the bulbs so that I have a central way to control that for all scenes.

light_profiles.csv

id,x,y,brightness
custom_nightlights,0.4578,0.41,25
custom_relax,0.4578,0.41,77
custom_nightlights_cool,0,0,68
custom_bright,0.4578,0.41,191
halloween_orange,0.615,0.374,95
halloween_purple,0.294,0.122,95
christmas_green,0.172,0.742,95
christmas_red,0.56,0.326,95
christmas_white,0.317,0.331,110
custom_concentrate,0.314,0.331,255

Scene

- id: '1234566789'
  name: Living room nightlights
  entities:
    light.living_room_mood_lights:
      effect_list:
      - colorloop
      - random
      friendly_name: Living Room Mood Lights
      is_hue_group: true
      max_mireds: 500
      min_mireds: 153
      state: 'on'
      supported_features: 63
      profile: custom_nightlights

This works correctly and has for years, but I also see the message below in my logs.

2020-09-14 10:50:00 WARNING (MainThread) [homeassistant.components.light.reproduce_state] The use of other attributes than device state attributes is deprecated and will be removed in a future release. Invalid attributes are ['profile']. Read the logs for further details: https://www.home-assistant.io/integrations/scene/

Any ideas on what I might be doing wrong?

1 post - 1 participant

Read full topic

I am try to see if there is a way to get the hs z-net network z-wave plus controller sense. The device is Raspberry Pi 3 with a EZZee, EZZeeUS, by Express Controls LLC, Cert ID: ZC10-15020001

1 post - 1 participant

Read full topic

ThingSpeak configuration help:

I entered the configuration in the configuration.yaml file

thingspeak:
  api_key: OOOXXXXKEY WRITE
  id: 27XXXXX
  whitelist: sensor.Sonda_Alta_temperature

but I don’t see the entity the channel is private and there are two fields

Does the component need to be installed? If so, how should I do?

1 post - 1 participant

Read full topic

Hi there,

I’m new here and ts my first try with RPI and with HA.

Hardware:
RPI 4b 4GB
RFXcom rfxtrx433XL USB

Software:
HA 0.113.0

Configuration.yaml

Configure a default setup of Home Assistant (frontend, api, etc)

default_config:

Text to speech

tts:

• platform: google_translate

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

logger:
default: debug

RFXcom

rfxtrx:
device: /dev/ttyUSB1

After adding RFXtrx to the config HA installed the integration for RFXcom.

The issue is that I dont see the rfxtrx by “entity”
Also i dont see new devices by “entity”

What I tried so far.

Followed this tutorial https://www.youtube.com/watch?reload=9&v=zcjNvSMG-hg
and this one https://www.home-assistant.io/integrations/rfxtrx/

Started with HA 0.114.4
After reading topic RFXCOM ok with 0.113, nok with 0.114.x i upgraded HA to Beta 0.115.0b9 same issue
Downgraded HA to 0.113.0 same issue

Connect the RFXcom to a windows machine upgrade the firware in the Rfxcom manager i see its working, getting all kind of info in the screen.

Connected the RFXcom to another USB port on the RPI

In the configuration.yaml
Changed configuration too.

rfxtrx:
automatic_add: true
device: /dev/ttyUSB1

I dont know what to try anymore.

1 post - 1 participant

Read full topic

I am building a large garden room and and starting to think about the electrics. I currently automate a lot of my lights and switches, using quite a few Sonoff Mini’s flashed with Tasmota, MQTT to Home Assistant, and although this method works well, I am thinking of a more centralised solution. For example, a 16 channel relay, controlled by Arduino, where everything runs back to the relay, mains plugs, lights, light switches, etc. Although Im sure this would work and be a good centralised system, I’m not sure on how I would go about getting this signed off by an electrician, or installed by an electrician. Or, is there a better option?

1 post - 1 participant

Read full topic