Windows - Home Assistant Integration
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
sleevezipper b27d26a287
have more control over application versioning
4 years ago
.vs have more control over application versioning 4 years ago
.vscode also rename project in launch tasks 4 years ago
Communication refactor so we don't need appsettings.json, further configure clickonce 4 years ago
Data refactor so we don't need appsettings.json, further configure clickonce 4 years ago
Domain add logging and running as a service 4 years ago
Properties have more control over application versioning 4 years ago
.gitignore add logging and running as a service 4 years ago
LICENSE add license 4 years ago
Program.cs have more control over application versioning 4 years ago
README.md have more control over application versioning 4 years ago
Worker.cs refactor so we don't need appsettings.json, further configure clickonce 4 years ago
appsettings.Development.json add logging and running as a service 4 years ago
appsettings.json add logging and running as a service 4 years ago
hass-workstation-service.csproj have more control over application versioning 4 years ago
hass-workstation-service.csproj.user implement ClickOnce installation method and use registry to autostart 4 years ago
hass-workstation-service.sln implement ClickOnce installation method and use registry to autostart 4 years ago
hass-workstation-service_TemporaryKey.pfx implement ClickOnce installation method and use registry to autostart 4 years ago

README.md

HASS Workstation Service

This goal of this project is to provide useful sensors and services from your workstation to Home Assistant. It accomplishes this goal by:

  • Running in the background as a service
  • Being lightweight so you'll never notice it
  • Using well defined standards
  • Being local when you want it to, only communicating through your own MQTT broker

It will try to futher accomplish this goal in the future by:

  • Being platform independent
  • Being easy to configure
  • Using secure communication

Deployments