David Gardiner

Troubleshooting GitHub Package NuGet feeds with GitHub Actions

2026-09-26T16:00:00.000+09:30

If you're building .NET applications with GitHub Actions, then you want to ensure the correct .NET SDK is in place. If you're using GitHub Packages to access a private NuGet feed then you'll also need to be able to authenticate to that feed. The actions/setup-dotnet action is great for doing both of these tasks, but there are some gotchas I've encountered when using it.

Using the action is pretty straight forward:

- uses: actions/setup-dotnet@v6

If you have a global.json file present in the root of your repo it will read it by default. If you don't then it doesn't know which version to install and you'll see this logged in the workflow run:

The global.json wasn't found in the root directory. No .NET version will be installed.

Better to use dotnet-version to indicate one (or more) SDK version ranges to install:

- uses: actions/setup-dotnet@v6
  with:
    dotnet-version: 10.0.x

That is fine, but the best approach in my opinion is to have a global.json file with an sdk property set like this:

{
  "sdk": {
    "version": "10.0.401",
    "rollForward": "latestFeature"
  },
  "test": {
    "runner": "Microsoft.Testing.Platform"
  }
}

The action will read the SDK version from there. This is often a good thing as it means you just need to set the version in one place rather than all through your workflow files.

Using GitHub Packages feeds

Assuming you've already configured your GitHub packages feed in your NuGet.Config file (and note the use of the newer packageSourceMapping block):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <packageSources>
        <add key="nuget" value="https://api.nuget.org/v3/index.json" />
        <add key="github" value="https://nuget.pkg.github.com/flcdrg/index.json" />
    </packageSources>

    <packageSourceMapping>
        <packageSource key="nuget">
            <package pattern="*" />
        </packageSource>
        <packageSource key="github">
            <package pattern="Verify.MongoDB" />
        </packageSource>
    </packageSourceMapping>
</configuration>

Then you can use the action to wire up authentication for the Packages feed with the source-url input parameter:

- uses: actions/setup-dotnet@v6
  with:
    source-url: https://nuget.pkg.github.com/flcdrg/index.json
  env:
    NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

Note that you must grant the GitHub token access to read packages!

permissions:
  contents: read
  packages: read

And you'd think that would be it. But there are some edge cases to be aware of.

Building from a subdirectory

The action defaults to looking in the root of the repository for global.json and NuGet.Config files. If your .NET source code resides in a subdirectory (often the case if you are using a monorepo approach), then make sure you tell the action where they are:

- uses: actions/setup-dotnet@v6
  with:
    global-json-file: globaljson-and-nugetconfig/global.json
    source-url: https://nuget.pkg.github.com/flcdrg/index.json
    config-file: globaljson-and-nugetconfig/nuget.config

If you forget to set global-json-file and/or config-file then it will only look in the root of the repository, and either load the wrong files or load nothing if those files don't exist at the root (as we saw earlier).

When the action/setup-dotnet action runs with source-url, it actually generates an additional temporary nuget.config file. You can see this in the workflow run output:

dotnet-auth: Finding any source references in /home/runner/work/using-setup-dotnet-action/using-setup-dotnet-action/nuget.config, writing a new temporary configuration file with credentials to /home/runner/work/using-setup-dotnet-action/nuget.config

That temporary file contains the authentication details for the feed.

But the restore fails:

Determining projects to restore...
/usr/share/dotnet/sdk/10.0.401/NuGet.targets(198,5): warning : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured. [/home/runner/work/using-setup-dotnet-action/using-setup-dotnet-action/globaljson-and-nugetconfig/tests/tests.csproj]
  Retrying 'FindPackagesByIdAsync' for source 'https://nuget.pkg.github.com/flcdrg/download/verify.mongodb/index.json'.

If you take a look at the contents of the temporary nuget.config file you might see the problem:

<configuration>
  <config>
    <add key="defaultPushSource" value="https://nuget.pkg.github.com/flcdrg/index.json"/>
  </config>
  <packageSources>
    <add key="Source" value="https://nuget.pkg.github.com/flcdrg/index.json"/>
  </packageSources>
  <packageSourceCredentials>
    <Source>
      <add key="Username" value="flcdrg"/>
      <add key="ClearTextPassword" value="***"/>
    </Source>
  </packageSourceCredentials>
</configuration>

The action knows the feed URL, but it has defaulted to using Source as the source name.

The issue here is that when dotnet restore runs, it finds the nuget.config file in the application directory and combines that with the temporary file.

The packageSourceMapping defines the github source as the only place to look for Verify.MongoDB package. But the temporary nuget.config file didn't use that name. So you end up that error.

The solution is to set the config-file input parameter so that the action can use the correct source name from your nuget.config file. With the names aligned, everything should work correctly.

Summary

If global.json is not in the root of the repository, use global-json-file
If NuGet.Config is not in the root of the repository, use config-file

SA Power Networks meter data

2026-09-23T13:30:00.000+09:30

For folks living in South Australia, electricity is distributed by SA Power Networks. As an electricity consumer, you don't normally deal with them directly. Instead you go through a retail company, of which there are a number to choose from.

SA Power Networks provide a service that allows you as a consumer to download your electricity data - Your Meter Data (you register for the service here).

Once you sign in you either download a PDF summary or a CSV file (in 'NEM12' format) with all your meter data, which includes both incoming and outgoing (like excess solar or battery) amounts.

I was keen to get that data so I could do some analysis of our power usage.

Having to repeatedly sign into that page and click on the various options just to download a CSV is a bit annoying. Ideally they'd provide a customer-facing API that I could call, but they don't. (I presume they do provide an API for the electricity retailers).

So I wrote a .NET library and an example console application that will do all that for you from the command line. Source available at https://github.com/flcdrg/sapowernetworks-meterdata-net.

You just supply your email address and password (that you signed up to the Your Meter Data site with) and it will grab the CSV for you:

dotnet run --project src/Gardiner.SaPowerNetworks.MeterData.Console -- --email your@email.com --password 'YOURPASSWORD' --file data.csv

If all goes well, will produce:

Logging in as your@email.com...
Logged in successfully.
Found 1 NMI(s):
  200012345678  Home  STREET SUBURBNAME 5000
Fetching data from 2026-08-18 to 2026-08-20...
Saved detailed NEM12 CSV to /Users/david/dev/sapowernetworks-meterdata-net/data.csv

The data looks something like this (truncated):

200,1234567899,E1B1,E1,E1,,LG1201234567,KWH,05,
300,20260619,0.00000000000000,0.00000000000000,0.00000000000000,0.00000000000000,0.00000000000000,
400,1,154,F19,,
400,155,288,A,,

And what about Home Assistant?

Hey, wouldn't this be a great data source for integrating with Home Assistant? You could use it to import your electricity meter data directly into HA. Well yes it would, but as nice as my console app is, it's written in .NET and Home Assistant integrations are written in Python.

So I used Copilot to create a new Home Assistant integration that imports the data each day automatically! It was able to use the .NET implementation as a reference and created equivalent Python code that would work with Home Assistant.

The source for the integration is at https://github.com/flcdrg/sapowernetworks-meterdata-ha. For the moment you will need to add that as a custom repository in Home Assistant HACS, but I've submitted it to be listed so that you will be able to just search for it in the HACS store.

The integration provides a control and a number of sensors:

But because all the data is historic, it doesn't provide a sensor with the current reading. Instead it publishes the historic data to Home Assistant's Recorder as statistics.

One way to view the data is via a Statistics graph card.

eg.

- type: statistics-graph
  entities:
    - sapowernetworks:9999999_import_e1
    - sapowernetworks:9999999_export_b1
  days_to_show: 7
  period: day
  chart_type: bar
  stat_types:
    - change
  logarithmic_scale: false

Which can give you a graph like this:

The blue 'import' is the electricity that came from the grid into the house. The yellow 'export' is excess solar power that was exported back to the grid.

The Saturday 19th and Sunday 20th were both beautiful sunny days here in Adelaide. The reason for the differences in the amounts on those days is that Saturday I was out driving most of the day, so we did not charge our car during the 11am-2pm free period that our current electricity plan offers. But Sunday once I got home from church the car was plugged in and recharged, so for that period while it was just as sunny, that solar power was going straight into our car instead of being exported.

Evnex E2 Plus EV Charger

2026-08-30T23:00:00.000+09:30

As part of the discussions with Adam from LAMM Solar and Electrical, I mentioned that we were getting an electric vehicle and I was interested in getting a home charger for faster charging. After clarifying that I wanted nothing to do with a certain T*sla brand, they recommended taking a look at an Evnex charger.

We only have single-phase power in our house (and no immediate plans to change that), so that narrowed it down to one of their E2 range that can provide up to 7.4 kilowatts:

Model	Connectivity	Solar	Cable	Price
E2 Flex	WiFi	-	5m	$AU799
E2 Core	WiFi	Y	5m	$AU1,099
E2 Plus	WiFi+4G	Y	8m	$AU1,399

The Flex is the base model. It doesn't have the 'Solar smart' feature that allows you to "schedule your charging to use only your excess solar power without drawing from the grid, giving you free kilometres from sunshine".

The Core sounded like it was the one, but I took note of Adam's advice to always get a longer cable than you think you'll need, as you won't regret it. Some chargers let you plug in your own cable, whereas unfortunately the Evnex ones don't. That pushed me to the 'Plus' as rather than 5m it comes with an 8m cable. It also supports a client/server model which I understand would be useful if we wanted to get a second charger installed and they could be managed together.

I was also interested to see what kind of ongoing support they had - I found there's an active support forum with prompt responses to queries, so that was also encouraging. They're designed and manufactured in New Zealand. If I can't buy Australian then New Zealand is the next best thing!

And so that's what we got. We ordered directly from Evnex and it arrived a couple of weeks later, just in time for LAMM to install when they refreshed our solar panels (there was a small reduction in costs for doing both together).

Oh and Adam was spot on with the longer cable. 8 metres was enough that I could run the cable along the ceiling of our carport over to near the charging port on our car. Keeping it off the ground and avoiding a tripping hazard. 5m would have been too short to do that.

Mobile app

Evnex provides a mobile app that you can view and manage your charger.

For comparison, here's the Kia app at the same time:

In the Evnex app you can view the details of the current charging session (and past ones too)

Like the solar inverter, the Evnex also uses a CT clamp to monitor actual electricity usage in your house. I'd say 'current usage' but that could be confusing🙂

You might just want to be able to charge any time, but for me I wanted to limit charging to when our electricity plan is cheapest. It is true that the Kia app provides simple scheduling for when to accept charging:

But the Evnex app has much more advanced controls:

The app has an advanced schedule setting, where you can configure when you want to allow charging and the costs that it would incur (from your electricity plan).

My current electricity plan has free power from 11am-2pm, so that's the main time I allow the car to charge. But on occasion I may want to allow charging overnight (when it isn't free but the cost is low) so I've created 1 hour intervals that I can selectively enable if needed.

You can add in different prices.

And for each time period you can assign one of three behaviours:

If we had a larger solar installation, then the Solar Smart feature could be useful too, to manage how much of your solar-generated electricity to allocate to EV charging.

Charging done (set to stop at 90%):

Home Assistant

Yes, there's a really good Home Assistant integration for the Evnex chargers. It provides two devices:

There's a number of controls and a bunch of sensors

You can use these to track usage and generate some nice graphs. I can imagine you could get quite clever with using Home Assistant to provide even finer control over how your car is charged. I could see something like monitoring the weather forecast to predict likely future solar generation to adjust how and when charging is offered. Not something I'm going to do now, but there's all kinds of possibilities.

Money back

Narelle discovered that our local council were offering a number of sustainability rebates, including for installing your own EV charger! We just had to supply a before and after photo of the installation and then a week or two later we got $200 back. Nice!

Replacing those panels

2026-08-27T22:00:00.000+09:30

So previously I described how our rooftop solar panels had a small failure that resulted in a reduced generating capacity. Now that we also have an EV, I was keen to get them back working as efficiently as possible. Ideally we'd be generating as much power as possible, not only to use in our house, but also to charge the new car.

Again, I contacted a few different installers, but ended back with LAMM Solar and Electrical again. There were a couple of constraints that they understood and worked with us on:

We're still receiving a generous government feed-in tariff for power we send back to the grid (paid in addition to any input rate on our electricity plan)
We don't have heaps of money to throw at a huge upgrade.

The first point is important. As I understand it, if you make any significant changes to your system, like increasing capacity or installing a battery, then the government tariff gets cancelled. So if at all possible, I'd prefer to keep that until it runs out in a couple of years.

Adam from LAMM patiently came up with a few different options to choose from that all kept any changes compliant. As long as the new system didn't exceed the capacity of the original then the feed-in tariff would continue.

One thing I hadn't considered was that solar panel technology has advanced a lot since our original panels were installed. The old system consisted of 24 x 190W panels.

The new system is 9 x 500W panels - and as it takes up a lot less roof space, it gives us physical room to expand in the future.

The alignment of the original panels was in two strings - with a longer one more north-aligned. It was great in Summer, but shaded by trees a lot more in Winter. The second string was at a slightly less north-facing angle, but not impacted by trees, so it could be relied on to keep generating through the whole year.

The replacement installation kept the second string. The plan was to put all 9 panels in that position, but on the day of installation we realised that they were just a bit too big to fit, so 3 panels were put on a different part of the roof. Those will pick up more afternoon sun and should also do well over Summer.

One slight annoyance was to discover that the government incentives for installing solar actually meant it was cheaper to put in a brand new inverter, rather than keep the perfectly fine one we had (it was only a few years old, having replaced the original inverter when that became faulty).

In a similar way, there wasn't much that could be done with the remaining old panels. If I had a farm shed or something similar I might have been able to repurpose them in some off-grid system, but I don't have any such thing. Even donating them to someone else would not be worth it, as I was informed that the cost of reinstallation would outweigh any savings compared to just putting in a new system. A shame but not much I could do about that.

Home Assistant monitoring

The new inverter is a GoodWe brand, and Home Assistant has support for that built in with the GoodWe Inverter integration.

I had read the documentation for that integration which mentioned you needed the Modbus TCP option enabled. That wasn't on by default. I want to give an extra thanks to the LAMM installers (Liam, Ethan and Ben), as they not only completed the installation but were happy to stay on a bit longer and adjust the inverter settings for me until the HA integration worked. That was much appreciated.

One advantage to getting a new inverter is it comes with a CT (Current Transformer) clamp. This allows it to monitor the electrical current in the mains connection. With that in place, you are able to see the actual amount of electricity that is being consumed by the house (in addition to any that is being generated by the solar panels).

I wish I'd started using Home Assistant much earlier, as I would have had a much longer history to compare with. As it is, here's a couple of months of the old system (and bear in mind it is Winter here in Adelaide, so any sunshine peaking through the clouds this time of year is a bonus!)

The new panels are already proving their worth. Whereas the old panels were lucky to get 6 kWh maximum, the new ones seem to have that as almost a daily minimum!

Replacing the panels was an unplanned expense, but the proceeds from selling the old Kia Sorento car ended up covering a good portion of the cost.

There's one other thing that I got LAMM Solar and Electrical to install on the day. I'll talk about that more in another post!

An electric vehicle

2026-08-20T20:30:00.000+09:30

We got an EV! I had been thinking for a while now that our next car should be an electric vehicle. Our good friend Jane had got one last year (and prior to that had a hybrid), and was a strong proponent making the switch, so it was definitely on my radar. We also attended a really informative community seminar early last year, where lots of EV owners brought their along cars for people to look at and ask questions. A few speakers gave really good presentations on what it's like owning an EV and the current state of the market. Given our driving patterns it just felt like the logical choice.

Our old car (a Kia Sorento 7 seater SUV) has had a good run, but it had recently ticked over 300,000 kms and while it was still going remarkably well (we did a road trip from Adelaide to Sydney earlier this year with it), it was likely going to get more expensive to keep on the road.

In hindsight I really should have done something about this last year - but I didn't count on a world-wide oil shortage, which then encouraged a lot of other people to start buying EVs too!

I also decided to take advantage of using a novated lease through work. There's some helpful government discounts that made this an option to consider. Some employers might only support a single lease provider, but SixPivot doesn't have any such limitation. I looked around at a number of leasing companies and also spoke to my work colleagues who were already leasing to hear their experiences. That's how I ended up choosing Fleetcare (If you're interested in using them, let me know and I'll share a referral code with you, and we both get a $250 gift card each if your lease is settled).

After a decent amount of research we settled on a Kia EV5. The base model (which we got) has a ~400km range and quite decent boot space compared to some other cars we looked at. It's a 5 seater SUV. Not quite as big as our old Sorento, but it does pass the "Cello" test. That's where you take a full-size Cello in its case and try and fit it into the car boot without having to put down one of the back seats. It's a lot more modern than our old car, but there's still a bit of "Kia" familiarity to it.

I'd also spent a bit of time looking at our past driving history and running costs to try and get a good idea of how much we could afford to budget for a new car. (The running costs also proved useful when filling out the lease documentation).

Some other brands I tried felt like the usable area of the windscreen was reduced quite a bit, especially around the rear-view mirror area - almost like driving with blinkers on. Maybe that's ok for shorter people, but as someone slightly taller, that was noticeable to me. A number of new cars seem to be adopting a US layout with indicator and wiper controls on the "wrong" side of the steering wheel. Not a deal breaker, but it was appreciated that the EV5 keeps with what I'm used to - wipers on the left, indicator on the right.

There's also a lot of variation across EV models as to how the gear stick is located. Not that you usually have more than just forward, park and reverse. Some have a dial in the centre console, some have what looks like a traditional gear stick, and some (like the EV5) have the gear stick as an extra "stalk" on the steering wheel.

A few bumps

About a week after we got the new car, I started noticing some weird error messages appearing on the dashboard display. They'd appear briefly and then go away, but a small warning icon would remain. They'd disappear when the car was turned off, but then another error would show up at some stage later. The strange thing was it wasn't always the same system that the error was referring to. They weren't predictable either.

Here's one that I did manage to get a photo of. The text would only appear for a few seconds, but the warning icon would stay in the bottom right of the display until you turned off the car.

I contacted our car sales guy to ask what the message meant, and he referred it to their service department. They asked for me to bring it in for a day. The result of that was they said they needed to book it in again for an extended period as they weren't sure what the problem was.

As a software developer, the worst kind of bug is one that you can't reproduce. Given the amount of software that runs inside a car these days, I was worried this might be one of those situations. But I was somewhat relieved to hear that when they plugged in their diagnostic tools into the car the technician could see a whole bunch of errors being logged. So it wasn't just me.

A couple of weeks later we took it back and it stayed in for a few days, during which they informed me they'd referred it up to Kia Australia. Finally they identified a fault with a high-voltage cable being too close to other wiring and causing interference and the 'phantom' warnings.

It was disappointing to be without our new car for about a week all up (at least we were given a loan car) but hopefully that problem is permanently resolved.

Bells and whistles

The new car is quite an upgrade from the old Sorento. Like most new cars on the market these days, it comes with a fully electronic dashboard, with navigation and all kinds of driving assistance features. Many of these like to go 'ding'! The steering wheel will rumble if the car thinks you're going out of your lane (or if it thinks you're about to change lanes and bump into a car).

As an avid Double-J Radio listener, I do appreciate having DAB digital radio built in.

Apple CarPlay is also nice, though maybe I'm "holding it wrong" as I've missed a few messages sometimes, that I thought I would get notified about. Also a bonus to be able to rely on Bluetooth and retire the old Aux cable. There can be a bit of competition now as to whose phone is the one to connect first and choose their music!

The built-in speed limit warnings are handy, except when they're not. As I understand it, the car can detect speed limit signs, but it presumably has some fallback mapping data that it defaults to. The quality of that data is variable. Some roads that have changed speed limits in the last year are obviously still using the old speed limits in its dataset. Others seem to have weird limits that make no sense - eg. there's a couple of roads where it insists the limit is "55km/h" - there is never a "55" speed limit. 40, 50 or 60, but not 55. I wish I knew how to submit updates or give feedback.

The EV5 does come with V2L (Vehicle to Load) with a standard Australian power point inside the boot. I haven't used it yet, but it's good to know the option is there. Handy if you're out on a picnic and want to boil a kettle, or if we ever have another massive storm with extended blackouts then we could use the car's battery to tide us over.

The car came with a standard charging cable (known by some as a 'granny' charger), that just plugs into a regular wall socket. My plan was to see how we went with that, knowing that it may take a while to recharge. In the short-term I could always take the car to a nearby fast-charging point, but if it became a regular problem then installing a higher-powered home charger would always an option.

Range anxiety?

The old car would average around 600km on a full tank. The new car has a nominal range of 400km, but I've found it can vary a bit depending on the kind of driving you're doing. Shorter drives to the shops or around town are easy. The longest we've done so far is a round trip to Port Elliott/Victor Harbor (~145km) which has been fine as well. I did notice that the faster highway driving does use up a bit more battery than just the normal suburban trips. But that's pretty normal for current generation EVs.

The more we use it, the more we get a feel for what it can do. I'm looking forward to taking on a longer drive. Yes, we'll need to plan out our stops for recharging, but given you really should stop every couple of hours for a break, I think that should coincide nicely.

And then there's the joy of driving past a petrol station and just ignoring the price of petrol. Probably the only downside to that is it means I need to be more intentional about stopping in occasionally just to keep the tyres up to pressure.

So yes, I'm happy we chose it.

Home Assistant

2026-08-16T22:00:00.000+09:30

My first exposure to Home Assistant (or 'HA' for short) was as an option for triggering a hallway light from a motion sensor for people who might want to go to the bathroom in the middle of the night. I know you can get self-contained sensor lights that do all that, but while I was researching those I found a few references to HA and I was intrigued.

I spun up a container on our Synology and had a play. Then I discovered that we already had a few devices in our house that it could talk to, like our UniFi network gear, the Synology itself and even our solar inverter!

I was curious about what else it could work with. I noticed that there were lots of integrations you could search for, including some power companies. But not the one I was using at the time - GloBird Energy. I did a general web search and discovered someone had built a custom integration for GloBird with HA - https://github.com/bolagnaise/globird-ha using something called "HACS". It turns out that HACS is the Home Assistant Community Store. Once you add HACS to your HA, you can add a whole bunch of additional 3rd-party integrations, plugins, themes and scripts. Lots of these are listed in the HACS store, but you can also add custom repositories that point to a Git repo (eg on GitHub) too.

Adding HACS to Home Assistant

After confirming I was running a recent version of Home Assistant, I followed the HACS instructions for installing into a Container.

As my container is running on my Synology NAS server, I needed to ssh to the Synology, then I could use the docker command to manage the container

Once you've done that then you can return to HA and proceed to setup HACS from within the UI.

Now you can search for HACS as a new integration

There's a few conditions to confirm before proceeding

Then a short wait for HACS to activate

And then you need to authorise HACS with GitHub

Give HACS a name (or accept the default)

And you're done

Adding GloBird integration from HACS to Home Assistant

Now that HACS is installed, there's a whole new list of integrations to choose from. But at the time GloBird wasn't in that list. That's ok. We can add a custom repository to let HACS know about it. Use the context menu.

Then enter the Git repository URL and select 'Integration' from the Type list.

Now that HACS is aware of the new repository, you can search the HACS store and GloBird will appear in the list.

Click on the context menu and choose Download

Once it is downloaded, HA lets you know that it needs to be restarted.

The first time I saw this, I switched back to the Synology Container Manager to restart the container. (I later realised that HA can actually restart itself through the UI and using Container Manager wasn't necessary!)

Now that the GloBird integration is installed, you can click on the Plus icon, and choose Add device

Then enter 'GloBird' and click on the matching item.

You'll be prompted to enter your credentials. For GloBird this is your account email and password.

You can accept the default device name or change it, and optionally assign the device to a 'room'. That makes more sense for physical devices in or around your house, but you can still do the same for 'utility' devices like an electricity provider.

And with that, the integration should be installed and configured. You can now see a page that shows all the current sensors and information from the device.

You might choose to add this to one or more dashboards, and also given in this case it relates to electricity, you could also add it to the Energy page.

Interestingly, when I first added the GloBird integration it provided information about our electricity account and usage, but GloBird also provide gas too (and we are using them as our gas provider). I contributed an update to the GloBird integration so that if you have a gas service with them, then you can also get that information as well.

Unlike electricity, gas requires a manual measurement - either by an official meter checker, or by me taking a photo of the meter and submitting it to GloBird. So the measurements are not "live" like a lot of HA devices, but always in the past. Because of that, the implementation I contributed sends the readings directly to HA's "recorder". They show up in HA as 'statistics', and you can visualise them.

Here's our recent monthly gas usage in HA.

I've since switched to a different electricity provider but I'm still using GloBird for gas. I'll be keeping an eye on their plans and there's always a chance I switch back.

Feel free to use this referral link if you want to check out GloBird for electricity or gas in Australia. You and I both get $50 credit (conditions apply)

Solar panel problems

2026-08-13T21:30:00.000+09:30

Back in March last year I discovered that the company that originally installed our solar panels back in 2011 had gone out of business. It was only in 2022 that they'd replaced a faulty inverter, so that was quite a surprise. I thought that they were a stayer, but like so many other solar companies, they didn't last.

When the inverter was installed, they configured it so that supposedly they would be monitoring it, and I was given "guest" access to view the daily statistics. I realised that obviously they wouldn't be monitoring it now they no longer existed. I got in touch with Fronius (the inverter manufacturer) and they were able to give me 'administrator' access. In doing that I updated the email it was using to send any notifications.

With my admin access, I now discovered that the firmware for the inverter and data sensor were both really outdated. Probably the same version it came with when it was installed. Something I assumed the installer would have been taking care of, but apparently not. Needless to say I fixed that.

And all was good until around November when I started getting some emails from the inverter saying "Code 475 Isolation Error". Not the most helpful of error messages! And we're heading into Summer when you want those panels working hard.

I contacted a few local solar companies - some just wanted to replace everything with a brand new, larger system, without even coming to take a look. LAMM Solar and Electrical were a bit more helpful.

One reason I tried them in the first place was that I remember seeing them at a local community fete. I was in favour of using a local company if possible.

One of their guys came out, discovered that one of my panels had actually cracked. It could have been a branch blown in the wind, or a bird dropping something on it.

As a short-term fix they disconnected the group of panels it was in. Our inverter was happier, though we now had slightly less generating capacity. Unfortunately, due to the age of the panel, it would be really unlikely to be able to replace it with another of the same capacity.

Our panels were back up and running, and if we ever needed someone to do more work on them then I now know a good company to deal with (and more about that soon).

Power Posts

2026-08-09T21:00:00.000+09:30

I've got a number of blog posts buzzing around in my head that I need to write up, all related to the topics of energy and electricity.

I think what's making it hard to get them out is they're all kind of interrelated. Yes, there is a timeline of events, but they cross over a bit, so figuring out which one to start with has me spinning my wheels a bit.

Hence this short post to at least get the ideas down as a list:

Solar panels (repairing vs replacing ours)
Electric vehicles (and the one we now have)
EV charging
Electricity smart meters
Choosing electricity plans
Home Assistant
Creating Home Assistant integrations

Ok. That's probably the posts I need to work on. Let's see which one comes together first 😀

Multiple .NET SDK versions and PowerShell on macOS with Homebrew

2026-07-19T13:30:00.000+09:30

As a long-time Chocolatey user on Windows, it's not surprising that Homebrew has become my go-to solution for installing software on macOS. There are a few quirks though, and the .NET SDK is one of them.

There's a dotnet 'Formula' (which installs the dotnet binary in /opt/homebrew/bin/dotnet)

There's also a dotnet-sdk 'Cask', but these are not compatible, and are known to conflict with each other.

(For my own benefit, a 'formula' is "Homebrew package definition that builds from upstream sources", and a 'cask' is a "Homebrew package definition that installs pre-compiled binaries built and signed by upstream")

PowerShell is also available via Homebrew, and interestingly it depends on the 'dotnet' formula, so if you also want to install PowerShell this way then that makes the decision for you.

But there's another problem. It's quite common to need to have multiple versions of .NET SDKs installed. Unfortunately the way that the default 'dotnet' formulae work is that while you can run brew install dotnet@8 as well, you only end up with one .NET SDK available (e.g. when you run dotnet --list-sdks).

Fortunately, some community members have built their own Homebrew packages that resolve this. I've used the one created by Junian Triajianto in https://github.com/junian/homebrew-dotnet

After adding his 'tap' (a Tap is Homebrew's term for a 3rd-party repository)

brew trust junian/homebrew-dotnet
brew tap junian/homebrew-dotnet

You can then install the SDKs. Note that you should use the full version number '8.0' or '10.0' otherwise Homebrew might install the above cask instead of Junian's

brew install dotnet-sdk@8.0
brew install dotnet-sdk@10.0

That installs dotnet in /usr/local/share/dotnet/dotnet

"But hey, what about PowerShell?" you ask!

Installing PowerShell via Homebrew will still install the dependent package 'dotnet'

brew install powershell

And by default Homebrew will have updated the PATH so that its binaries are found first. We need to fix that

I edited my ~/.zprofile and appended the following to it:

# Force the https://github.com/junian/homebrew-dotnet versions of .NET (not the one installed by PowerShell)
export DOTNET_ROOT="/usr/local/share/dotnet"

# Keep dotnet ahead of Homebrew paths.
typeset -U path
path=("$DOTNET_ROOT" "$HOME/.dotnet/tools" $path)
export PATH

The end result is that I get multiple .NET SDKs working:

dotnet --list-sdks
8.0.423 [/usr/local/share/dotnet/sdk]
10.0.302 [/usr/local/share/dotnet/sdk]

But PowerShell is still happy too:

In this scenario, I'd suggest that Chocolatey probably does a better job of curating packages so that you don't end up with multiple variations of packages for the same software, but it's good that Homebrew offers a way to resolve the issue.

The network switch that keeps switching more than it should

2026-06-16T20:30:00.000+09:30

A couple of months ago a suggestion came up at home about getting some kind of low-powered light in the hallway for people who might need to go to the bathroom in the middle of the night. Not an unreasonable request - maybe some LED strip lights would work? And then I wondered, how about adding a motion sensor? And then could you integrate it with some home automation of some kind? And that's how I ended up completely distracted looking at Home Assistant!

Installing it on our Synology NAS seemed the logical choice, and it was pretty straightforward, going down the Docker container route. I clicked around the UI and it looked interesting, but didn't go much further (and I must admit by that time I'd forgotten the original reason for heading down this rabbit hole).

Then a couple of weeks ago we got a new car (a Kia EV5) and it has an app that you can use to check current status and some limited remote control options. Given the need to charge it at home started me off on a new area of research for home charging devices, and also considering the current state of our home solar panels - whether to upgrade them, or at least figure out how to replace some that have had to be taken out of service due to impact damage.

That inspired me to go back and take another look at my Home Assistant instance, and see if I could add some 'integrations' with some of the existing networked devices we already have. It turns out our current model solar panel inverter (a Fronius) is supported, as well as the Ubiquiti UniFi networking gear I have installed. That is pretty cool.

And that is a very long way of getting to the point of this blog post - once I had these devices integrated, I noticed in Home Assistant's Activity page, that there were heaps of these entries being logged for my UniFi USW Flex Mini switch:

For some reason, either the Flex Mini switch itself, or my UniFi Cloud Gateway Ultra thinks that the uplink MAC address for the switch is changing every minute. That is really weird.

The physical arrangement of networking hardware in our home looks roughly like this:


graph TD;
    ISP --> GW
    GW[Cloud Gateway Ultra]
    click GW href "https://www.amazon.com.au/Ubiquiti-UniFi-Cloud-Gateway-Ultra/dp/B0D8PSW2BZ?&linkCode=ll2&tag=flcdrg07-22&linkId=39ad4320d21517a1048ccd7df111cbd5&ref_=as_li_ss_tl" "Cloud Gateway Ultra on Amazon" _blank
    GW --> TP

    TP[TP-Link Switch]
    TP --> PR

    LT(UAP AC Lite)
    TP --> LT

    PR(AC Pro)
    click PR href "https://www.amazon.com.au/UAP-AC-PRO-UBIQUITI-Ac1750-Access-Injector/dp/B07JDNS774?&linkCode=ll2&tag=flcdrg07-22&linkId=bfe6e1c092cbf6dbf88d14b28e295ed4&ref_=as_li_ss_tl" "AC Pro" _blank

    USW(USW Flex Mini)
    click USW href "https://www.amazon.com.au/Ubiquiti-Flex-Managed-Gigabit-Switch/dp/B08VRV9PWD?&linkCode=ll2&tag=flcdrg07-22&linkId=0dfeac74af4a36b6280c22ca74a2afad&ref_=as_li_ss_tl" "USW Flex Mini switch on Amazon" _blank
    TP --> USW

I had to do some hunting within the Cloud Gateway UI to figure out what the devices where that corresponded to the two MAC addresses.

One was indeed the gateway (which is what I would expect). The second, surprisingly turned out to be AC Pro wireless access point. That doesn't make a lot of sense - it's a wireless access point. It should not be acting as the upstream for a wired device.

It's funny though. Once you're paying attention to something, you often notice other things that have probably been there the whole time.

Switching to the Cloud Gateway UI and bringing up the Network page, I noticed something interesting.

At first it looked as I would have expected:

But then while on that page it updated and woah! That lines up with those logs!

Both the Flex Mini switch and the AC Pro access point use Power over Ethernet (PoE), and the TP-Link switch provides that on some of its ports so I had them both plugged into that.

The TP-Link is not a managed switch. It is essentially 'invisible' to other devices on the network (notice how it doesn't show up on those Gateway Network diagrams above), so I wonder if that may be relevant?

To test this theory, I changed the cables so that the Flex Mini is plugged directly into the Cloud Gateway. But as the gateway doesn't provide PoE I needed to power the Mini directly through its USB-C port.

Making that change, and now the Cloud Gateway's Network page reverts back to the expected layout and doesn't change. Home Assistant's Activity log also becomes a lot quieter.

That seems to have solved the problem. I'd really prefer to keep using PoE for the Flex Mini switch, but I suspect to do that in a reliable way might mean replacing the unmanaged TP-Link switch with a newer managed one - something like the UniFi USW Lite 8 or USW Ultra. Except it does seem the price jumps quite a bit when you go from 5 ports to 8. Maybe I'll stick with the USB-C power option for now.

Amazon affiliate links