Home Assistant beginners

Think I have an Octopus Mini, little purple/pink device for live data.
I had thought linking to the Bright app would work, seems a few people got that working but doesn't look easy.
Both methods will work. I have the octopus mini and use the 'Home Assistant Octopus Energy' integration from HACS.
 
No I haven't used CSS, wouldnt know how! The theme is Frosted Glass. The calendar is Calendar Card Pro card, then a Weather Forecast card. Below that is the waste collection cards, from this vid -
. Then a Glance card showing the system stats, The solcast is shown on an Entities card, the EV car is on a grid card with top part just an image, then bottom part the stats, with a graph for the footer. Then 2 webpage cards showing Windy.

views:
- theme: Backend-selected
title: Home
icon: mdi:home
type: sections
layout: {}
badges: []
cards: []
sections:
- type: grid
cards:
- entities:
- entity: calendar.pt_days_off
accent_color: '#49eb34'
split_multiday_events: true
- entity: calendar.roster
accent_color: '#eb7734'
- entity: calendar.birthdays
accent_color: '#9834eb'
- entity: calendar.family
accent_color: '#eb34e5'
days_to_show: 10
accent_color: ''
vertical_line_width: 3px
day_separator_width: 1px
week_separator_width: 1px
month_separator_width: 1px
today_indicator: glow
show_single_allday_time: false
show_end_time: false
weather:
position: date
date:
show_conditions: true
show_high_temp: true
show_low_temp: true
icon_size: 14px
font_size: 12px
color: var(--primary-text-color)
event:
show_conditions: true
show_temp: true
icon_size: 14px
font_size: 12px
color: var(--primary-text-color)
entity: weather.gwennel
type: custom:calendar-card-pro
- type: grid
cards:
- show_current: true
show_forecast: true
type: weather-forecast
entity: weather.forecast_home
forecast_type: daily
secondary_info_attribute: wind_speed
name: Gwennel
- type: custom:mushroom-template-card
icon: mdi:home
primary: '{{ state_attr(''sensor.upcoming'',''upcoming'')[1].type }}'
secondary: >-
{% set date = as_datetime(state_attr('sensor.upcoming','upcoming')
[1].date) -%}

In {{ (date.date() - now().date()).days }} days(s)
picture: '{{ state_attr(''sensor.upcoming'',''upcoming'')[1].picture }}'
layout: vertical
fill_container: false
grid_options:
columns: 3
rows: 2
- type: custom:mushroom-template-card
icon: mdi:home
primary: '{{ state_attr(''sensor.upcoming'',''upcoming'')[0].type }}'
secondary: >-
{% set date = as_datetime(state_attr('sensor.upcoming','upcoming')
[0].date) -%}

In {{ (date.date() - now().date()).days }} days(s)
picture: '{{ state_attr(''sensor.upcoming'',''upcoming'')[0].picture }}'
layout: vertical
fill_container: false
grid_options:
columns: 3
rows: 2
- type: tile
features_position: bottom
vertical: false
entity: sensor.waste_today
show_entity_picture: true
grid_options:
columns: 6
rows: 1
- type: tile
features_position: bottom
vertical: false
entity: sensor.waste_tomorrow
show_entity_picture: true
- type: grid
cards:
- show_name: true
show_icon: true
show_state: true
type: glance
entities:
- entity: sensor.processor_use
name: CPU
- entity: sensor.processor_temperature
name: Temp
- entity: sensor.memory_free
name: Mem Free
- entity: sensor.disk_free
name: Disk Free
- entity: sensor.disk_use
name: Disk Use
- entity: sensor.disk_use_percent
name: Disk Use %
title: System Stats
state_color: true
grid_options:
columns: full
rows: null
columns: 6
- type: entities
entities:
- entity: sensor.solcast_pv_forecast_forecast_today
name: Forecast Today
- entity: sensor.solcast_pv_forecast_forecast_tomorrow
name: Forecast Tomorrow
- entity: sensor.solcast_pv_forecast_forecast_day_3
name: Forecast Day 3
- entity: sensor.solcast_pv_forecast_forecast_day_4
name: Forecast Day 4
- entity: sensor.solcast_pv_forecast_forecast_day_5
name: Forecast Day 5
- entity: sensor.solcast_pv_forecast_forecast_day_6
name: Forecast Day 6
- entity: sensor.solcast_pv_forecast_forecast_day_7
name: Forecast Day 7
title: Solcast PV Forecast
grid_options:
columns: null
rows: 10
- square: false
type: grid
columns: 1
cards:
- camera_view: auto
fit_mode: cover
type: picture-glance
entities:
- entity: sensor.polestar_6309_battery_charge_level
image_entity: /local/polestar2.jpg
image: /api/image/serve/e6cd3ccd36a36eff8ed27418b9cdb85b/512x512
- type: entities
entities:
- entity: sensor.polestar_6309_estimated_range
name: Range
- entity: sensor.polestar_6309_charging_status_2
name: Charging Status
- entity: sensor.polestar_6309_current_odometer_2
name: Odometer
- entity: sensor.polestar_6309_average_energy_consumption
name: Ave. Energy Consumption
- entity: sensor.myenergi_zappi_25816923_internal_load_ct1
name: Zappi Charge
- entity: sensor.myenergi_zappi_25816923_green_energy_today
name: Zappi Solar Charge Today
icon: mdi:lightning-bolt-outline
- entity: sensor.polestar_6309_battery_charge_level
name: Battery Level
state_color: false
show_header_toggle: false
footer:
type: graph
entity: sensor.polestar_6309_battery_charge_level
detail: 2
hours_to_show: 168
- type: iframe
url: >-
https://embed.windy.com/embed.html?...l=surface&lat=50.562&lon=-4.548&pressure=true
aspect_ratio: 100%
grid_options:
columns: null
rows: 10
- type: iframe
url: >-
https://embed.windy.com/embed.html?...l=surface&lat=50.562&lon=-4.548&pressure=true
aspect_ratio: 100%
grid_options:
columns: null
rows: 10
column_span: 4
max_columns: 6
 
Start a new automation then click on the three dots at the top right. Select "Edit in YAML". Copy the YAML code I wrote and paste it into the text field. Change nothing!! Then select the three dots again and this time "Edit in visual editor" which should take you back to the easier to use editor. YAML can be a pain to copy and paste due to indentations but it should be OK.
Legend, thank you! I've just followed those steps and set up the automation - looking at the visual editor I think I can just about understand the logic. I would never of worked out how to set that up!
I'll see if it works tomorrow come sunset :cool:
 
Legend, thank you! I've just followed those steps and set up the automation - looking at the visual editor I think I can just about understand the logic. I would never of worked out how to set that up!
I'll see if it works tomorrow come sunset :cool:

Frequently you have to look at automations from a different direction to get them to work the way you want. In my own case I’ve often had to swap Conditions with Triggers which is pretty much what I did in your case. Hope it works!
 
Think I have an Octopus Mini, little purple/pink device for live data.
I had thought linking to the Bright app would work, seems a few people got that working but doesn't look easy.

It's easy enough to setup to Bright app but I found it quite unreliable, it'd often show no data and having to reconfigure the energy dashboard when a new fork of the integration was needed was a bit of a faff.

These days I'm using one of these plus this HACS integration. Everything now gets pulled into HA from the IHD over MQTT and it's a big improvement - the refresh rate of the data is significantly quicker.

Probably not of interest to you if you've got an Octopus Mini but could be interesting to others.
 
Frequently you have to look at automations from a different direction to get them to work the way you want. In my own case I’ve often had to swap Conditions with Triggers which is pretty much what I did in your case. Hope it works!
It works a treat, well chuffed with that. Thanks again!

Now onto the next challenge, I'd like to get HA to send out get requests/commands on my local network. Wish me luck :D
 
Last edited:
All my automations say this.

"This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn't have an ID."

They were all fine yesterday.
 
Back
Top Bottom