Home Assistant beginners

Just use good/legit SD cards - I have constant looping 4K CCTV video writing to endurance SD cards and have done so for quite literally years without failure. I ran a fairly chunky HA setup on an endurance class SD card for years and years before moving to a NUC and never once had a failure on that particular Pi. I ran a 6-node Pi-based Kubernetes cluster with a moderate local I/O and yes, cheap/counterfeit SD cards degraded but after switching to decent cards I never had another failure.

You should be running backups like anything important but I wouldn't overly worry about it. The best solution if you are worried about it is to do it "properly" with a Pi 5 and an M.2 hat.
 
isn't there a problem with power failures on pi's where it may corrupt the sd card to the point where you have to re-built the image. Its certainly been the case with the zero W I use for solar monitoring...
 
I spent a couple of weeks setting up HA on an Intel NUC (@DRZ) and tweaking all the power monitoring etc etc.

Then I never even looked at it for a month so clearly I didn’t need it.

Rebuilt it to Windows and it’s now my PRTG system as the old Gigabyte tiny PC I had was on the way out.
 
  • Sad
Reactions: DRZ
Can anyone help me with my CCTV setup please. I'm having issues since updating to version 0.15 of Frigate. The errors I'm getting are: "WARNING : Too many unprocessed recording segments in cache for garage_camera_fr. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...".

This is happening on all 4 of my cameras. They are a RLC-510A for front and back gardens, RLC-520A for garage and E1 Pro (WiFi) for kitchen. The E1 Pro didn't work with go2rtc which is why it doesn't show in the list of cameras below. Only included the front camera code below as the code is the same for all.

YAML: 
mqtt:
  host: 192.168.1.19
  user: USERNAME
  password: PASSWORD

detectors:
  coral:
    type: edgetpu
    device: usb

go2rtc:
  streams:
    front_camera_fr_main:
      - ffmpeg:http://192.168.1.100/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USERNAME&password=PASSWORD#video=copy#audio=copy#audio=opus
    front_camera_fr_sub:
      - ffmpeg:http://192.168.1.100/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=USERNAME&password=PASSWORD
    back_camera_fr_main:
      - ffmpeg:http://192.168.1.101/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USERNAME&password=PASSWORD#video=copy#audio=copy#audio=opus
    back_camera_fr_sub:
      - ffmpeg:http://192.168.1.101/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=USERNAME&password=PASSWORD
    garage_camera_fr_main:
      - ffmpeg:http://192.168.1.102/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USERNAME&password=PASSWORD#video=copy#audio=copy#audio=opus
    garage_camera_fr_sub:
      - ffmpeg:http://192.168.1.102/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=USERNAME&password=PASSWORD

#Cameras
cameras:
  front_camera_fr:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/front_camera_fr_main
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/front_camera_fr_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-aac
    best_image_timeout: 60
    detect:
      fps: 7
      enabled: true
      width: 896
      height: 672
      max_disappeared: 25
    objects:
      track:
        - person
    motion:
      mask:
        - 0.213,0.193,0.473,0.108,0.723,0.11,0.792,0.211,1,0.541,1,0,0.436,0,0.001,0,0,0.494
        - 0.301,0.927,0.231,0.897,0.182,0.924,0.153,1,0.31,1
    zones:
      front_camera_drive_zone:
        coordinates:
          0.426,0.613,0.354,0.719,0,0.629,0,0.804,0,0.909,0,1,0.244,0.879,0.318,0.928,0.363,1,0.41,1,0.527,1,1,1,0.96,0.487,0.768,0.182,0.724,0.118,0.471,0.116,0.454,0.204,0.462,0.333,0.463,0.491
        objects: person
        inertia: 3
        loitering_time: 0
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: false
      crop: false
      required_zones:
        - front_camera_drive_zone
      retain:
        default: 10
        objects:
          person: 10
    record:
      enabled: true
      expire_interval: 360
      retain:
        days: 0
        mode: motion
      alerts:
        retain:
          days: 10
        pre_capture: 3
        post_capture: 3
      detections:
        retain:
          days: 1
    review:
      alerts:
        required_zones: front_camera_drive_zone
 
Last edited:
Has anyone on here seen the new Home Assistant Voice that Nabu Casa are releasing?

https://www.home-assistant.io/voice-pe/

Seems interesting since it has a 3.5 jack for audio output as I've been looking for something to replace the Google Homes/Nest Homes for a while now however it would have been nice if it had a semi-decent speaker on it as I've yet to find anything for the price that can do commands plus also works as a reasonable sounding speaker in groups
 
TechMinerUK said:
Has anyone on here seen the new Home Assistant Voice that Nabu Casa are releasing?

https://www.home-assistant.io/voice-pe/

Seems interesting since it has a 3.5 jack for audio output as I've been looking for something to replace the Google Homes/Nest Homes for a while now however it would have been nice if it had a semi-decent speaker on it as I've yet to find anything for the price that can do commands plus also works as a reasonable sounding speaker in groups
Click to expand...
It’s been out for a while. I’ve had one since it was released but I have to confess I’ve not used it very much as I’ve just not had the time to play about with it. I’ve been put off by the fact I don’t like any of the limited waken words which is a very shallow reason not to use it! Even now I’d say that you get one to experiment with. The PE stands for Preview Edition after all.
 
Bluecube said:
It’s been out for a while. I’ve had one since it was released but I have to confess I’ve not used it very much as I’ve just not had the time to play about with it. I’ve been put off by the fact I don’t like any of the limited waken words which is a very shallow reason not to use it! Even now I’d say that you get one to experiment with. The PE stands for Preview Edition after all.
Click to expand...
Ahh, I saw preview edition and assumed it had just been brought out!

I'll likely pick one up over the next few weeks and see if I can bodge a semi-decent speaker onto it :)
 
There's at least one project that has already done that

community.home-assistant.io

Hi-Fi Audio Upgrade for Home Assistant Voice PE (Complete How-to Guide)

Hi-Fi Upgrade for Home Assistant Voice PE! Audio Comparison / Sample Features 2x5W speakers >= 3x output volume Massive increase in audio quality One input cable (USB-C power) - everything fits inside the housing Reuses stock rubber feet Open-source 3D design files License...
community.home-assistant.io community.home-assistant.io
 
The1nonly1 said:
Can anyone help me with my CCTV setup please. I'm having issues since updating to version 0.15 of Frigate. The errors I'm getting are: "WARNING : Too many unprocessed recording segments in cache for garage_camera_fr. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...".
Click to expand...
Do all your individual stream URLs for go2rtc (minus ffmpeg: ) and the Frigate cameras still work in a browser or something like VLC ?

I'd clone your config and strip out everything apart from one camera and try and get that working.

I can't see any ffmpeg hwaccel_args:, wondering if any of the presets help with processing frames in your instance? Are you getting any video from any camera?
 
Last edited:
@DRZ was it you that suggested Predbat?

I need a little help configuring it.

1747427148168.png


I've got this far - and set up the apps.yaml,

1747427251745.png


So it's picking up a lot of the stuff.

I kinda want to find out if I can be more specific in controlling the charging / discharging - or if you generally let it do it's thing.

I wanted to explore making it only charge 25% in the evening by the time 5am hits if the day is going to be a 20kW+ day. But to do a max charge between 2-5am if the forecast would be under 10kW. Or is that not even needed?

Am I missing anything critical from my config?

YAML: 
pred_bat:
  module: predbat
  class: PredBat

  # Sets the prefix for all created entities in HA - only change if you want to run more than once instance
  prefix: predbata

  # Timezone to work in
  timezone: Europe/London

  # Currency, symbol for main currency second symbol for 1/100s e.g. $ c or £ p or e c
  currency_symbols:
   - '£'
   - 'p'

  # Number of threads to use in plan calculation
  # Can be auto for automatic, 0 for off or values 1-N for a fixed number
  threads: auto

  # Set to auto-match with a GivEnergy serial number, but you can override the serial or the sensor names
  # if it doesn't work or if you have more than one inverter you will need to list both
  geserial: 'CE2219G489'

  # Sets the maximum period of zero load before the gap is filled, default 30 minutes
  # To disable set it to 1440
  load_filter_threshold: 30

  #
  # Sensors, more than one can be specified and they will be summed up automatically
  #
  load_today:
    - sensor.givtcp_{geserial}_load_energy_today_kwh
  import_today:
    - sensor.givtcp_{geserial}_import_energy_today_kwh
  export_today:
    - sensor.givtcp_{geserial}_export_energy_today_kwh
  pv_today:
    - sensor.givtcp_{geserial}_pv_energy_today_kwh

  # When set use the REST API rather than HA entity for control, should be more reliable/faster to control
  # Set one per inverter
  # If using Docker then change homeassistant.local to the Docker IP address
  givtcp_rest:
    - 'http://10.10.10.13:6345'

  # Battery control settings
  charge_rate:
    - number.givtcp_{geserial}_battery_charge_rate
  discharge_rate:
    - number.givtcp_{geserial}_battery_discharge_rate
  battery_power:
    - sensor.givtcp_{geserial}_battery_power
  pv_power:
    - sensor.givtcp_{geserial}_pv_power
  load_power:
    - sensor.givtcp_{geserial}_load_power
  soc_kw:
    - sensor.givtcp_{geserial}_soc_kwh
  soc_max:
    - sensor.givtcp_{geserial}_battery_capacity_kwh
  reserve:
    - number.givtcp_{geserial}_battery_power_reserve
  inverter_mode:
    - select.givtcp_{geserial}_mode
  inverter_time:
    - sensor.givtcp_{geserial}_invertor_time
  charge_start_time:
    - select.givtcp_{geserial}_charge_start_time_slot_1
  charge_end_time:
    - select.givtcp_{geserial}_charge_end_time_slot_1
  charge_limit:
    - number.givtcp_{geserial}_target_soc
  scheduled_charge_enable:
    - switch.givtcp_{geserial}_enable_charge_schedule
  scheduled_discharge_enable:
    - switch.givtcp_{geserial}_enable_discharge_schedule
  discharge_start_time:
    - select.givtcp_{geserial}_discharge_start_time_slot_1
  discharge_end_time:
    - select.givtcp_{geserial}_discharge_end_time_slot_1

  # Pause mode settings
  pause_mode:
   - select.givtcp_{geserial}_battery_pause_mode
  pause_start_time:
   - select.givtcp_{geserial}_battery_pause_start_time_slot
  pause_end_time:
   - select.givtcp_{geserial}_battery_pause_end_time_slot

  # Only gen3 supports discharge target SOC, will be ignored if not present
  discharge_target_soc:
    - number.givtcp_{geserial}_discharge_target_soc_1

  # Inverter max AC limit (one per inverter). E.g for a 3.6kw inverter set to 3600
  inverter_limit:
    - 3000

  # Inverter clock skew settings
  inverter_clock_skew_start: 0
  inverter_clock_skew_end: 0
  inverter_clock_skew_discharge_start: 0
  inverter_clock_skew_discharge_end: 0
  clock_skew: 0

  # Using existing Solcast integration from Home Assistant
  # No need for API key as we're using the HA integration sensors directly
  pv_forecast_today: sensor.solcast_pv_forecast_forecast_today
  pv_forecast_tomorrow: sensor.solcast_pv_forecast_forecast_tomorrow
  pv_forecast_d3: sensor.solcast_pv_forecast_forecast_day_3
  pv_forecast_d4: sensor.solcast_pv_forecast_forecast_day_4

  # Octopus energy rate configuration
  metric_octopus_import: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_rate)'
  # metric_octopus_import: 'sensor.octopus_import_pence'
  metric_octopus_export: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_export_current_rate)'
  metric_standing_charge: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_standing_charge)'


  # Battery configuration
  # Force discharge from 4-7pm with 25% minimum SoC
  rates_export_override:
   -  start: '16:01:00'
      end: '18:59:00'
      soc_target: 40
      discharge_power_limit: 3000
      reason: "Peak export window"
      inverter_mode: "Timed Discharge"

  rates_import_override:
    - start: '05:00:00' # Daytime Solar Only
      end: '02:00:00'   # (Next day)
      inverter_mode: "Eco"
      rate: 999
      reason: "Daytime Solar Charging & Self-Consumption"
  #  - start: '19:00:00' # Evening/Night Self-Consumption
  #    end: '02:00:00'   # (Next day)
  #    inverter_mode: "Eco"
  #    rate: 999
  #    reason: "Evening/Night Self-Consumption"

  # Daytime eco mode (5am-4pm) - let inverter manage solar charging and self-consumption
  # -  start: '05:00:00'
  #    end: '16:00:00'
  #    inverter_mode: "Eco"
  #    reason: "Daytime Solar Charging & Self-Consumption"
  #    rate: 999  # Prevent grid charging with high rate

  # Night mode settings for 7pm-2am
  # -  start: '19:00:00'
  #    end: '02:00:00'
  #    inverter_mode: "Eco"
  #    rate: 999  # Prevent grid charging with high rate
  #    reason: "Evening/Night Self-Consumption"
      
  # Night charging window (2am-5am) - will be automatically managed
  # Predbat will determine charge amount based on forecast

  # Optimal charge planning configuration
  # This configures the rules for adaptive night charging based on forecast
  adaptive_charging: true
  # night_rate_threshold: 15
 
  # Solcast forecast threshold settings
  pv_forecast_min_threshold: 10  # Minimum threshold for low solar day
  pv_forecast_good_threshold: 20  # Threshold for high solar day
 
  # Adaptive SOC targets based on forecast
  adaptive_target_soc:
  low_pv: 100   # Target 100% SOC for low solar days
  high_pv: 25   # Target 25% SOC for high solar days
    
  # Minimum SOC fallback setting 
  min_soc_target: 25
 
  # Days previous is the number of days back to find historical load data
  days_previous:
    - 7

  days_previous_weight:
    - 1

  # Number of hours forward to forecast
  forecast_hours: 48

  # Battery scaling makes the battery smaller or bigger than its reported
  battery_scaling:
    - 1.0

  # Export triggers for automation
  export_triggers:
     - name: 'large'
       minutes: 60
       energy: 1.0
     - name: 'small'
       minutes: 15
       energy: 0.25

  # Watch list for sensors to trigger plan updates
  watch_list:
    - '{pv_forecast_today}'
    - '{metric_octopus_import}'
 
It was me but I've yet to put the time into getting it fully functioning with my inverter. It isn't supported so I'm having to do a lot of fiddling and faffing - and this wasn't helped by the inverter manufacturer changing their APIs completely without much in the way of notice. You've given me the kick I need to get going so perhaps this week I'll finally get it sorted.

I believe it should be possible to do what you're suggesting but from what I have read it is designed to learn and adapt so might be best leaving it to its own devices for a week/month and see what it ends up doing?
 
DRZ said:
It was me but I've yet to put the time into getting it fully functioning with my inverter. It isn't supported so I'm having to do a lot of fiddling and faffing - and this wasn't helped by the inverter manufacturer changing their APIs completely without much in the way of notice. You've given me the kick I need to get going so perhaps this week I'll finally get it sorted.

I believe it should be possible to do what you're suggesting but from what I have read it is designed to learn and adapt so might be best leaving it to its own devices for a week/month and see what it ends up doing?
Click to expand...
Yeah that's what I've done. It says it needs 7 days of data I think.

I used the octopus, givenergy, solcast template and it seems to be working well.

Thank you for the recommendation!
 
Todays dopamine hit with HA. Programmed the hallway Hue smart button that controls the lights, for long press = open garage doors (Meross smart integration). Surprising how often it gets used.
 
A recent purchase that I thought was going to be a cheap fudge ended up being a great buy

Google 2 or 4 channel tuya relay.... bought both versions from Ali(with housing) and some nice looking 433 wireless stick on remote panels

Here's the thing that really impressed me, from the Tuya app you can pair any 433 remote to the relay switches so the nice glass touch panel that I got off the bay also worked. The relay itself is connected to HA with local Tuya and the switches / panel are perfect for the not so technically inclined ie the Mrs... Also the switches will always work regardless of whether a network or HA is unavailable
 
Last edited:
I’ve just started a thread looking for some recommendations for a come assistant compatible roller garage door controller.

If anyone has any experience with these would you mind popping over to this thread:

Roller Garage Door Openers - any recommendations?

Hi all I’ve currently got two doors controlled by NECO controllers, specifically these: http://www.britaliadoors.co.uk/controls/neco-garage-remote-control/?Page_ID=3610&refpid=41892&id=781388 I’m looking at options to replace it with something ‘smarter’ or add smart functionality to this...
forums.overclockers.co.uk forums.overclockers.co.uk
 
b0rn2sk8 said:
I’ve just started a thread looking for some recommendations for a come assistant compatible roller garage door controller.

If anyone has any experience with these would you mind popping over to this thread:

Roller Garage Door Openers - any recommendations?

Hi all I’ve currently got two doors controlled by NECO controllers, specifically these: http://www.britaliadoors.co.uk/controls/neco-garage-remote-control/?Page_ID=3610&refpid=41892&id=781388 I’m looking at options to replace it with something ‘smarter’ or add smart functionality to this...
forums.overclockers.co.uk forums.overclockers.co.uk
Click to expand...
I use a Meross and its been solid. Its just a smart box that connects to wifi, and has 2 wires that goes to pins on existing roller shutter door switching unit.
 
Last edited:
tres said:
Moved from an Rpi4 to a N100 NUC running proxmox
I'm surprised at the difference it's made, rock solid, faster responses, very much worth the upgrade.
Click to expand...

I actually run proxmox on a meatier machine 5700u, coral TPU, 64G RAM, 13TB of total storage
Runs everything I need so far, HA, localAI, whisper, frigate, openwrt and numerous other things

Even by itself HA running on a PI is pants - any serous HA'er should be running on a minimum of a N100
 
Last edited:
Subliminal Aura said:
I actually run proxmox on a meatier machine 5700u, coral TPU, 64G RAM, 13TB of total storage
Runs everything I need so far, HA, localAI, whisper, frigate, openwrt and numerous other things

Even by itself HA running on a PI is pants - any serous HA'er should be running on a minimum of a N100
Click to expand...
Well done you.

RPi4 handled 60 ZigBee devices for years without a massive issue. It's a completely adequate way of using HA.
 
You must log in or register to reply here.
Back
Top Bottom