No description
Find a file
renovate_bot aeda0df445
All checks were successful
CI / build-update-json (push) Has been skipped
CI / build (arm64, linux) (push) Successful in 1m19s
CI / build (amd64, darwin) (push) Successful in 2m16s
CI / build (amd64, linux) (push) Successful in 1m46s
CI / build (arm64, darwin) (push) Successful in 1m41s
CI / build (arm64, windows) (push) Successful in 1m38s
CI / build (amd64, windows) (push) Successful in 2m45s
CI / upload-to-s3 (push) Has been skipped
Update https://code.forgejo.org/forgejo/upload-artifact action to v5
2026-11-18 13:22:35 +00:00
.forgejo/workflows Update https://code.forgejo.org/forgejo/upload-artifact action to v5 2026-11-18 13:22:35 +00:00
api default to prod gin mode 2025-11-23 20:40:19 +01:00
configuration allow configuring keyword 2025-11-14 14:35:38 +01:00
docs add api docs 2025-11-10 19:06:04 +01:00
update debug log upodater url 2025-11-10 19:25:39 +01:00
.gitignore ignore build artifacts 2025-11-10 19:22:52 +01:00
config.yaml.example add example config 2025-11-23 20:26:07 +01:00
go.mod Update module go.yaml.in/yaml/v3 to v4 2026-11-12 20:11:13 +00:00
go.sum Update module go.yaml.in/yaml/v3 to v4 2026-11-07 23:49:39 +00:00
main.go add ci pipeline and update management 2025-11-10 19:14:33 +01:00
Readme.md update update URL 2026-03-09 19:54:49 +01:00
renovate.json add renovate config 2025-11-10 19:45:50 +01:00
version.go update update URL 2026-03-09 19:54:49 +01:00

Shelly Smoke to Alamos forwarder

This tool was developed to use the relativly cheap Shelly Plus Smoke detectors in combination with Alamos as alarming software. The smoke detector will trigger a webhook from the API server, which then will forward the alarm to Alamos.

Installation

  1. Download the latest version here: https://s3.jonasled.de/shelly-smoke-alamos/shelly-smoke-alamos-windows-amd64.exe
  2. Dowload the Non-Sucking Service Manager: https://nssm.cc/
  3. Register a new Windows Service for starting the forwarder in the background by calling nssm install shelly-smoke-alamos using powershell.
  4. Configure the service like in the screenshot described. You can change the folder to any folder you like to use: Screenshot from NSSM service editor
  5. Go into the Alamos FE2 webui and create a external connector: Screenshot from Alamos FE2 Screenshot from Alamos FE2
  6. Download the example config file from this repo ( config.yaml.example ) and place it as config.yaml in the same folder as the shelly-smoke-alamos-windows-amd64.exe file.
  7. Configure your alamos connection in the config file. The secret must be the same as the valid sender option on the FE2 configuration.
  8. Create your smoke detectors. As name you can use anything to identify the smoke detector in your alarm later. For the id use a random character string and for target select your alamos target configuration.
  9. Start the shelly-smoke-alamos windows service.
  10. Allow connections from your smoke detectors to Port 8080 in you windows firewall.
  11. Configure your smoke detector to connect to your WiFi and add two automations:
    1. When smoke detected trigger this URL: http://<ip of your server>:8080/api/webhook/<smokedetector id>
    2. When the test button is pressed, trigger this URL: http://<ip of your server>:8080/api/webhook/<smokedetector id>/test. When you're missing the test function in the automation, your smoke detector is running a older firmware release and you first have to update the sensor.