openhab-distro VS core

The GitHub update, including changes, here: https://github.com/openhab/openhab-distro/releases/tag/4.1.0.M1

I understand the feeling :) I’ve tried home assistant multiple times, and I always come back to openHAB. Maybe it’s me getting old, don’t know. But like you, I dislike updating my server and having broken dependencies. That happens quite frequently with HA, where every once in a while we get people over on openHAB community forum asking for advice ( e.g. https://community.openhab.org/t/migration-from-home-assistant-to-openhab-and-installation-type/140110 ) because they too just want a stable service that they can rely on. I won’t say that there’s never been broken dependencies - not at all, in a previous update they changed the way the API works and the node red node broke - but here the difference is that you can go to their GitHub and review the changes (https://github.com/openhab/openhab-distro/releases/tag/3.4.0.M3) and they are impeccable in documentation. Check out the google integration documentation to understand what I mean:

OpenHab : https://github.com/openhab/openhab-distro/pull/1343

openHAB Beta 2.18.2-beta: Vendor and technology agnostic open source home automation

Look into OpenHab.

OpenHAB would work well as well. Definitely agree on zwave or maybe zigbee devices for low power usage.

I use this https://www.home-assistant.io/ or another https://www.openhab.org/ and a cheap raspberry pi zero. It can run 24/7. And maybe some "hacking" on your devices if not supported aka listed.

🌟.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

Microsoft does not adapt their new products to operating systems (https://github.com/dotnet/core/issues/7556) which have reached End-of-Support status. Therefore, the game's system requirements have changed:

Thanks to .Net core