Home Assistant : Q&A, Tips & Tricks, Your Configs

InternetLuddite said:
Questions:-
1. What flavour of HASS do I need to install inside docker to get the same experience the Hass.io image that runs on Pi? Is it Hass supervisor?
2. Is my planned Ubuntu setup with Docker valid?. The PC has one NIC, but based on what I read, I can make it tagged so that traffic for both VLAN 1+2 can be handled
3. Is 4GB of Ram on the PC enough to keep this all running well. The PC has 250GB HDD but will swap to SSD. I may install Plex inside docker itself and some DB like grafana or influx ??? (sorry still a newb on this topic).

Thanks. Hoping to get this all done during this lockdown period.

Cheers in advance (sorry I have no alcohol left except for what may be in the sanitisers) :ROFL:
Click to expand...
1. Go with the supervisor install. So you install a clean Ubuntu 18.04 on the NUC, then before you do anything else, follow the supervisor install guide. That is what I did. You can still do addons ect.
Use this link for the instructions: https://www.home-assistant.io/hassi...-assistant-supervised-on-a-generic-linux-host

So instead of a "Hassio" menu item, you get a "Supervisor" menu item. It still allows you to install addons etc. and to do updates etc in the website interface or app on your phone.

2. Ubuntu can do vlans, but it is up to you if you really need and want to go vlan route.

3. HA on my Ubuntu with Grafana and influx uses about 1GB ram. My plex server is however separate and eats up memory. I am happy they not together, my HA setup need to be reliable because home automation cant get stuck because of memory issues.
 
So finally managed to get custom cards working in my Lovelace ui.

I failed doing this manually, so ended up installing HACS (silly of me not looking for something like this earlier) and then used that to install it, and 1st try it works.

Now I can use a card like this:
Code: 
type: 'custom:auto-entities'
card:
  type: entities
  title: Open Doors/Windows
  show_header_toggle: false
show_empty: false
filter:
  include:
    - name: '*Door*'
    - name: '*Window*'
  exclude:
    - name: '*Pet*'
    - state: 'off'
So what is great about this is, now the card only shows up if any windows or doors are open and only the open items show up. Makes it super easy at the end of the night before arming the alarm to check what is open.
 
Tinuva said:
1. Go with the supervisor install. So you install a clean Ubuntu 18.04 on the NUC, then before you do anything else, follow the supervisor install guide. That is what I did. You can still do addons ect.
Use this link for the instructions: https://www.home-assistant.io/hassi...-assistant-supervised-on-a-generic-linux-host

So instead of a "Hassio" menu item, you get a "Supervisor" menu item. It still allows you to install addons etc. and to do updates etc in the website interface or app on your phone.

2. Ubuntu can do vlans, but it is up to you if you really need and want to go vlan route.

3. HA on my Ubuntu with Grafana and influx uses about 1GB ram. My plex server is however separate and eats up memory. I am happy they not together, my HA setup need to be reliable because home automation cant get stuck because of memory issues.
Click to expand...
Many thanks. :)
 
Tinuva said:
So finally managed to get custom cards working in my Lovelace ui.

I failed doing this manually, so ended up installing HACS (silly of me not looking for something like this earlier) and then used that to install it, and 1st try it works.

Now I can use a card like this:
Code: 
type: 'custom:auto-entities'
card:
  type: entities
  title: Open Doors/Windows
  show_header_toggle: false
show_empty: false
filter:
  include:
    - name: '*Door*'
    - name: '*Window*'
  exclude:
    - name: '*Pet*'
    - state: 'off'
So what is great about this is, now the card only shows up if any windows or doors are open and only the open items show up. Makes it super easy at the end of the night before arming the alarm to check what is open.
Click to expand...
Great to see that you are winning.
 
Tinuva said:
ok slowly but surely working on this whenever I get time. Only been in the house for 5 weeks now since moving in and there a bunch of non-tech non-homeassistant stuff that also needed to get done...and still needing to get done.

So I haven't checked out "packages" yet mentioned by patrick123, but I am definitely struggling to get custom components working for who know what reason.

/snip
Click to expand...
Packages are great when you have a unit that is multiple types of sensors and/or switches.
Instead of having entries for it all over the place, the package contains them all like a mini config within your config.
 
would anyone be interested in a fuel price sensor.
Returns inland 93 past present and future price.
It only uses webscraping as i cant find a free api. If anyone knows of a free api i would appreciate it.Screenshot_20200518-193243.png
I can upload to github if anyone is interested.
 
when having 2 devices under cover: what should the syntax be

cover:
platform: mqtt
name: "Garage"
state_topic: "cmnd/garagestate/POWER2"
command_topic: "cmnd/GarageSV/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
platform: mqtt
name: "Gate"
state_topic: "cmnd/gatestate/POWER2"
command_topic: "cmnd/GateSV/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
 
alqassam said:
when having 2 devices under cover: what should the syntax be

cover:
platform: mqtt
name: "Garage"
state_topic: "cmnd/garagestate/POWER2"
command_topic: "cmnd/GarageSV/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
platform: mqtt
name: "Gate"
state_topic: "cmnd/gatestate/POWER2"
command_topic: "cmnd/GateSV/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
Click to expand...

i think you want it like

cover:
- platform: mqtt
name: "Alarm"
state_topic: "cmnd/alarmstate/POWER2"
command_topic: "cmnd/alarm/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: shutter

- platform: mqtt
name: "Gate"
state_topic: "cmnd/gatestate/POWER2"
command_topic: "cmnd/gate/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: shade

note i dont have the cover heading since mine is in a cover yaml

also dont mess up the indenting like the forum just did for mine
 
Steamy Tom said:
i think you want it like

cover:
- platform: mqtt
name: "Alarm"
state_topic: "cmnd/alarmstate/POWER2"
command_topic: "cmnd/alarm/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: shutter

- platform: mqtt
name: "Gate"
state_topic: "cmnd/gatestate/POWER2"
command_topic: "cmnd/gate/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: shade

note i dont have the cover heading since mine is in a cover yaml

also dont mess up the indenting like the forum just did for mine
Click to expand...
Sorted thanks I'd didn't have the space after the hyphen

Look at this layout. Pretty cool and easy to use and control
https://imgur.com/J7RM30C
 
Can someone please share their automation YAML for clickable notification on garage doors.

Garage is a bit more complex as I only want the alert between 10pm and 7 am. Gate can be continuous alerts

I tried the sample from the interwebs but was throwing errors
 
I've been using Sonoff switches and bridge/PIRs for a while now, all on the eWeLink app. I also had a couple of things set up via IFTTT.

Been avoiding Home Assistant for a while, knowing it would be a vertical learning experience, but I was notified that eWeLink is going to be billing for IFTTT integration soon, so I decided to have a go at HA.

I installed HassOS in VirtualBox on a Windows 10 laptop, following this video:


and then got my Sonoff stuff on board using this video from DrZzs:


This resulted in a ''Supervisor'' HA install, with most stuff working out of the gate.

I now need some assistance with getting the PIRs that I use working on the system - at the moment, the bridge is operating but only registers one PIR at a time (whichever one was last triggered). I use 3 PIRs at the moment, so I imagine I need to get individual identifiers from the PIRs and go from there. Do I need to install MQTT to handle this?
 
riscbroker said:
I've been using Sonoff switches and bridge/PIRs for a while now, all on the eWeLink app. I also had a couple of things set up via IFTTT.

Been avoiding Home Assistant for a while, knowing it would be a vertical learning experience, but I was notified that eWeLink is going to be billing for IFTTT integration soon, so I decided to have a go at HA.

I installed HassOS in VirtualBox on a Windows 10 laptop, following this video:


and then got my Sonoff stuff on board using this video from DrZzs:


This resulted in a ''Supervisor'' HA install, with most stuff working out of the gate.

I now need some assistance with getting the PIRs that I use working on the system - at the moment, the bridge is operating but only registers one PIR at a time (whichever one was last triggered). I use 3 PIRs at the moment, so I imagine I need to get individual identifiers from the PIRs and go from there. Do I need to install MQTT to handle this?
Click to expand...

Congrats on going HA!

I don't have any direct experience with the Sonoff / eWeLink add-on, but note that MQTT will require you to flash the bridge with Tasmota. Which is what I did and it works great.

Why not take it one step deeper and start flashing? Just do a Sonoff Basic first -- it is easy enough! If you position the pins just right you don't have to worry about soldering.

Here's the Bridge running Tasmota. While it shows 16 "buttons" there I don't even bother with it -- I can receive unlimited number of codes and send out any number (I only use it for receiving).


Screenshot 2020-06-02 at 22.19.09.png
I have a Sonoff PIR, another brand door sensor that transmit a code with both opening/closing, another brand single button, a Sonoff remote with 8 buttons and then a plain Ellies wireless doorbell where I've switched off the original receiver (that goes DING-DONG). Instead I catch the button press with the RF bridge and process it in Home Assistant (it takes a pic using my Hikvision cameras and my Google Home announces "doorbell!").
 
I'm very sure there is a lot of flashing in my future - I just don't have the kit at the moment so I'm experimenting with what I have on hand.

Since Home Assistant already recognizes the bridge and has listed it among entities, do I absolutely have to flash it with Tasmota for it to work with MQTT? ie are they interdependent?

Maybe @Dairyfarmer has some info on this ?

Update: all PIRs working now, no flashing the bridge, no MQTT required...
 
Last edited:
Anyone up for helping me get remote access to my HA instance?

I've been trying for a couple of days now. HA (the ''Supervisor'' install) is on a virtual machine on Windows 10, I have set up DuckDNS and fiddled with port forwarding on my Telkom DSL-G2562DG router. Whatever settings I use, I end up at the login page for my router.

I'm sure there is a fundamental setting/entry that I have messed up or omitted but my networking skills are really basic and I cannot figure it out.
 
riscbroker said:
Anyone up for helping me get remote access to my HA instance?

I've been trying for a couple of days now. HA (the ''Supervisor'' install) is on a virtual machine on Windows 10, I have set up DuckDNS and fiddled with port forwarding on my Telkom DSL-G2562DG router. Whatever settings I use, I end up at the login page for my router.

I'm sure there is a fundamental setting/entry that I have messed up or omitted but my networking skills are really basic and I cannot figure it out.
Click to expand...
Use the :8123 at the end of the duckdns url


Xxxxxx.duckdns.org:8123
 
riscbroker said:
Anyone up for helping me get remote access to my HA instance?

I've been trying for a couple of days now. HA (the ''Supervisor'' install) is on a virtual machine on Windows 10, I have set up DuckDNS and fiddled with port forwarding on my Telkom DSL-G2562DG router. Whatever settings I use, I end up at the login page for my router.

I'm sure there is a fundamental setting/entry that I have messed up or omitted but my networking skills are really basic and I cannot figure it out.
Click to expand...
Ugh, it looks like you're exposing/port forwarding to your router's IP.

You need to set it to the IP where HA is running.

If you can post some screenshots it will help.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X