homebridge-gsh VS core

You don’t need to use HomeKit for this to work, but you will need https://github.com/oznu/homebridge-gsh. (Caveat: I haven’t tried this myself since I use HomeKit and Alexa devices.)

I have no idea about the Google Home Mini, but I managed to add my Nest Mini to HomeKit using the Enomek. You can try it as it simplifies the whole homebridge process. Also, Look for the homebridge-gsh plugin on github.

Since you’re a homebridge user, check out https://github.com/oznu/homebridge-gsh then you can set up google home on her pixel. Most smart home stuff already works with google home

I currently use homebridge-gsh as a way to have my Google Home speakers control my devices strictly through Homebridge. Is there a similar plugin that I could use the same way with HA where commands from Google Home interact with HA vs with each device's own cloud provider?

Maybe homebridge with this plugin? https://github.com/oznu/homebridge-gsh

Try this to add all the homekit devices in google home.

Sorry I thought I answered you, but I guess it never went through... but instead of the Alexa plugin, for Google Home you can use this plugin that does the same thing. I have tested this as well.

Answering myself once again.. I found the gsh (Google Smart Home) plugin for homebridge. Unfortunately, it requires running HB without authentication: https://github.com/oznu/homebridge-gsh

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