home.social

#homeautomation — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #homeautomation, aggregated by home.social.

  1. 📢 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 updates

    Check out more on selfhost.directory

    #homeautomation #ai #api #automation

  2. 📢 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 updates

    Check out more on selfhost.directory

    #homeautomation #ai #api #automation

  3. 📢 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 updates

    Check out more on selfhost.directory

    #homeautomation #ai #api #automation

  4. 📢 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 updates

    Check out more on selfhost.directory

    #homeautomation #ai #api #automation

  5. 📢 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 updates

    Check out more on selfhost.directory

    #homeautomation #ai #api #automation

  6. RE: social.heise.de/@heiseonlineen

    Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.

  7. RE: social.heise.de/@heiseonlineen

    Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.

    #Google #SmartHome #homeautomation #homeassistant

  8. RE: social.heise.de/@heiseonlineen

    Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.

    #Google #SmartHome #homeautomation #homeassistant

  9. RE: social.heise.de/@heiseonlineen

    Google already forced my Google Home speakers onto Gemini. Can’t wait until I can replace them with Home Assistant voice satellites.

    #Google #SmartHome #homeautomation #homeassistant

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

    matterdevices.io/news/schneide

    #HomeAutomation

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

    matterdevices.io/news/schneide

    #HomeAutomation

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

    matterdevices.io/news/schneide

    #HomeAutomation

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

    matterdevices.io/news/schneide

    #HomeAutomation

  14. 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)

    #homeautomation #homeassistant #esphome #iot

  15. 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)

    #homeautomation #homeassistant #esphome #iot

  16. 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)

    #homeautomation #homeassistant #esphome #iot

  17. 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)

    #homeautomation #homeassistant #esphome #iot