#homeautomation — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #homeautomation, aggregated by home.social.
-
📢 New #updates · 1 Oct #15
· Wekan v12.14 — Translation test now checks Trello link by parsed host
· convex precompiled-2026-10-01-689f8f3 — Fixed URLSearchParams iterator handling
· fluxer [email protected] — Improved user authentication flowMore self-hosted updates → https://selfhost.directory
-
📢 New #updates · 1 Oct #15
· Wekan v12.14 — Translation test now checks Trello link by parsed host
· convex precompiled-2026-10-01-689f8f3 — Fixed URLSearchParams iterator handling
· fluxer [email protected] — Improved user authentication flowMore self-hosted updates → https://selfhost.directory
-
📢 New #updates · 1 Oct #15
· Wekan v12.14 — Translation test now checks Trello link by parsed host
· convex precompiled-2026-10-01-689f8f3 — Fixed URLSearchParams iterator handling
· fluxer [email protected] — Improved user authentication flowMore self-hosted updates → https://selfhost.directory
-
📢 New #updates · 30 Sept #14
· fluxer [email protected]
· lightdash 2.397.0 — Brand refresh and bug fixes
· lemonade candidate-v2026.41.0 — New models and GPU naming updatesCheck out more on https://selfhost.directory
-
📢 New #updates · 30 Sept #14
· fluxer [email protected]
· lightdash 2.397.0 — Brand refresh and bug fixes
· lemonade candidate-v2026.41.0 — New models and GPU naming updatesCheck out more on https://selfhost.directory
-
📢 New #updates · 30 Sept #14
· fluxer [email protected]
· lightdash 2.397.0 — Brand refresh and bug fixes
· lemonade candidate-v2026.41.0 — New models and GPU naming updatesCheck out more on https://selfhost.directory
-
📢 New #updates · 30 Sept #14
· fluxer [email protected]
· lightdash 2.397.0 — Brand refresh and bug fixes
· lemonade candidate-v2026.41.0 — New models and GPU naming updatesCheck out more on https://selfhost.directory
-
📢 New #updates · 30 Sept #14
· fluxer [email protected]
· lightdash 2.397.0 — Brand refresh and bug fixes
· lemonade candidate-v2026.41.0 — New models and GPU naming updatesCheck out more on https://selfhost.directory
-
📢 New #updates · 30 Sept #13.2
· shelf.nu [email protected] — Asset index now shows models and improved scan tracking
Full changelogs → https://selfhost.directory
-
📢 New #updates · 30 Sept #13.2
· shelf.nu [email protected] — Asset index now shows models and improved scan tracking
Full changelogs → https://selfhost.directory
-
📢 New #updates · 30 Sept #13.2
· shelf.nu [email protected] — Asset index now shows models and improved scan tracking
Full changelogs → https://selfhost.directory
-
RE: https://social.heise.de/@heiseonlineenglish/117353400433226336
Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.
-
RE: https://social.heise.de/@heiseonlineenglish/117353400433226336
Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.
-
RE: https://social.heise.de/@heiseonlineenglish/117353400433226336
Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.
-
RE: https://social.heise.de/@heiseonlineenglish/117353400433226336
Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.
-
Shelly to be acquired by Schneider Electric… be interesting to see what changes that brings over time. Shelly has pretty good integration options at the moment including a well featured #HomeAssistant integration.
https://matterdevices.io/news/schneider-electric-to-acquire-shelly-group/
-
Shelly to be acquired by Schneider Electric… be interesting to see what changes that brings over time. Shelly has pretty good integration options at the moment including a well featured #HomeAssistant integration.
https://matterdevices.io/news/schneider-electric-to-acquire-shelly-group/
-
Shelly to be acquired by Schneider Electric… be interesting to see what changes that brings over time. Shelly has pretty good integration options at the moment including a well featured #HomeAssistant integration.
https://matterdevices.io/news/schneider-electric-to-acquire-shelly-group/
-
Shelly to be acquired by Schneider Electric… be interesting to see what changes that brings over time. Shelly has pretty good integration options at the moment including a well featured #HomeAssistant integration.
https://matterdevices.io/news/schneider-electric-to-acquire-shelly-group/
-
I'm setting up a bit of a convoluted alarm system using Home Assistant and ESPHome.
The physical alarm system uses EV1527 codes (20-bit "unique” device code, 4-bit command data, transmitted on 433Mhz), but I want to use my existing Zigbee contact/motion sensors.
So: all my sensors get labeled ”Alarmsystem" in Home Assistant. I have an automation that triggers when any of the sensors with that label change state. The automation calculates a unique(-enough) 20-bit device code based on the Home Assistant device id for the sensor, and tacks on the command data ("open" or "closed”). This yields a 24-bit code.
This code is then passed to an ESP32 running ESPHome, which transmits the code using the "RC Switch" protocol.
I'll learn all the codes into the alarm system as separate sensors, and done!
(I don't want to build an alarm system based entirely on HA, for reasons)
-
I'm setting up a bit of a convoluted alarm system using Home Assistant and ESPHome.
The physical alarm system uses EV1527 codes (20-bit "unique” device code, 4-bit command data, transmitted on 433Mhz), but I want to use my existing Zigbee contact/motion sensors.
So: all my sensors get labeled ”Alarmsystem" in Home Assistant. I have an automation that triggers when any of the sensors with that label change state. The automation calculates a unique(-enough) 20-bit device code based on the Home Assistant device id for the sensor, and tacks on the command data ("open" or "closed”). This yields a 24-bit code.
This code is then passed to an ESP32 running ESPHome, which transmits the code using the "RC Switch" protocol.
I'll learn all the codes into the alarm system as separate sensors, and done!
(I don't want to build an alarm system based entirely on HA, for reasons)
-
I'm setting up a bit of a convoluted alarm system using Home Assistant and ESPHome.
The physical alarm system uses EV1527 codes (20-bit "unique” device code, 4-bit command data, transmitted on 433Mhz), but I want to use my existing Zigbee contact/motion sensors.
So: all my sensors get labeled ”Alarmsystem" in Home Assistant. I have an automation that triggers when any of the sensors with that label change state. The automation calculates a unique(-enough) 20-bit device code based on the Home Assistant device id for the sensor, and tacks on the command data ("open" or "closed”). This yields a 24-bit code.
This code is then passed to an ESP32 running ESPHome, which transmits the code using the "RC Switch" protocol.
I'll learn all the codes into the alarm system as separate sensors, and done!
(I don't want to build an alarm system based entirely on HA, for reasons)
-
I'm setting up a bit of a convoluted alarm system using Home Assistant and ESPHome.
The physical alarm system uses EV1527 codes (20-bit "unique” device code, 4-bit command data, transmitted on 433Mhz), but I want to use my existing Zigbee contact/motion sensors.
So: all my sensors get labeled ”Alarmsystem" in Home Assistant. I have an automation that triggers when any of the sensors with that label change state. The automation calculates a unique(-enough) 20-bit device code based on the Home Assistant device id for the sensor, and tacks on the command data ("open" or "closed”). This yields a 24-bit code.
This code is then passed to an ESP32 running ESPHome, which transmits the code using the "RC Switch" protocol.
I'll learn all the codes into the alarm system as separate sensors, and done!
(I don't want to build an alarm system based entirely on HA, for reasons)
