Mycodo VS core

Check out this environmental monitoring and control software I’m using on a raspberry pi with my grows, it’s amazing: Mycodo

If you don't feel like rolling your own, Mycodo is great.

Outside of light, nitrogen (N), phosphorus (P), and potassium (K), or NPK for short

Finding the right combination of these elements is what hydroponics farmers do everyday, pushing the limits of their crop for maximum quality/yield. We are starting to see a big shift in hydroponic fertilizers from liquid to powder since nobody wants to pay for shipping water.

I highly recommend https://github.com/kizniche/Mycodo for anyone doing anything in hydroponics.

Aside from that, might look at what this guy did https://kylegabriel.com/projects/2020/06/automated-hydroponic-system-build.html with the more generic open source Mycodo platform: https://github.com/kizniche/Mycodo

This guys level is what I aspire to: https://github.com/kizniche/Mycodo His video was source for a lot of inspiration.

For people that don’t mind a bit of DIY there’s a great Open-source project for the raspberry pi named Mycodo that can be upscaled and easily customized towards personal needs as well as supporting many sensors and devices out of the box.

yes, Mycodo is a candidate

You could likely use mycodo environmental sensing and control software: https://github.com/kizniche/Mycodo You will probably want to use relays to control a heater and humidifier. The kind of relay will depend on the heater and humidifier. Do you have links to datasheets?

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }

The tooling is not entirely open or freely available.

If you, for e.g., want to debug you have to use MS tooling.[0] You also can't use VSCodium because only the MS built/distributed version of VSCode contains the necessary proprietary binary blobs necessary to debug C# (which also means you're forced to using the aggressive telemetry and other data collection built into the non-open source distribution of VSCode).

They've also taken steps to lock down the LSP support for C#, which once again requires that you use a MS sanctioned code editor to write C#. [1]

I really enjoy writing C# and think dotnet is a great platform to develop for, but the barriers preventing me from building more projects on it is that I don't want to be forced to use VSCode or Visual Studio.

[0] https://github.com/dotnet/core/issues/505

Thanks to .Net core

Similarly, here is the API diff between .NET 8.0 Preview 1 and .NET 8 Preview 2

Also .NET 7 dropped support for client Windows OSes older than Windows 10 v1607 ( ref: https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md ) so if Windows 7 support is needed, the newest they could go is .NET 6.0 but that mandates SP1 w/ ESU.

If you go that route, it's completely useless to support both. Just support the latest, it will work for everyone. Win7 support will be dropped in net7 so you are still good with net6. But you never said win7 support is required either, I think in this day and age it's acceptable to drop it. If what worries you is having to install the net6 runtimes dependencies, just bundle them with your app as self contained.

You can read what's coming in this case https://github.com/dotnet/core/issues/8133