Home Assistant

10-10-20 · 27-01-2024 11:54pm

https://www.boards.ie/discussion/comment/121683083#Comment_121683083

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

https://pve.proxmox.com/wiki/Root_Password_Reset

Jonathan · 28-01-2024 12:32am

https://www.boards.ie/discussion/comment/121683168#Comment_121683168

Or hope that you're still signed in on one of the virtual consoles. 😉

emaherx · 28-01-2024 7:27am

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

poker--addict · 28-01-2024 9:56am

ok I now joined the dots. My HA tools are likely not working since 24 hour power failure

I can't find home assistant when using IP internally

emaherx · 28-01-2024 10:04am

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.

poker--addict · 28-01-2024 10:29am

bingo, ran a scan and found new IP. So I am in

guess now I just change cloudflare somewhere with new IP

thanks very much.

I am not sure it's worth investing in standby power tbh. It is a bit surprising in today's world that all these smart home options aren't more simple (at least without paying 1000s for smart house gates etc). HA provides cost effective solutions but some knowledge of computer language etc helps (or being a boards.ie with patient people willing to answer stupid questions - but shouldn't have to be like this)

rant over - delighted the help has me working again or close to it

Jonathan · 28-01-2024 10:59am

Give it a static DHCP lease in the router and that will avoid the fun next time.

emaherx · 28-01-2024 11:17am

https://www.boards.ie/discussion/comment/121683865#Comment_121683865

If you are using the cloudflare addon you shouldn't have to change any settings even though the IP changed. It might be different if you have manually set up a tunnel. If using the addon, make sure it is running or try restarting it before changing anything.

I don't think anyone would disagree with you, but different manufactures still refuse to cooperate properly so unless you stick with one ecosystem then HA is the best option. Sticking with one ecosystem is not great either as it is impossible to find everything you may want within one and usually ends up locking you into more costly products. The constant updates are both HA's strength and it's weakness, technology changes rapidly so it needs to keep up, but in fairness it's gotten much better and simpler to use since I started using it.

The power backup suggestion is what I've been thinking about for the last week for myself and I think I will need to consider, my setup is probably a little more complicated than most as it covers multiple locations connected through VPN's run by a single HA instance losing power can mess things up a bit and I need to reboot a few devices if they happen to come online before HA. At least if I could keep HA and the router online then everything else would recover more easily without intervention.

paulbok · 28-01-2024 7:15pm

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.

Shoog · 28-01-2024 7:46pm

I am most of the way through setting up an NSPanel as a smart thermostat. I am using someone else's yaml file to set it up and have got almost everything working but it is showing the incorrect date (and possibly day though I think I have sorted that). The logic is;

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

const char *str = day_semana[id(homeassistant_time).now().day_of_week]; // range [0-6, Mon.=0]

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

The bolded bit is at fault, but I do not know enough about the code to understand the issue. Anyone make a suggestion as to whats the issue.

swampgas · 28-01-2024 8:13pm

https://www.boards.ie/discussion/comment/121686237#Comment_121686237

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.

10-10-20 · 28-01-2024 9:15pm

https://www.boards.ie/discussion/comment/121686237#Comment_121686237

Ah, this is a Nextion api command, no wonder the printf looked odd.

https://esphome.io/api/classesphome_1_1nextion_1_1_nextion#a2d4cf1e2f4fe2ad1c975cb069bf698d4

I think we might need to see what page0.date looks like to understand that better...

Shoog · 28-01-2024 11:00pm

https://www.boards.ie/discussion/comment/121686603#Comment_121686603

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.

10-10-20 · 29-01-2024 12:08am

https://www.boards.ie/discussion/comment/121687133#Comment_121687133

I was assuming that Page0 is one of the screen pages used to present data? I use oled displays on my esp32's and I write pages like this:

Screenshot_20240128_230711_Home Assistant.jpg

Do you not have similar in the device configuration section?

Shoog · 29-01-2024 10:00am

https://www.boards.ie/discussion/comment/121687550#Comment_121687550

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:

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

# Define some inputs

binary_sensor:

# Switches between HEAT or OFF mode

- platform: gpio

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

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

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

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

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

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

internal: true

accuracy_decimals: 0

variable_name: dp

update_interval: 1s

- platform: uptime

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

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

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

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

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

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

10-10-20 · 29-01-2024 1:39pm

~~Stick that in code quotes @Shoog and we might be able to read it. ;)~~

Nevermind.

So it's this part... (as you previously posted) which I now understand a bit better:

  - 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());'

So it seems to me that page0 is the initial page which is displayed on the Nextion device, subsequent pages would be page1 and so forth. You can write to each of the elements on that page (such as "wind", "date, "time", "btn0") with text or icon objects.

Initially the date/time string is gathered from Home Assistant as a string through the time platform up at line 49.

time:
  - platform: homeassistant
    id: homeassistant_time
    timezone: Europe/London

Then this lambda converts that string into the required elements "day (day of month)", "month (month of year)":

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

Below that it the lambda then takes the day_week as an integer (the day number within a week) and then converts it into a text string of the day name called "str".

Then here in this line...

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

It uses the "str, day and month" to create a new string of, for example: "Monday 29/01" which is then sent to the date object within page0.

The Nextion should then be displaying that within the boxes or options on that initial page on the device.

Shoog · 29-01-2024 3:04pm

https://www.boards.ie/discussion/comment/121689407#Comment_121689407

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.

10-10-20 · 29-01-2024 3:11pm

https://www.boards.ie/discussion/comment/121689873#Comment_121689873

So you always get Sat 8/1, nothing else?

I can modify that code and run it against my oled screen later and see what happens, should be simple enough (takes hat off head and adds salt & pepper).

Shoog · 29-01-2024 4:08pm

https://www.boards.ie/discussion/comment/121689926#Comment_121689926

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.

10-10-20 · 30-01-2024 10:41am

@Shoog - works fine here. 😂 (to a point)

      - id: page4
        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
            it.printf(0, 0, id(font1), "1: %s", str);
            it.printf(0, 44, id(font1), "2: %02i/%02i", day, month);

I took out the if-statement above (as it wasn't working - more to follow) and broke out the code a bit (to fit my 0.96" oled), now I get this on the display:

I'm thinking that you might have a broken connection back to the HA server and you're not getting a date/time...? Could that be the issue? I'll test more later.

10-10-20 · 30-01-2024 10:52am

Just reading a bit more about the nextion displays, where did you get it? Amazon? They look interesting as a control interface.

They take an SD card which is formatted with the used-designed layout then receive a UART in to input the values and text for each of the predefined elements. Pretty cool. Might look into obtaining one as a way of getting the kids to stop turning on the boiler to heat water when it already there and waiting. feckers.

JayBee66 · 30-01-2024 11:04am

On a related note, for the Solcast integration my HA outputs "Today", "Tomorrow" and "The Day After". How would the code above be altered to yield new day labels for the three PV forecasts?

10-10-20 · 30-01-2024 11:29am

https://www.boards.ie/discussion/comment/121693698#Comment_121693698

On a Nextion?

You would have to import the equivalent sensor (such as sensor.energy_production_tomorrow_2 which I have for the basic Forecast.Solar integration) over the to Nextion. You import them onto the ESP32 like so, for example:

sensor:
  - platform: homeassistant
    id: office_temperature
    entity_id: sensor.tsr_ah_kitchenlower_air_temperature
  - platform: homeassistant
    id: downstairs_trv_temp_median
    entity_id: sensor.downstairs_trv_temp_median

Then work them into whatever layout (via suitable printf statements) you composed on the Nextion via the editor mentioned on the esphome page.

https://esphome.io/components/display/nextion.html

paulbok · 08-02-2024 7:08pm

Is a Ring subscription still needed to access your cameras in Home Assistant.

Just got notice they are upping the sub price by a dollar per cam.

Just started a long overdue process to setup Frigate and install some other cameras around. Plan on replacing my Ring doorbell and a floodlight cam, find there is an awful lag in detecting movement and the notification.

If the sub isn't needed, I'd move the floodlight cam to a less important area.

tnegun · 08-02-2024 7:24pm

I've never had a sub and have full access to mine in HA using the Ring-MQTT addon.

poker--addict · 17-02-2024 12:05pm

My gate opening via phone entering a zone near my home has stopped working. I am not sure where to start with a fix?

10-10-20 · 17-02-2024 12:15pm

https://www.boards.ie/discussion/comment/121779402#Comment_121779402

Using the newer proximity features? Did you set it up as an automation? If so go into the automation and click "edit in YAML" and then post the text here.

lostboy75 · 05-04-2024 2:40pm

After quite a while using Lidl gateway with their plugs and bulbs I have finally gotten around to setting up HA, all I had on the Lidl setup has been transferred over and is working as it should. Happy with it all so far and excited by the new possibilities it will allow for. Was getting really fed up of each time Lidl smart gear was in store it was, the gateway, the plugs and the bulbs again and again.

So this might be considered a heads up, another newbie that might have questions has joined! :-)

paulbok · 05-04-2024 7:39pm

I have a couple of the Lidl smart plugs, strips and led strips. Can't fault them at all.

Them and IKEA are a great source of cheap kit without shopping in China, but I have found some of the their stuff temperamental.

lostboy75 · 06-04-2024 11:33am

I agree, had no issue with the Lidl stuff, just wanted access to other items, motion sensor, switches etc. If the were released here I might not have jumped. Picked up a few smart tech stuff on clearance in woodies a few months back, had had ordered a few items from Amazon, all ZigBee, but none would work with the Lidl gateway, unsurprisingly.

Home Assistant

Comments