Home Assistant

Is there a supervisor docker version available? I thought it wasn't available?

What sort of weather system have you?

It is possible to have supervisor with docker, although it is only officially supported with Debian as host OS, I run it on Pi OS without any issue, except warnings in the logs about 'unsupported OS' and lately moaning about other non-HA apps running in Docker. These warnings don't affect the operation though. But since I have started to convert the other Docker apps that I need into HA add-ons I may go back to running HAOS.

Be careful out there

I had read about these, but that's as far as I got. I've been messing around with 0.96" OLED displays on ESP32 devices running ESPHOME. The e-paper tags limit the interactivity and the performance of a system using them, but I can see good use cases for them alright - for example reporting on the amount of hot water in the cylinder - no rapid updates needed there.

Have you got InfluxDB and Grafanna installed on HA, they should be more useful and designed for timebased data and graphing.

For anyone who likes to have news ticker like information these work great with home assistant. You can set up automations to display any sensor information and if you set up the home assistant app on an android phone or tablet can you display the latest notification it received. I set up an old android tablet for example to run a livescores app and subscribed to all the big leagues and everytime a goal is scored it will be displayed on the led display (android has a limit on the amount of notifications that it can have in the notification list though so you need to run macdroid app to clear notifcations every so often if you use it for the likes of live scores where there are a lot of updates).

Edit: Example of live football scores.

Example of using sensor information, in this video it's showing forecasts and what was generated.

We have various Google Nest speakers around the house. Until recently when I asked one of them to turn a light on or off it would just chime which was perfect. They've recently started replying with full sentences like 'Turning off Landing Lights' which is beginning to get on my nerves especially at night. I didn't change anything in our home to cause this, has anyone else had the same problem recently?

I think this depends on your room setup.

If I say to my kitchen speaker to turn on the living room lights it response "turning on ..."

If I say the same to my living room speaker it will just turn them on and chime

What website, the Home Assistant dashboard or some cloud service for your gates?

Sounds like an issue with a cloudflare service. If it's for your HA then you should be still able to connect to it by the local address if on same network.

Finding the learning curve with HA very steep. Doesn't help that the constant OS upgrading seems to render most tutorials redundant shortly after they are released.

Incremental improvements can make it tricky, but I find that it's one of the best documented applications out there due to its popularity. Rock stable too.

Proxmox is tricky but can be done in a few mins.

Would you have them stored in a password store of a browser?

Yep, multiple power cuts over the past week has caused some fun here too, perhaps time to consider some backup power.

Maybe your HA has taken up an alternative IP address? There is a mobile app called fing that is great for seeing what IP addresses your devices have. There is a PC version too (free version is good enough) or alternatively Angry IP scanner.

I have a second-hand ups box that keeps HA going for about an hour, though I'm Moving to a new bigger server this week so that'll drop to half an hour or less. Don't mind that much, I mainly have it to avoid several brown outs a year we get causing havoc on the PC. Have another smaller back up that needs a new battery, that I'll be plugging the router into, that's in a different location to the server.

I never have any issues with the monthly updates that aren't of my own doing. If I stick to my updating process I always can roll back if I need to.

1. Run any updates on Proxmox.

2. Run and updates for installed integrations, including on HACS.

3. Check release notes for any breaking changes. These are flagged months in advance nowadays.

4. Create a HA backup and download it to a different PC.

5. Create a snapshot on Proxmox. This is the most important step, will roll back to this if the HA update screws up

6. Run the new HA update.

7. Run the new HA OS update if available.

8. Check for any more integration updates.

9. If all looks to be ok, create another Proxmox snapshot and that's it.

A good few steps but doesn't take long to run through it all, and can be pottering away at something else while it's running.

What date do you get, with that code?

The code for the day of the week looks iffy - shouldn't it be something like this if "day_semana[id(homeassistant_time).now().day_of_week]" returns 0 for Monday, as suggested by the comments?

Like this maybe: char const *day_semana[] = { "Mon.", "Tue.", "Wed.", "Thur.", "Fri.", "Sat.", "Sun." };

Edit: don't know enough about the rest of it to comment though.

Yes, he has gone with just about the most complex way to extract data that you could choose. Elegant if you know what you are doing but excluding if you aren't a programmer.

I get a static "Sat 8/1" for the output on the screen, which I think is just a default fallback value. Going to see if my efforts produce a day change tomorrow - but am lost as to where he is getting the date from. To be honest I dont even know what page0.date is refering to.

No there is no specific display section.

This is the whole yaml and to be frank I cannot see for the life of me why its not working - it looks perfectly setup to extract the day and date, but it never does.

# Set some variables for convenience

substitutions:

node_name: nspanel

device_name: NSPanel

target_temp_home: 20.0 °C

target_temp_eco: 16.0 °C

esphome:

name: $node_name

comment: $device_name

esp32:

board: esp32dev

wifi:

ssid: !secret wifi_ssid

password: !secret wifi_password

# Optional manual IP

# Enable logging

logger:

level: DEBUG

logs:

sensor: ERROR

# Enable wireless updates

ota:

password: !secret wifi_password

# Enable Home Assistant API

api:

services:

# Service to play a song

- service: play_rtttl

variables:

song_str: string

then:

- rtttl.play:

rtttl: !lambda 'return song_str;'

- service: upload_tft

then:

- lambda: 'id(disp1)->upload_tft();'

- service: send_command

variables:

cmd: string

then:

- lambda: 'id(disp1).send_command_printf("%s", cmd.c_str());'

time:

- platform: homeassistant

id: homeassistant_time

timezone: Europe/London

on_time:

- seconds: 0

minutes: '*'

then:

- script.execute: tft_date_update

- script.execute: tft_time_update

- script.execute: tft_weather_update

# A reboot button is always useful

button:

- platform: restart

name: Restart $device_name

# Define some inputs

binary_sensor:

# Switches between HEAT or OFF mode

- platform: gpio

name: $device_name Left Button

pin:

number: 14

inverted: true

on_press:

then:

- climate.control:

id: caldera

mode: !lambda |-

if (id(caldera).mode==CLIMATE_MODE_OFF)

{

return CLIMATE_MODE_HEAT;

}

else

{

return CLIMATE_MODE_OFF;

}

- script.execute: tft_wake_up

# Switches between a predefined "night" or "sleep" target temperature and a "normal" target temperature

# this will be also automated in homeassistant, but it is nice to have a button for it

- platform: gpio

name: $device_name Right Button

pin:

number: 27

inverted: true

on_press:

then:

- climate.control:

id: caldera

preset: !lambda |-

if (id(caldera).preset==CLIMATE_PRESET_ECO)

{

return CLIMATE_PRESET_HOME;

}

else

{

return CLIMATE_PRESET_ECO;

}

- script.execute: tft_wake_up

- platform: nextion

name: $device_name Up Button

page_id: 0

component_id: 6

on_press:

then:

- climate.control:

id: caldera

target_temperature: !lambda "return id(caldera).target_temperature + 0.1;"

- platform: nextion

name: $device_name Down Button

page_id: 0

component_id: 7

on_press:

then:

- climate.control:

id: caldera

target_temperature: !lambda "return id(caldera).target_temperature - 0.1;"

sensor:

- platform: wifi_signal

name: $device_name WiFi Signal

id: wifi_rssi

update_interval: 60s

on_value:

# Push it to the display

# RSSI is negative

# -0 - -50 => excellent - wlan4 - pic id 21

# -50 - -60 => good - wlan3 - pic id 20

# -60 - -70 => fair - wlan2 - pic id 19

# -70 - -85 => weak - wlan1 - pic id 18

# -85 - -90 => offline - wlan0 - pic id 17

then:

- lambda: |-

if (id(wifi_rssi).state >= -50) { id(disp1).set_component_pic("page0.picSignal", 21); }

if ((id(wifi_rssi).state < -50) && (id(wifi_rssi).state >= -60)) { id(disp1).set_component_pic("page0.picSignal", 20); }

if ((id(wifi_rssi).state < -60) && (id(wifi_rssi).state >= -70)) { id(disp1).set_component_pic("page0.picSignal", 19); }

if ((id(wifi_rssi).state < -70) && (id(wifi_rssi).state >= -85)) { id(disp1).set_component_pic("page0.picSignal", 18); }

if (id(wifi_rssi).state < -85) { id(disp1).set_component_pic("page0.picSignal", 17); }

# from https://github.com/darktim/ESPHome-NSPanel/blob/main/WiFi-Indicator.md

- platform: adc

id: ntc_source

pin: 38

update_interval: 10s

attenuation: 11db

- platform: resistance

id: resistance_sensor

sensor: ntc_source

configuration: DOWNSTREAM

resistor: 11.2kOhm

- platform: ntc

id: temperature

sensor: resistance_sensor

accuracy_decimals: 2

filters:

- median:

window_size: 15

send_every: 10

send_first_at: 3

calibration:

b_constant: 3950

reference_temperature: 25°C

reference_resistance: 10kOhm

name: $device_name Temperature

on_value:

then:

- lambda: 'id(disp1).set_component_text_printf("page0.intTemp", "%.1f""\xb0", x);'

# Grab current temperature from Home Assistant

- platform: homeassistant

id: ext_temperature

entity_id: weather.forecast_home

attribute: temperature

on_value:

then:

- lambda: 'id(disp1).set_component_text_printf("page0.extTemp", "%.1f""\xb0", x);'

- platform: homeassistant

id: wind_speed

entity_id: weather.forecast_home

attribute: wind_speed

unit_of_measurement: "km/h"

on_value:

then:

- lambda: 'id(disp1).set_component_text_printf("page0.wind", "%i km/h""\xb0", (int)id(wind_speed).state);'

- platform: nextion

id: current_page

name: "current_page"

internal: true

accuracy_decimals: 0

variable_name: dp

update_interval: 1s

- platform: uptime

name: Uptime Sensor

text_sensor:

- platform: homeassistant

id: current_weather

entity_id: weather.forecast_home

on_value:

then:

- script.execute: tft_weather_update

script:

- id: tft_weather_update

then:

- lambda: |-

char const *wstr[] = {"clear-night", "cloudy", "fog",\

"lightning", "lightning-rainy", "partlycloudy",\

"pouring", "rainy", "snowy", "sunny"};

int i = 0;

if (id(current_weather).state=="unknown") return;

while ((id(current_weather).state!=wstr[i])&&(i<9)) {i++;}

if ((i>0)&&(i<10))

{

id(disp1).send_command_printf("page0.weather.pic=%i", i+3);

id(disp1).set_component_text_printf("page0.wind", "%i km/h", (int)id(wind_speed).state);

}

- id: tft_date_update

then:

- lambda: |-

int day = id(homeassistant_time).now().day_of_month;

int month = id(homeassistant_time).now().month;

if ((day>0)&&(day<7)&&(month>0)&&(month<13))

{

char const *day_week[] = { "Saturday", "Sunday", "Monday", "Tuesday", "Wednsday", "Thursday", "Friday" };

const char *str = day_week[id(homeassistant_time).now().day_of_week]; // range [1-7], Saturday=1

id(disp1).set_component_text_printf("page0.date", "%s %02i/%02i", str, day, month);

}

- id: tft_time_update

then:

- lambda: 'id(disp1).set_component_text_printf("page0.time", "%s", id(homeassistant_time).now().strftime("%H:%M").c_str());'

- id: tft_wake_up

then:

- lambda: |-

id(disp1).send_command_printf("page0.sleep_cnt.val=page0.sleep_timeout.val");

id(disp1).send_command_printf("page0.sleep_timer.en=1");

if (id(current_page).state!=0)

id(disp1).send_command_printf("page 0");

id(disp1).send_command_printf("dim=page0.brightness.val");

# Define some outputs

switch:

# Relay 2 is the thermostat switch, Relay 1 was physically removed!

- platform: gpio

name: $device_name Relay

id: relay_2

internal: true # it should not be activated directly by home assitant

pin:

number: 19

# Pin 4 always needs to be on to power up the display

- platform: gpio

id: screen_power

entity_category: config

pin:

number: 4

inverted: true

restore_mode: ALWAYS_ON

- platform: template

name: $device_name auto sleep

id: auto_sleep

entity_category: config

restore_mode: ALWAYS_ON

optimistic: true

on_turn_on:

- lambda: 'id(disp1).send_command_printf("page0.disable_sleep.val=0");'

on_turn_off:

- lambda: 'id(disp1).send_command_printf("page0.disable_sleep.val=1");'

number:

- platform: template

name: $device_name Brightness

id: brightness

entity_category: config

unit_of_measurement: '%'

icon: "mdi:brightness-percent"

min_value: 0

max_value: 100

step: 1

initial_value: 30

set_action:

then:

- lambda: |-

id(disp1).send_command_printf("page0.sleep_timer.en=1");

if (id(current_page).state!=0)

id(disp1).send_command_printf("page 0");

id(disp1).set_backlight_brightness(x/100);

# Sets the sleep timer value

# requires code running in the nextion tft to make a 1 second period timer

# with a counter and a variable to store the timeout

- platform: template

name: $device_name Sleep timeout

id: sleep_timeout

entity_category: config

unit_of_measurement: 's'

icon: "mdi:timer"

min_value: 3

max_value: 300

step: 1

initial_value: 60

set_action:

then:

- lambda: |-

id(disp1).send_command_printf("page0.sleep_timeout.val=%i", (int)x); // set the timeout

id(disp1).send_command_printf("page0.sleep_cnt.val=%i", (int)x); // reset the counter to its maximum

# Configure the internal bleeper

output:

- platform: ledc

id: buzzer_out

pin:

number: 21

# Enable ringtone music support

rtttl:

id: buzzer

output: buzzer_out

# Configure UART for communicating with the screen

uart:

id: tf_uart

tx_pin: 16

rx_pin: 17

baud_rate: 115200

# Configure the screen

display:

- platform: nextion

id: disp1

exit_reparse_on_start: true

uart_id: tf_uart

tft_url: !secret panel_file

on_setup:

then:

- number.set:

id: brightness

value: 30

- lambda: |-

id(disp1).set_component_text_printf(

"page0.intTemp", "%.1f""\xb0", id(temperature).state);

id(disp1).set_component_text_printf(

"page0.extTemp", "%.1f""\xb0", id(ext_temperature).state);

id(disp1).set_component_text_printf("page0.btn0", "ENCENDER");

id(disp1).set_component_text_printf("page0.btn1", "MODO ECO");

- script.execute: tft_date_update

- script.execute: tft_time_update

- script.execute: tft_weather_update

- rtttl.play: "twobits:d=4,o=5,b=220:c6,8g,8g,a,g,p,b,c6"

# Single-point thermostat (for heating only)

climate:

- platform: thermostat

id: caldera

name: $device_name Thermostat

sensor: temperature

preset:

# Sleep temperature

- name: eco

default_target_temperature_low: $target_temp_eco

# Normal heating temperature

- name: home

default_target_temperature_low: $target_temp_home

heat_deadband: 0.2

heat_overrun: 0.2

min_heating_off_time: 300s

min_heating_run_time: 300s

min_idle_time: 30s

heat_action:

- switch.turn_on: relay_2

idle_action:

- switch.turn_off: relay_2

on_state:

- lambda: |-

id(disp1).set_component_text_printf("page0.setTemp", "%.1f""\xb0", id(caldera).target_temperature);

if (id(caldera).mode==CLIMATE_MODE_OFF)

id(disp1).set_component_text_printf("page0.btn0", "HEATER OFF");

else

id(disp1).set_component_text_printf("page0.btn0", "HEATER ON");

if (id(caldera).preset==CLIMATE_PRESET_ECO)

id(disp1).set_component_text_printf("page0.btn1", "ECO MODE");

else

id(disp1).set_component_text_printf("page0.btn1", "HOME MODE");

if (id(caldera).action==CLIMATE_ACTION_HEATING)

id(disp1).set_component_pic("page0.picBurn", 13);

else

id(disp1).set_component_pic("page0.picBurn", 22);

visual:

min_temperature: 10

max_temperature: 30

temperature_step: 0.1

Yep that's how I figured it, but it simply is falling over in some way. There seems to be no actual issue with the code so maybe it a problem in the nexion page format. The default fall back screen output is Sat. 8/1.

I will mess about with it some more, I got the day to change last night but broke it again today. Can't find much detailed info on the now() command to see exactly what it returns to each call type which would be helpful.

Yes that all that it outputs.

There is a fault in the conditional logic which prevents the date stripping after the first seven days of the month. change the condition to between 0 and 32 days (was 0 to 7) and it runs. This correctly inserts the Day text but still no actual date. Progress though.

Update: All resolved, I had deleted %02i/%02i from the print command by accident which was preventing the date from been printed. Put it back and all is well.