@compbl wrote:

I upgraded to 0.107 and have been doing some cleanup. Had a few config errors for obsolete things in 107 which I have fixed.

I have one stubborn error that I cannot get rid of. It is referring to my Harmony Hub.

Invalid config for [group]: [control] is an invalid option for [group]. Check: group->group->harmonytv->control. (See /config/configuration.yaml, line 170).

Since I really don’t use the Harmony Hub/Remote I have removed just about everything related to it that I can find, and yet the error still persists.

Any help would be appreciated!!

Posts: 2

Participants: 2

Read full topic

@agneev wrote:

Hi,

I did a supervised installation on my RPi.

I screwed up the configuration.yaml and now HA won’t start up. How do I undo my changes/edit the config file?

Posts: 1

Participants: 1

Read full topic

@Ryan911199 wrote:

I am having a problem that once i add light groups to home assistant i can use the light groups to control everything for about one min maybe two but then when i flip the switch of set one up as a single light i can no longer control the group or individual device.it renders the whole thing unusable. i have pasted my config file maybe there is a problem in that. i have tried running this on a pi, on a VM, in docker but i always get the same result. please if you all could help it would be greatly appreciated.

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

default_config:

Uncomment this if you are using SSL/TLS, running in Docker container, etc.

http:

base_url: example.duckdns.org:8123

Text to speech

tts:

• platform: google_translate

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

frontend:
themes: !include_dir_merge_named themes
weather:

• platform: darksky
  api_key: 772695ee44cc981bedd241550c0321e7

august:
login_method: phone
username: “+15095993288”
password: FLgr@mmy9

input_boolean:
ryland_is_home:
name: ryland is home
initial: on
icon: mdi:account
shaun_is_home:
name: shaun is home
initial: on
icon: mdi:account
trevor_is_home:
name: trevor is home
initial: on
icon: mdi:account
house_guest:
name: house Guest
initial: on
icon: mdi:account
home_occupied:
name: occuped
initial: on
icon: mdi:account

yeelight:
devices:
192.168.1.7:
name: rylands room 1
192.168.1.11:
name: rylands room 2
192.168.1.28:
name: hall
192.168.1.12:
name: living room 1
192.168.1.13:
name: living room 2
192.168.1.6:
name: living room 3
192.168.1.4:
name: laundry room 1
192.168.1.8:
name: laundry room 2
192.168.1.14:
name: shauns room 1
192.168.1.22:
name: shauns room 2
192.168.1.38:
name: bathroom 1
192.168.1.37:
name: bathroom 2
192.168.1.3:
name: kitchen 1
192.168.1.10:
name: kithcen 2
192.168.1.36:
name: dining room 1
192.168.1.41:
name: dining room 2
192.168.1.35:
name: rylands bathroom 1
192.168.1.34:
name: rylands bathroom 2
192.168.1.40:
name: trevors Room 1
192.168.1.39:
name: trevors Room 2

light:

• platform: group_1
  name: house
  entities:
  • light.bathroom_1
  • light.bathroom_2
  • light.dining_room_1
  • light.dining_room_2
  • light.kitchen_1
  • light.kithcen_2
  • light.laundry_room_1
  • light.laundry_room_2
  • light.living_room_1
  • light.living_room_2
  • light.living_room_3
  • light.rylands_bathroom_1
  • light.rylands_bathroom_2
  • light.rylands_room_1
  • light.rylands_room_2
  • light.shauns_room_1
  • light.shauns_room_2
  • light.hall
  • light.trevors_room_1
  • light.trevors_room_2
• platform: group_2
  name: living room
  entities:
  • light.living_room_1
  • light.living_room_2
  • light.living_room_3
• platform: group_3
  name: rylands room
  entities:
  • light.rylands_bathroom_1
  • light.rylands_bathroom_2
  • light.rylands_room_1
  • light.rylands_room_2
• platform: group_4
  name: bathroom room
  entities:
  • light.bathroom_1
  • light.bathroom_2
• platform: group_5
  name: dining room
  entities:
  • light.dining_room_1
  • light.dining_room_2
• platform: group
  name: kitchen
  entities:
  • light.kitchen_1
  • light.kithcen_2
• platform: group_6
  name: laundry room
  entities:
  • light.laundry_room_1
  • light.laundry_room_2
• platform: group_7
  name: living room
  entities:
  • light.living_room_1
  • light.living_room_2
  • light.living_room_3
• platform: group_8
  name: shauns room
  entities:
  • light.shauns_room_1
  • light.shauns_room_2
• platform: group_9
  name: trevors room
  entities:
  • light.trevors_room_1
  • light.trevors_room_2

Posts: 3

Participants: 3

Read full topic

@tyjtyj wrote:

How to create templete sensor different last 24 hours ?

Trying to create sensor for new corona virus case per day

Posts: 2

Participants: 1

Read full topic

@Justin_Wuffen wrote:

Hello all,

I was wondering if there is a way to make create a carousel of the views. So that after a few minutes the page change to a view further?

greetings justin

Posts: 1

Participants: 1

Read full topic

@daggy72 wrote:

I am trying to get some BLE Beacons/Sensors to work in HomeAssistant but I am having some troubles with the MQTT JSON file the Gateway broadcasts. It’s not one topic per sensor but one JSON file containing an array including all the various sensors and beacons.

hardware:

• a Minew G1 Gateway
• various Minew S1 Humidity and Temperature sensors
  attached is part of the MQTT JSON files the gateway broadcasts every xx seconds

Objective: I would like to create sensors for each parameter of each device. The only way to distinguish the devices is via their MAC addresses. I know for example that the MAC address “AC233FA29263” is the device in my living room. I would like to log/record the Temperature and Humidity as well as the rssi and battery levels (to create automations that will alert me when the devices are offline or the battery level drops below a certain level)

MQTT JSON output:

[
    {
        "timestamp": "2020-03-29T16:58:11.341Z",
        "type": "Gateway",
        "mac": "AC233FC064F3",
        "gatewayFree": 87,
        "gatewayLoad": 1.17
    },
    {
        "timestamp": "2020-03-29T16:58:11.341Z",
        "type": "iBeacon",
        "mac": "AC233FA29261",
        "bleName": "",
        "ibeaconUuid": "E2C56DB5DFFB48D2B060D0F5A71096E0",
        "ibeaconMajor": 0,
        "ibeaconMinor": 0,
        "rssi": -51,
        "ibeaconTxPower": -59,
        "battery": 0
    },
    {
        "timestamp": "2020-03-29T16:58:11.525Z",
        "type": "S1",
        "mac": "AC233FA29261",
        "bleName": "",
        "rssi": -64,
        "battery": 100,
        "temperature": 20.24,
        "humidity": 57.34
    },
    {
        "timestamp": "2020-03-29T16:58:11.530Z",
        "type": "iBeacon",
        "mac": "AC233FA29263",
        "bleName": "",
        "ibeaconUuid": "E2C56DB5DFFB48D2B060D0F5A71096E0",
        "ibeaconMajor": 0,
        "ibeaconMinor": 0,
        "rssi": -71,
        "ibeaconTxPower": -59,
        "battery": 0
    },
    {
        "timestamp": "2020-03-29T16:58:11.550Z",
        "type": "S1",
        "mac": "AC233FA293DC",
        "bleName": "",
        "rssi": -66,
        "battery": 100,
        "temperature": 17.93,
        "humidity": 51.44
    },
    {
        "timestamp": "2020-03-29T16:58:11.830Z",
        "type": "S1",
        "mac": "AC233FA29262",
        "bleName": "",
        "rssi": -68,
        "battery": 100,
        "temperature": 18.44,
        "humidity": 52.76
    },

Posts: 1

Participants: 1

Read full topic

@Peter_West wrote:

Hi,

I’ve been running Home Assistant for a few months now and i’ve found the AdGuard add-on to be really useful.

However, i’ve grown tired of constantly trying to remember the IP addresses of the many devices i’ve got so ideally i’d like to get a DNS server running internally.

I had originally thought about using DNSMasq, but of course the immediate problem i’ve hit is that it won’t run because it wants to also grab Port #53 (TCP and UDP) which is already being utilised by AdGuard.

So far as I can’t see there isn’t any way in AdGuard to add your own CNAME, A and PTR records so i’m a bit stuck as to how I could work around the issue. I also contemplated using alternate ports but all of the various locations I can see where you might specify a DNS server address don’t provide any means to specify an alternate port.

Has anyone got any good suggestions on how to work around this please?

I’m running HA using Hass.io which in turn is running as a VM in Proxmox, so another option might be to create a totally seperate VM and run another DNS Server in there, but if there’s a means to do the entire thing within HA then that’d be a big plus.

Thanks inadvance

Pete

Posts: 1

Participants: 1

Read full topic

@wivaku wrote:

My volvooncall component has been working fine. Until recently. I get error messages in the log (HA 0.107.7): Cannot connect to host vocapi.wirelesscar.net:443

Maybe related: in the Volvo On Call app (not Home Assistant) they mentioned they recently updated the security.

2020-03-29 18:56:12 WARNING (MainThread) [volvooncall.volvooncall] Failure when communcating with the server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:56:12 WARNING (MainThread) [volvooncall.volvooncall] Could not query server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:56:12 WARNING (MainThread) [homeassistant.components.volvooncall] Could not query server
2020-03-29 18:58:21 WARNING (MainThread) [volvooncall.volvooncall] Failure when communcating with the server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:58:21 WARNING (MainThread) [volvooncall.volvooncall] Could not query server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:58:21 WARNING (MainThread) [homeassistant.components.volvooncall] Could not query server
2020-03-29 18:59:27 WARNING (MainThread) [volvooncall.volvooncall] Failure when communcating with the server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:59:27 WARNING (MainThread) [volvooncall.volvooncall] Could not query server: Cannot connect to host vocapi.wirelesscar.net:443 ssl:None [Try again]
2020-03-29 18:59:27 WARNING (MainThread) [homeassistant.components.volvooncall] Could not query server

The standalone python app still works fine.

Posts: 1

Participants: 1

Read full topic

@wolfer4004 wrote:

Is it possible to have a Google Calendar event turn on/off an alarm my phone (Pixel 3)?
Basically, If calender.event message is “work”, turn on Work alarm…
I work a non standard work week and I really don’t want my alarm going off at 5am on the day I don’t have to work.
Do I need the Google Assistant SDK to make this work?

Thanks

Posts: 1

Participants: 1

Read full topic

@TomasCZ wrote:

Hi Friends!

I am trying to display readins from current sensors in HA.

Data are sent from from ESP8266 with Tasmota over MQTT to HA.

I can read the data in HA using MQTT listening:

{
    "SSerialReceived": {

        "I1": 0.07,
        "I2": 0.02,
        "I3": 0.01,
        "I4": 0.03
    }
}

Auto discovery did not wor so I created sensor entities manualy:

sensor:
  - platform: mqtt
    name: I1
    unique_id: "I1"
    state_topic: "tryskac/zatizeni/RESULT"
    unit_of_measurement: 'Amp' 
    value_template: "{{ value_json.I1 }}"
  - platform: mqtt
    name: I2
    unique_id: "I2"
    state_topic: "tryskac/zatizeni/RESULT"
    unit_of_measurement: 'Amp' 
    value_template: "{{ value_json.I2 }}"
  - platform: mqtt
    name: I3
    unique_id: "I3"
    state_topic: "tryskac/zatizeni/RESULT"
    unit_of_measurement: 'Amp' 
    value_template: "{{ value_json.I3 }}"
  - platform: mqtt
    name: I4
    unique_id: "I4"
    state_topic: "tryskac/zatizeni/RESULT"
    unit_of_measurement: 'Amp' 
    value_template: "{{ value_json.I4 }}"

Sensor entities have been created

entities1170×343 5.91 KB

I created lovelace sensor cards:

gauge1450×548 15.7 KB

But no any values are displayed.

I am playing with it couple of days and became desperate.

Any idea what could be wrong?

Posts: 1

Participants: 1

Read full topic

@ochstobi wrote:

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

Posts: 1

Participants: 1

Read full topic

@mspinolo wrote:

Hi guys,

i have an HA setup with some MiFlora sensor being gathered by miflora-mqtt-daemon running on a couple of RPI3 which I have around the house for other purposes primarily (transmission, Kodi, running deepstack server with Coral USB Stick).
Issue is these are not really well placed to catch all the plants.

Also around the house I have quite a lot of ESP32 with ESPHOME so I could use it: I gave up time ago as BLE implementation was a bit buggy (frequent disconnections, OTA not working).

Recently I tried to flash and ESP32 with 1.15-dev version of ESPHOME and latest Platformio (4.3.1) and issue seems gone.

Now I was wondering if it is possible to have the same MiFlora gathered by multiple devices (i.e. RPI running miflora-mqtt-daemon and ESP32 with ESPHOME) and publishing value on a single sensor.
I guess this could be achieved with some sensor templating merging the two: a simple average could work but I am not sure how to manage in case one of the two is “NaN” or “Unknown”.

Can someone provide a hint?

Posts: 1

Participants: 1

Read full topic

@gianlulen80 wrote:

Good Morning Guys,
I have a RP4b with the latest version of Hassio.
Im trying to work with bluetooth devices.
I have added in the configuration.yaml

device_tracker:

• platform: bluetooth_tracker
• platform: bluetooth_le_tracker

and i receive errors on the logs:

[homeassistant.components.device_tracker] Error setting up platform legacy topic:
[[homeassistant.components. bluetooth le tracker . device tracker ] No Bluetooth LE devices to track!]

I have also added this section (inserting the MAC address)

sensor:

• platform: mitemp_bt
  mac: ‘xx:xx:xx:xx:xx:xx’
  name: Kids Room Temp
  force_update: true
  median: 1
  monitored_conditions:
  • temperature
  • humidity
  • battery

And in this case additional errors like
[ homeassistant . components . sensor . mitemp_bt ] Polling error
or timeout messages.

What can i do?
I have to install some add-on ?

Thanks in advance
Regards
Gianluca

Posts: 1

Participants: 1

Read full topic

@abhilabhila wrote:

Hi Experts,

Off late, Shopping List Card is throwing up the error:

“Custom element doesn’t exist: hui-shopping-list-card”

I went thru the release notes for the latest updates and did not find anything breaking the Shopping List Card.

Please advice.

BR,

Abhilash

Posts: 1

Participants: 1

Read full topic

@Makis wrote:

Hi
I have a Paradox Alarm system and I integrated to HA with this setup

In the configuration.yaml I have the following
alarm_control_panel:

  - platform: mqtt
    state_topic: "paradoxdCTL/hassio/Arm"
    command_topic: "paradoxCTL/in"
    payload_disarm: '{"password":"0000","Command":"disarm","Subcommand":"0"}'
    payload_arm_night: '{"password":"0000","Command":"sleep","Subcommand":"0"}'
    payload_arm_home: '{"password":"0000","Command":"stay","Subcommand":"0"}'
    payload_arm_away: '{"password":"0000","Command":"arm","Subcommand":"0"}'

Iknow that I have to change the password to the one I have but I will do it later (I am noob so one step at a time)
I have also setup all the binary sensors and are working ok.

The problem right now is I don’t get the status of the of the alarm in Home Assistant alarm card
but I can get the messages in the MQTT topic. (see below message 71)
I am not sure what I have to type in the subcommand in configuration yaml or what the problem is.
Can someone help a little please?

Listen to a topic
 
Listening to
#
 
Message 98 received on paradoxCTL/in at 11:50 AM:
{
    "password": "0000",
    "Command": "disarm",
    "Subcommand": "0"
}
QoS: 0 - Retain: false
Message 97 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 0,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone OK",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 96 received on paradoxdCTL/hassio/zone3 at 11:48 AM:
OFF
QoS: 0 - Retain: false
Message 95 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 1,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone open ",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 94 received on paradoxdCTL/hassio/zone3 at 11:48 AM:
ON
QoS: 0 - Retain: false
Message 93 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 0,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone OK",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 92 received on paradoxdCTL/hassio/zone3 at 11:48 AM:
OFF
QoS: 0 - Retain: false
Message 91 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 0,
    "sub_event": 4,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone OK",
    "data": "R.XOL"
}
QoS: 0 - Retain: false
Message 90 received on paradoxdCTL/hassio/zone4 at 11:48 AM:
OFF
QoS: 0 - Retain: false
Message 89 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 1,
    "sub_event": 4,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone open ",
    "data": "R.XOL"
}
QoS: 0 - Retain: false
Message 88 received on paradoxdCTL/hassio/zone4 at 11:48 AM:
ON
QoS: 0 - Retain: false
Message 87 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 1,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone open ",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 86 received on paradoxdCTL/hassio/zone3 at 11:48 AM:
ON
QoS: 0 - Retain: false
Message 85 received on paradoxdCTL/out at 11:48 AM:
{
    "event": 0,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone OK",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 84 received on paradoxdCTL/hassio/zone3 at 11:48 AM:
OFF
QoS: 0 - Retain: false
Message 83 received on paradoxdCTL/out at 11:47 AM:
{
    "event": 1,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone open ",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 82 received on paradoxdCTL/hassio/zone3 at 11:47 AM:
ON
QoS: 0 - Retain: false
Message 81 received on paradoxdCTL/out at 11:47 AM:
{
    "event": 0,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone OK",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 80 received on paradoxdCTL/hassio/zone3 at 11:47 AM:
OFF
QoS: 0 - Retain: false
Message 79 received on paradoxdCTL/out at 11:47 AM:
{
    "event": 1,
    "sub_event": 3,
    "partition": 0,
    "sub_eventD": "",
    "eventD": "Zone open ",
    "data": "R.SALONI"
}
QoS: 0 - Retain: false
Message 78 received on paradoxdCTL/hassio/zone3 at 11:47 AM:
ON
QoS: 0 - Retain: false
Message 77 received on paradoxdCTL/hassio/zone8 at 11:40 AM:
OFF
QoS: 0 - Retain: true
Message 76 received on paradoxdCTL/hassio/zone10 at 11:40 AM:
OFF
QoS: 0 - Retain: true
Message 75 received on paradoxdCTL/hassio/zone6 at 11:40 AM:
ON
QoS: 0 - Retain: true
Message 74 received on paradoxdCTL/hassio/zone9 at 11:40 AM:
ON
QoS: 0 - Retain: true
Message 73 received on paradoxdCTL/hassio/zone11 at 11:40 AM:
ON
QoS: 0 - Retain: true
Message 72 received on paradoxdCTL/hassio/zone2 at 11:40 AM:
OFF
QoS: 0 - Retain: true
Message 71 received on paradoxdCTL/hassio/Arm0 at 11:40 AM:
disarmed

Posts: 6

Participants: 2

Read full topic

@brebar07 wrote:

Hello All,

I have recently updated to v0.107.7 and now my shopping_list is not working.

# DEFAULT CONFIGURATION FOR HASSIO
default_config:

# SHOPPING LIST
shopping_list:

My old shopping list has disappeared and when i try to add a new item nothing happens (e.g. not added to the list).

Any ideas?

Posts: 2

Participants: 1

Read full topic

@baz123 wrote:

I do not understand why the filter sensor is not updated when the source sensor is. I have defined a time_date sensor. I would expect the filter to update every time the source sensor is updated. Is that an incorrect expectation? This is a moving window but I have also tried it with lowpass with same behaviour. The system has been running for a while since last restart and I can see delays of over 30 mins sometimes.

Sensor and filter

- platform: time_date
  display_options:
    - 'time'
    - 'date'
    - 'date_time'
    - 'date_time_utc'
    - 'date_time_iso'
    - 'time_date'

## Study
- platform: mqtt
  name: "studyroomtemp"
  state_topic: "emon/sensor/mi_t_4c65a8d8e0d8/state"
  unit_of_measurement: '°C'
  device_class: temperature

- platform: filter
  name: studyroomtempfil
  entity_id: sensor.studyroomtemp
  filters:
    - filter: time_simple_moving_average
      window_size: 00:05
      precision: 1

Looking at the states

{{ states('sensor.studyroomtemp' )}}
{{ states.sensor.studyroomtemp.last_updated}}
{{ states('sensor.studyroomtempfil' )}}
{{ states.sensor.studyroomtempfil.last_updated}}

20.21
2020-03-30 09:50:12.171099+00:00
20.5
2020-03-30 09:48:40.278234+00:00  

Posts: 10

Participants: 4

Read full topic

@anjoze wrote:

I’m trying to setup Thingspeak integration following the instructions here: https://www.home-assistant.io/integrations/thingspeak

It’s not working and I have this message:

Error while accessing the ThingSpeak channel. Please check that the channel exists and your API key is correct

I’m using Version 213 on Docker on Ubuntu 18.04
I don’t know if it is related or not or if it is normal but since the last update the hassio_dns container doesn’t start.
I didn’t try it before update to this version.

Posts: 1

Participants: 1

Read full topic

@stavrosso wrote:

Hello everyone,

I have been playing with lovelace and picture elements card to make my floorplan. I managed to put images for off and states of the entities and everything was working fine.

All of a sudden a grey stripe with a corrupted image icon appeared in the middle of my floorplan (see image)

I checked all off my pictures, icons, and entities and they are correct.

Any ideas,please?

problematic floorplan image1361×626 301 KB

Thank you

Posts: 6

Participants: 3

Read full topic

@Codec303 wrote:

Hi, I removed the ‘MQTT’ integration as I was trying to remove a device that was still appearing in my MQTT despite the device being removed using MQTT explorer.

Is there a way I can make HAC so the ‘auto-discover’ process again?

Posts: 3

Participants: 2

Read full topic