Open source home automation that puts local control and privacy first.

Overview

Home Assistant Chat Status

Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server.

Check out home-assistant.io for a demo, installation instructions, tutorials and documentation.

screenshot-states

Featured integrations

screenshot-components

The system is built using a modular approach so support for other devices or actions can be implemented easily. See also the section on architecture and the section on creating your own components.

If you run into issues while using Home Assistant or during development of a component, check the Home Assistant help section of our website for further help and information.

Comments
  • No gpio to reset/unexpected event/command timeout/failed to disable LE scan - Errors

    No gpio to reset/unexpected event/command timeout/failed to disable LE scan - Errors

    The problem

    Hi I have a ZEXMTE BT-505 (RTL8761BU) which is a "known working adaptor"

    But in my HA server I get this error over and over even though everything works on the front end: Screenshot 2023-01-03 at 9 06 07 pm

    is there any way to stop this from happening?

    Please let me know if you need any more information.

    Thank you in advance!

    What version of Home Assistant Core has the issue?

    2022.12.9

    What was the last working version of Home Assistant Core?

    None.

    What type of installation are you running?

    Home Assistant OS

    Integration causing the issue

    Bluetooth

    Link to integration documentation on our website

    https://www.home-assistant.io/integrations/bluetooth/

    Diagnostics information

    config_entry-bluetooth-5f4dd3d4ad582485d0598937703bf0b1.json.txt

    Example YAML snippet

    N/A
    

    Anything in the logs that might be useful for us?

    No errors or problems in logs.
    

    Additional information

    No response

    integration: bluetooth 
    opened by oneseventhree 1
  • Update stale strings in repairs tests

    Update stale strings in repairs tests

    Breaking change

    Proposed change

    Type of change

    • [ ] Dependency upgrade
    • [ ] Bugfix (non-breaking change which fixes an issue)
    • [ ] New integration (thank you!)
    • [ ] New feature (which adds functionality to an existing integration)
    • [ ] Deprecation (breaking change to happen in the future)
    • [ ] Breaking change (fix/feature causing existing functionality to break)
    • [ ] Code quality improvements to existing code or addition of tests

    Additional information

    • This PR fixes or closes issue: fixes #
    • This PR is related to issue:
    • Link to documentation pull request:

    Checklist

    • [ ] The code change is tested and works locally.
    • [ ] Local tests pass. Your PR cannot be merged unless tests pass
    • [ ] There is no commented out code in this PR.
    • [ ] I have followed the development checklist
    • [ ] The code has been formatted using Black (black --fast homeassistant tests)
    • [ ] Tests have been added to verify that the new code works.

    If user exposed functionality or configuration variables are added/changed:

    If the code communicates with devices, web services, or third-party tools:

    • [ ] The manifest file has all fields filled out correctly.
      Updated and included derived files by running: python3 -m script.hassfest.
    • [ ] New or updated dependencies have been added to requirements_all.txt.
      Updated by running python3 -m script.gen_requirements_all.
    • [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
    • [ ] Untested files have been added to .coveragerc.

    To help with the load of incoming pull requests:

    cla-signed small-pr has-tests integration: repairs Quality Scale: internal 
    opened by emontnemery 1
  • Clarify SensorDeviceClass.PRECIPITATION docstring

    Clarify SensorDeviceClass.PRECIPITATION docstring

    Breaking change

    Proposed change

    Type of change

    • [ ] Dependency upgrade
    • [ ] Bugfix (non-breaking change which fixes an issue)
    • [ ] New integration (thank you!)
    • [ ] New feature (which adds functionality to an existing integration)
    • [ ] Deprecation (breaking change to happen in the future)
    • [ ] Breaking change (fix/feature causing existing functionality to break)
    • [ ] Code quality improvements to existing code or addition of tests

    Additional information

    • This PR fixes or closes issue: fixes #
    • This PR is related to issue:
    • Link to documentation pull request:

    Checklist

    • [ ] The code change is tested and works locally.
    • [ ] Local tests pass. Your PR cannot be merged unless tests pass
    • [ ] There is no commented out code in this PR.
    • [ ] I have followed the development checklist
    • [ ] The code has been formatted using Black (black --fast homeassistant tests)
    • [ ] Tests have been added to verify that the new code works.

    If user exposed functionality or configuration variables are added/changed:

    If the code communicates with devices, web services, or third-party tools:

    • [ ] The manifest file has all fields filled out correctly.
      Updated and included derived files by running: python3 -m script.hassfest.
    • [ ] New or updated dependencies have been added to requirements_all.txt.
      Updated by running python3 -m script.gen_requirements_all.
    • [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
    • [ ] Untested files have been added to .coveragerc.

    To help with the load of incoming pull requests:

    core cla-signed small-pr integration: sensor Quality Scale: internal 
    opened by emontnemery 1
  • Shelly DeviceConnectionError after HA restart

    Shelly DeviceConnectionError after HA restart

    The problem

    After restarting HA some Shelly devices appear sporadically unconnected. All devices types are affected, be it Shelly1 oder 2.5. What helps is to force them to reconnect (yes, they are already connected and can be pinged via terminal) them to my wifi (in my Unifi controller add-on) and reload the integration afterwards. As this affects all device types and after every particular restart of HA different devices appear unconnected I am putting it down to an issue with the integration. I cannot say exactly when the issue occurred first but what I am sure about is that it started during the 2022.12 cycle.

    Logger: homeassistant.components.websocket_api.http.connection
    Source: components/shelly/entity.py:349 
    Integration: Home Assistant WebSocket API (documentation, issues) 
    First occurred: 08:25:54 (11 occurrences) 
    Last logged: 09:02:11
    
    [547177164672] Setting state for entity Rollo Wohnzimmer failed, state: {'go': 'open'}, error: DeviceConnectionError()
    [547177164672] Setting state for entity Rollo Küche failed, state: {'go': 'to_pos', 'roller_pos': 100}, error: DeviceConnectionError()
    [547177164672] Setting state for entity Rollo Schlafzimmer failed, state: {'go': 'open'}, error: DeviceConnectionError()
    [547177164672] Setting state for entity Rollo Bad failed, state: {'go': 'open'}, error: DeviceConnectionError()
    [547559197904] Setting state for entity Lenes Rollo failed, state: {'go': 'open'}, error: DeviceConnectionError()
    Traceback (most recent call last):
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
        return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
      File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
        raise exceptions[0]
      File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
        sock = await self._connect_sock(
      File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
        await self.sock_connect(sock, address)
      File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
        return await fut
      File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in _sock_connect_cb
        raise OSError(err, f'Connect call failed {address}')
    OSError: [Errno 113] Connect call failed ('192.168.0.84', 80)
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/usr/local/lib/python3.10/site-packages/aioshelly/block_device.py", line 259, in http_request
        resp: ClientResponse = await self.aiohttp_session.request(
      File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 535, in _request
        conn = await self._connector.connect(
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 542, in connect
        proto = await self._create_connection(req, traces, timeout)
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 907, in _create_connection
        _, proto = await self._create_direct_connection(req, traces, timeout)
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
        raise last_exc
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
        transp, proto = await self._wrap_create_connection(
      File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
        raise client_error(req.connection_key, exc) from exc
    aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.0.84:80 ssl:default [Connect call failed ('192.168.0.84', 80)]
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/usr/src/homeassistant/homeassistant/components/shelly/entity.py", line 346, in set_state
        return await self.block.set_state(**kwargs)
      File "/usr/local/lib/python3.10/site-packages/aioshelly/block_device.py", line 481, in set_state
        return await self.device.http_request(
      File "/usr/local/lib/python3.10/site-packages/aioshelly/block_device.py", line 276, in http_request
        raise DeviceConnectionError from err
    aioshelly.exceptions.DeviceConnectionError
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
        await hass.services.async_call(
      File "/usr/src/homeassistant/homeassistant/core.py", line 1745, in async_call
        task.result()
      File "/usr/src/homeassistant/homeassistant/core.py", line 1782, in _execute_service
        await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
      File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
        await service.entity_service_call(
      File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
        future.result()  # pop exception if have
      File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 943, in async_request_call
        await coro
      File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
        await result
      File "/usr/src/homeassistant/homeassistant/components/shelly/cover.py", line 123, in async_open_cover
        self.control_result = await self.set_state(go="open")
      File "/usr/src/homeassistant/homeassistant/components/shelly/entity.py", line 349, in set_state
        raise HomeAssistantError(
    homeassistant.exceptions.HomeAssistantError: Setting state for entity Rollo Küche failed, state: {'go': 'open'}, error: DeviceConnectionError()
    

    What version of Home Assistant Core has the issue?

    2022.12.8

    What was the last working version of Home Assistant Core?

    No response

    What type of installation are you running?

    Home Assistant OS

    Integration causing the issue

    Shelly

    Link to integration documentation on our website

    https://www.home-assistant.io/integrations/shelly/

    Diagnostics information

    No response

    Example YAML snippet

    No response

    Anything in the logs that might be useful for us?

    No response

    Additional information

    No response

    integration: shelly 
    opened by Zahnweh 2
  • Tibber integration cannot connect

    Tibber integration cannot connect

    The problem

    Since approx mid-November 2022 I havent had connection with tibber. The integration doesnt get data from Tibber. I have tried the API explorer and that works ok.

    I am on the latest core and HA OS.

    I have tried reinstalling the integration several times. Last time today after upgrading to 2022.12.9.

    What version of Home Assistant Core has the issue?

    2022.12.9

    What was the last working version of Home Assistant Core?

    approx 2022.10.1

    What type of installation are you running?

    Home Assistant OS

    Integration causing the issue

    Tibber

    Link to integration documentation on our website

    https://github.com/home-assistant/core/tree/dev/homeassistant/components/tibber

    Diagnostics information

    No response

    Example YAML snippet

    No response

    Anything in the logs that might be useful for us?

    This is from the debug log
    
    2023-01-03 08:55:04.378 ERROR (MainThread) [tibber] Error connecting to Tibber, resp code: 500
    

    Additional information

    No response

    opened by 02dag 0
  • Smartthings integration not creating

    Smartthings integration not creating "climate" for multichannel devices

    The problem

    After the migration to smartthings edge drivers, the new drivers for Heatit devices do not "relay" the child device capabilitiess like some of the groovy drivers did in the past.

    Smarttings integration no longer recognises these devices as climate devices, and doesnt return a temperature measurement:

    image

    It is unclear to me whether the driver is obliged to relay the child devices or whether the smartthings integration would be able to retrieve these

    What version of Home Assistant Core has the issue?

    2022.12.1

    What was the last working version of Home Assistant Core?

    No response

    What type of installation are you running?

    Home Assistant OS

    Integration causing the issue

    smartthings

    Link to integration documentation on our website

    No response

    Diagnostics information

    No response

    Example YAML snippet

    No response

    Anything in the logs that might be useful for us?

    No response

    Additional information

    https://community.smartthings.com/t/including-multichannel-device-always-uses-dth-not-edge-driver/247530/30

    opened by jeremycook61 0
Releases(2023.1.0b5)
Owner
Home Assistant
Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts.
Home Assistant
Implemented robot inverse kinematics.

robot_inverse_kinematics Project setup # put the package in the workspace $ cd ~/catkin_ws/ $ catkin_make $ source devel/setup.bash Description In thi

Jianming Han 2 Dec 08, 2022
A low power 1U Raspberry Pi cluster server for inexpensive colocation.

Raspberry Pi 1U Server There are server colocation providers that allow hosting a 1U server for as low as $30/month, but there's a catch: There are re

Paul Brown 627 Dec 31, 2022
Point Density-Aware Voxels for LiDAR 3D Object Detection (CVPR 2022)

PDV PDV is LiDAR 3D object detection method. This repository is based off [OpenPCDet]. Point Density-Aware Voxels for LiDAR 3D Object Detection Jordan

Toronto Robotics and AI Laboratory 114 Dec 21, 2022
Self Driving Car Prototype

Package Delivery Rover 🚀 This project is a prototype of Self Driving Car. It's based on embedded systems, to meet the current requirement of delivery

Abhishek Pawar 1 Oct 31, 2021
A set of postprocessing scripts and macro to accelerate the gyroid infill print speed with Klipper

A set of postprocessing scripts and macro to accelerate the gyroid infill print speed with Klipper

Jérôme W. 75 Jan 07, 2023
Ansible tools for operating and managing fleets of Blinksticks in harmony using the Blinkstick Python library.

Ansible tools for operating and managing fleets of Blinksticks in harmony using the Blinkstick Python library.

Greg Robinson 3 Aug 10, 2022
a weather application for the raspberry pi and the Pimorioni Inky pHAT.

raspi-weather a weather application for the raspberry pi and the Inky pHAT

Derek Caelin 59 Oct 24, 2022
Red Light Green Light Robot

Red Light Green Light Robot The primary problem addressed by our project is robotic follower behavior i.e. maintaining distance from a moving target.

Will Romano 2 Nov 20, 2021
A refreshed Python toolbox for building complex digital hardware

A refreshed Python toolbox for building complex digital hardware

nMigen 1k Jan 05, 2023
A versatile program that uses the raspberry pi camera and provides it as a service

PiCameleon Is a daemon program meant to provide the RaspberryPi Camera as a service while running according to a configuration.

André Esser 52 Oct 16, 2022
Electrolux Pure i9 robot vacuum integration for Home Assistant.

Home Assistant Pure i9 This repository integrates your Electrolux Pure i9 robot vacuum with the smart home platform Home Assistant. The integration co

Niklas Ekman 15 Dec 22, 2022
Automatically draw a KiCad schematic for a circuit prototyped on a breadboard.

Schematic-o-matic Schematic-o-matic automatically draws a KiCad schematic for a circuit prototyped on a breadboard. How It Works The first step in the

Nick Bild 22 Oct 11, 2022
A small Python app to converse between MQTT messages and 433MHz RF signals.

mqtt-rf-bridge A small Python app to converse between MQTT messages and 433MHz RF signals. This acts as a bridge between Paho MQTT and rpi-rf. Require

David Swarbrick 3 Jan 27, 2022
Hourglass on the pi pico using circuitpython

hourglass-on-pico "Hourglass" on the raspberry pi pico using circuitpython circuitpython version 7.0.0 Components used: Raspberry Pi Pico ADXL345 acce

4 Jul 18, 2022
Volkswagen ID component for Home Assistant

Volkswagen ID component for Home Assistant This folder contains both a generic Python 3 library for the Volkswagen ID API and a component for Home Ass

55 Jan 07, 2023
PlatformIO development platform for GSM modules

PlatformIO development platform for GSM modules Supported Modules Quectel M66 OpenCPU Arduino - TODO other - in progress... Supported Boards Comet M66

Georgi Angelov 5 Aug 06, 2022
Simples Keylogger para Windows com um autoboot implementado no sistema

MKW Keylogger Keylogger simples para Windos com um autoboot implementado no sistema, o malware irá capturar pressionamentos de tecla e armazená-lo em

3 Jul 03, 2021
Brogrammer-keyboard - FIrmware for the Brogrammer Keyboard v1.0

Brogrammer Keyboard Firmware The package contains the firmware that runs on the Brogrammer Keyboard v1.0 See https://imgur.com/a/oY5QZ14 This keyboard

Devin Hartleben 1 Apr 21, 2022
Quasi-static control of the centroid of quadruped robot

Quasi-static control of quadruped robot   This is a demo of the quasi-static controller for the centroid of the quadruped robot. The Quadratic Program

Junwen Cui 21 Dec 12, 2022
The PicoEMP is a low-cost Electromagnetic Fault Injection (EMFI) tool,

ChipSHOUTER-PicoEMP The PicoEMP is a low-cost Electromagnetic Fault Injection (EMFI) tool, designed specifically for self-study and hobbiest research.

NewAE Technology Inc. 312 Jan 07, 2023