Home Assistant

Black_Knight wrote: »

I likey. I do miss a few things, but its early days. I can add those things in yet.

Things I miss:
- tapping on an entity gave me all the info about it (history graphs, colour wheels for light bulbs etc). Now i've nice quick on/off 1 touch entities in lovelace, but the other night I wanted to change the colour of a bulb and I had to use the hue app. It's a learning curve though, and lovelace makes it so simple to update the UI.
.

If you use the button card this will give you those functions, it is what I use for Hue and Hive bulbs.button_card.JPG

Still playing around with Lovelace so a bit to go yet but some nice cards to play around with.

THE ALM wrote: »

If you use the button card this will give you those functions, it is what I use for Hue and Hive bulbs.button_card.JPG

Still playing around with Lovelace so a bit to go yet but some nice cards to play around with.

I'm really new to HA & lovelace. I'm always on the look out for examples though so any chance you'd share your lovelace config? I'm very much in the copy, paste & tweak phase at the moment!

I got around to installing Ubuntu on the spare laptop over the weekend only to find that I can't get Docker to install because it's got a 32 bit processor. Looking at other options I see the below posted in BA, which might be of interest to some.

tryfix wrote: »

4-in-1 Raspberry Pi 3 Model B+ + Acrylic Case + Cooling Fan + Heatsink Kit

Special Price €37.77

https://www.zapals.com/4-in-1-raspberry-pi-3-model-b-acrylic-case-cooling-fan-heatsink-kit.html

A nice little piece of kit from China with the latest 3 b+ model and there's a 3.5" touch screen add on below for €9.43.



3.5-inch LCD Touch Screen with Stylus Pen for Raspberry Pi 3 Model B

https://www.zapals.com/raspberry-pi-3-model-b-3-5-inch-lcd-touch-screen-with-stylus-pen-hd-1920x1080.html

Hi All,

I recently switched my HA setup from a Raspberry Pi to a NUC with docker. So far I'm loving the experience but I spent all of yesterday trying to add a new zwave device and got nowhere. Now it could be the device (Fibaro Sensor - of which I have two already) but I don't think it is.

I have made sure to pass the Z Wave USB stick to docker and point to the correct place in the config file and it successfully communicates with and controls all my existing devices so it must be substantially working but it just will not talk to the new device. I only have one new one here and I'm not going to delete one of the working ones to try to re-add it!

If anyone has had a similar experience let me know.

I want to troubleshoot the issue a few different ways - the way I always did this with the RPi was to have a "working" SD card with the current set up on it and a testing card to play around with. I assume I can do something similar by having two different containers in docker - i.e. a stable container and a working container. My entire docker knowledge is gleaned from the net in the past few weeks so it is limited! Could anyone lay out the steps they might take in a similar circumstance?

Thanks lads, love this thread. I realise reddit is there and the HA forums but I like the vibe here!!

For the Teckin Sp23 Power Monitoring sockets that regularly on offer on Amazon UK, use this Wiki entry to use them with Tasmota and HA

https://github.com/arendst/Sonoff-Tasmota/wiki/Teckin-SP23

I flashed two and no issues

Jumping on this train now - just picked up a Rasperry Pi 3 B+ and installed Home Assistant last night.

Anyone setup broadlink with this?

Finally got a few hours to sit down and configure my NUC to run Docker & Hassio yesterday.

I got my Xiaomi Miija Devices all set up and working ( Temp & Humidity Sensors, Door & Window Sensors, Motion Sensors, Smoke Detector and a Switch ).

All working and reading back nicely, customized and grouped together.

Problem Number 1:
Still attempting to locate the token for the Yeelights proved a bit beyond the time I had allowed so after a number of different of attempts form what I found on Google I left it for the time being.

Problem Number 2:
Having purchased the Teckin Smart Plugs from the Flash Amazon sales I flashed them with Tasmota. I installed the MQTT Broker plugin on HASSIO and setup the plugs to match. However no success with Auto-Discovery. After much googling I tried another option, I set up a Cloud MQTT Broker. I configured the plugs and could see them on the Broker – however again they were not showing up on my Home Assistant.

This is what is in my configuration.yaml:

[PHP]mqtt:
broker: xxxxxxx
port: xxxxxxxxx
username: xxxxxxx
password: xxxxxx [/PHP]

From what I’ve read the plugs should automatically show in the Integrations MQTT in Configuation?

I’ve also tried placing this in my configuration.yaml but to no success:

[PHP]switch:
platform: mqtt
name: “Sonoff1”
command_topic: “cmnd/sonoff1/power”
state_topic: “stat/sonoff1/POWER”
qos: 1
payload_on: “ON”
payload_off: “OFF”
retain: true[/PHP]

If I do get this connected, how do I customize similar to my Xiaomi Sensors? for example, in my customize.yaml file the Xiaomi Sensors are:

sensor.temperature_158d00016fdxxx:
  friendly_name: Kitchen Temperature
sensor.humidity_158d00016fdxxx:
  friendly_name: Kitchen Humidity
  icon: mdi:water-percent
binary_sensor.door_window_sensor_158d000xxxxxx:
    friendly_name: Kitchen Door
    device_class: opening

I suspect I've a few more evenings scratching my head and getting dirty looks from herself!

Newtown90 wrote: »

If only I read "thecivvie" post above before I posted......

I run ecilpse mosquitto on my docker. that way I limit access to it via my vpn tunnel, also on the same docker for outside nework devices.

mqtt:
  broker: !secret mqtt_broker
  port: 1883
  username: !secret mqtt_user
  password: !secret mqtt_pass

Sonoff as a device

 - platform: mqtt
   name: "Cabinet"
   state_topic: "stat/sonoff15/POWER"
   command_topic: "cmnd/sonoff15/POWER"
   availability_topic: "tele/sonoff15/LWT"
   payload_on: "ON"
   payload_off: "OFF"
   payload_available: "Online"
   payload_not_available: "Offline"
   optimistic: false
   qos: 1
   retain: true

Sensors

  - platform: mqtt
    name: "Cabinet Energy Today"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Today"] }}'
    unit_of_measurement: "kWh"
  - platform: mqtt
    name: "Cabinet Energy Yesterday"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Yesterday"] }}'
    unit_of_measurement: "kWh"
  - platform: mqtt
    name: "Cabinet Energy Total"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Total"] }}'
    unit_of_measurement: "kWh"
  - platform: mqtt
    name: "Cabinet Power"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Power"] }}'
    unit_of_measurement: "W"
  - platform: mqtt
    name: "Cabinet Voltage"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Voltage"] }}'
    unit_of_measurement: "V"
  - platform: mqtt
    name: "Cabinet Power Factor"
    state_topic: "tele/sonoff15/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Factor"] }}'

I graph the data using influxdb and Grafana as well



Dog Bowl is my dog's water fountain. The Teckin smart socket turns it on in the morning and off at night

I have spent many sleepless nights getting it to how I want.

Worryingly I added my Netatmo weather station to the system and found my house has a problem



I have, so far, 17 sonoff enabled devices. I am ordering 4 more of the Teckin Smart Plugs today as they on a lightning deal

Newtown90 wrote: »

They all go in your configuration.yaml correct?

no, mine is broken up.

Sensors in a sensor.yaml, switches, lights and so on. I have also merge_dirs as well for heavier yaml files that get broken up, like my automations.

But yes it is possible to put them all into configuration.yaml

my include setup

group: !include_dir_merge_named group
automation: !include_dir_merge_list automations/
script: !include scripts.yaml
sensor: !include sensors.yaml
light: !include_dir_merge_list light/
switch: !include switch.yaml
camera: !include_dir_merge_list camera
scene: !include_dir_merge_list scene
binary_sensor: !include  binary_sensor.yaml

Dr4gul4 wrote: »

Just adding this Github repo i've been recently looking at for an alarm system. works well, obv it's for a specific model / make of alarm, but i've yet to see it catered for any where else. Docker image included there also ..

https://github.com/lucacalcaterra/risco-mqtt-bridge

Looks good. I've recently gotten the konnected interface panel to get states from my HKC alarm. But unfortunately haven't had a chance to install yet.

mcgovern wrote: »

Can I use the Raspberry Pi I have running Hass.io to flash them?

Yes and No . You can try tuya OTA or Via Serial from a laptop / computer

https://github.com/arendst/Sonoff-Tasmota/wiki/Teckin-SP23
https://www.youtube.com/watch?v=7vjpcEedEBI

mcgovern wrote: »

And after they are flashed can I still use them in Alexa or only in Home Assistant?

If you have the Home assistant module added to alexa you can, assuming you then have the devices in Home asssitant.

mcgovern wrote: »

And finally I need something like this to calibrate them afterwards?

Possibly, but you could plug in a new 60 watt bulb and a light maybe . might provide the same info ? kinda, maybe not really tho ..