Home Assistant - New Zealand

I’ve not used Plex into a card to visualise much, rather the ability to control actions, when plex is playing switch lights on / off etc.

Have a look here, this looks like an interesting card design someone came up with on Reddit

1 Like

Hi Guys, I recently purchased a Sensy One S1 in white (Products – Sensy-One) presence detector. It works fantastic using the map card, tracking up to 3 things in real time (https://youtu.be/H-Rij8gbK3s?si=ZKf0Zzg6P1iMIp_B&t=239). I had hoped to use this in my lounge to detect presence in various zones (up to 10 zones can be setup) and such…

BUT! I didn’t read the fine print when I ordered. Max distance is 6m, and my lounge/dining area is 7.5m long with an entrance at at the far end, so it won’t detect if there is presence until someone steps right into the room. Not good for light automation! Unfortunately I cant think of any thing or where else I need to us this in the house.

The unit cost NZ$91.00 including shipping to get here. Happy to send free to anyone in NZ if they are interested. Please hit me up with an offer?!

Very basic dashboard setup…

1 Like

Thanks I’ve installed that and like the look of it.

So now that flick is sold, are you moving?

I was about to go to flick but now im stuck in “What home assistant compatible power companies are there now”

I’ve just switched to Powershop, but it looks like there’s no HA integration available. Has anyone tried to get information out of Powershop recently? I’ll start poking around this evening.

Im currently using powershop using multiscrape to get prices etc and then a Shelly EM to track the power usage if that helps?

Thanks. Yeah, I’ve started to set up a scraper to get the usage reports, but I noticed a bug in the detailed consumption report which is a deal breaker for me. We have three meters on our property and the detailed report doesn’t tell me which is which - it just shows three readings for each timespan on the CSV without identifying which meter the reading is associated with.

I spent 1.5 hours on a frustrating chat session trying to explain to the support people with no luck. I then sent them an email with details and got back an auto-reply saying that the average response time is 10 days.

I think my time with Powershop is going to be short-lived… :upside_down_face:

Here is the yaml im using in the config file to make it all work FYI. Plus the template to set the daily supply charge. Fingers x’ed, touch wood, this has all worked well for me for a while now.

multiscrape:
  - name: Powershop Rates
    resource: 'https://secure.powershop.co.nz/rates'
    log_response: true
    scan_interval: 43200 #every 12hrs
    verify_ssl: false
    form_submit:
      submit_once: true
      verify_ssl: false
      resource: 'https://secure.powershop.co.nz'
      select: ".content > form"
      input:
        email: !secret powershop_user
        password: !secret powershop_pass
    sensor:
      - unique_id: powershop_offpeak
        name: Powershop Off Peak
        select: "#main_container > div > div.row > div.rates-table-container.base-rates-table > table > tbody > tr:nth-child(1) > td.base-rates.current > span.rate.gst_inclusive"
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary     
      - unique_id: powershop_peak
        name: Powershop Peak
        select: "#main_container > div > div.row > div.rates-table-container.base-rates-table > table > tbody > tr:nth-child(2) > td.base-rates.current > span.rate.gst_inclusive"      
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary 
      - unique_id: powershop_weekend
        name: Powershop Weekend
        select: "#main_container > div > div.row > div.rates-table-container.base-rates-table > table > tbody > tr:nth-child(3) > td.base-rates.current > span.rate.gst_inclusive"      
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary 
      - unique_id: powershop_offpeak_special
        name: Powershop Off Peak Special
        select: "#main_container > div > div.row > div.rates-table-container.special-rates-table > table > tbody > tr:nth-child(1) > td.base-rates.current > span.rate.gst_inclusive"
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary     
      - unique_id: powershop_peak_special
        name: Powershop Peak Special
        select: "#main_container > div > div.row > div.rates-table-container.special-rates-table > table > tbody > tr:nth-child(2) > td.base-rates.current > span.rate.gst_inclusive"      
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary
      - unique_id: powershop_weekend_special
        name: Powershop Weekend Special
        select: "#main_container > div > div.row > div.rates-table-container.special-rates-table > table > tbody > tr:nth-child(3) > td.base-rates.current > span.rate.gst_inclusive"      
        unit_of_measurement: "NZD/kWh"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary
      - unique_id: powershop_daily_charge
        name: Powershop Daily Charge
        select: "#main_container > div > div.row > div.rates-table-container.base-rates-table > table > tbody > tr:nth-child(4) > td.base-rates.current > span.rate.gst_inclusive"      
        unit_of_measurement: "NZD"
        value_template: '{{ (value | int) / 100 | float | round(3) }}'
        device_class: monetary      
        on_error:
          log: warning
          value: last

template:
  - sensor:
    - name: "Powershop Supply Charge"
      unit_of_measurement: "Wh"
      device_class: energy
      state_class: total_increasing
      state: >-
        {{ int(as_timestamp(now()) | timestamp_custom("%d")) + 1 - int(as_timestamp("2023-08-03") | timestamp_custom("%d")) }}
1 Like

Thanks - that’s super helpful.

I’m interested to know what benefits you get from getting info from your power provider more often than monthly (with your invoices).

I am an Electrician (by trade) and I used to work for a “Power Authority” as “Test Room Foreman” often helping customers manage their power consumption.

None of the answers came from their power bills.
The biggest savings come from eliminating wastage (heating when you don’t really need it, boiling 6 cups of water when you only need 2, putting lids on cooking pots, running hot water when cold would do, using clothes dryers when the sun is shining etc.) and changing habits (shift as much usage as possible to “night rate”).

I use Home Assistant automations to control our aircon, chargers (bikes, cars and tools), water heater, under tile heaters, towel rails and lights. (One day I hope to get a “smart” washing machine and dishwasher too)

(That’ll be 2 cents)
Rob

I’m a customer of Powershop and it would be great to get the usage data into HA. Could you use the multiscape component to get the usage data from the secure.powershop.co.nz/usage_report page? I’ve looked at your yaml code for the rates and the source for the usage-report page but I’m not web savy so it would be trial and error for me to work it out. Getting the usage data once a day for every half hour and showing that in HA I guess won’t help you save power, but I like the idea of seeing it.

I’ve been importing usage data into InfluxDB for a couple of years now, and then building dashboards to show usage patterns. Definitely helps to visually identify where we are wasting power. We’ve been on peak/offpeak plans for a while now, and the charts have helped us to see if we’re making the most of the offpeak rates. We also have three meters on our property and it’s useful to see how the usage of each one varies depending on what’s going on in the house.

OK, sorry forgot some of the setup… So I setup 3 schedule helpers:

Which are like this:

Then I have the following automation that updates input_number.powershop_current_kwh_cost & input_text.current_powershop_rate based on those schedules.

alias: Powershop Update Current Rate
description: ""
mode: single
triggers:
  - entity_id:
      - schedule.power_weekday_peak
    from: "off"
    to: "on"
    id: peak
    trigger: state
  - entity_id:
      - schedule.power_weekday_off_peak
    from: "off"
    to: "on"
    id: offpeak
    trigger: state
  - entity_id:
      - schedule.power_weekend_off_peak
    from: "off"
    to: "on"
    id: weekend
    trigger: state
conditions: []
actions:
  - data:
      value: "{{ states('sensor.powershop_'~trigger.id~'') }}"
    target:
      entity_id: input_number.powershop_current_kwh_cost
    action: input_number.set_value
  - data:
      value: |
        {% if trigger.id == 'peak' %}
          Weekday Peak
        {% elif trigger.id == 'offpeak' %}
          Weekday Off Peak
        {% elif trigger.id == 'weekend' %}
         Weekend Off Peak
        {% else %}
          None
        {% endif %}
    target:
      entity_id: input_text.current_powershop_rate
    action: input_text.set_value

These you can then use in your energy dashboard setup:

Firstly, I cant remember when I last actually looked at a power invoice. We know how much we are spending with them each month. With HA, im getting the rates from powershop every 12 hours to make sure that they are current - and obviously so I dont have to look a power invoice and enter something into HA manually. Then using the Shelly EM I can now track everything in the house.

To be honest, im not really looking to reduce cost, it’s more about the visibility of things in our house and what they consume.

I haven’t been on HAS for a while, I had too much other stuff going on and I found myself getting frustrated and overwhelmed with it all due to lack of time.
But now I’m back and was just reading the Powershop Multiscrape thread which is very interesting to me. I’m just trying to get my head around what goes where and what I need to edit in order to make it all work.

However one thing that I have run into is my Fronius setup (again) I stupidly lost the API Keys that I originally had and now I can’t complete the setup using the Fronius integration. Does anyone know if it’s possible to get these easily? Last time the installer just showed me the data in the Gen24 Inverter Technician page, but due to lots of changes at the Installers, it seems they have updated the Tech password and so access is no longer granted to me and I don’t seem able to make anyone understand that I’m not trying to get the solarweb premium subscription I just need the API keys to make Homeassistant work.

Anyone have any ideas how I can get this info now? I haven’t checked the Modbus data so perhaps it’s hidden in there?? Or Can I glean the info I require and not use the Fronius integration??

TIA

I have the Fronius Integration “locally” with 50 entities.
I think that all I needed was the local IP address and maybe my username and password for the Solarweb stuff.

Thanks Rob, I’ve been trying to load the wrong thing the whole time! I had two different Fronius integrations and the one I kept trying to load was asking for the API Keys etc.

Thanks so much

My implementation of pulling down information via the CSV might be of help.

1 Like

Thanks for this.

Now that Frank is closing down, I’ll be closing that repo in September. Happy to take this over for Genesis if you wanted to submit it back to the main repo. Although not 100% sure I’ll be switching to Genesis so if you have capacity to keep/maintain it that’s cool too.

I’m currently working on an extension to show your what your historical power costs would haven been for each provider, might be more motivated to finish it now I’m back looking again…