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
DIY split-flap display

The goal is to make a low-cost display that's easy to fabricate at home in small/single quantities (e.g. custom materials can be ordered from Ponoko or similar, and other hardware is generally availa

Scott Bezek 2.5k Jan 05, 2023
KIRI - Keyboard Interception, Remapping, and Injection using Raspberry Pi as an HID Proxy.

KIRI - Keyboard Interception, Remapping and Injection using Raspberry Pi as a HID Proxy. Near limitless abilities for a keyboard warrior. Features Sim

Viggo Falster 10 Dec 23, 2022
Designed and coded a password manager in Python with Arduino integration

Designed and coded a password manager in Python with Arduino integration. The Program uses a master user to login, and stores account data such as usernames and passwords to the master user. While lo

Noah Colbourne 1 Jan 16, 2022
Better support for Nuki devices to the Home Assistant

Another attempt to add a better support for Nuki devices to the Home Assistant Features: Lock interface implementation Uses local webhook from bridge

Konstantin 105 Jan 07, 2023
Projet d'integration SRI 3A ROS

projet-integration-sri-2021-2022 Projet d'intégration ROS SRI 2021 2022 Organization: Planification de tâches Perception Saisie: Cédérick Mouliets Sim

AIP Primeca Occitanie 3 Jan 07, 2022
Vvim - Keyboardless Vim interactions

This is done via a hardware glove that the user wears. The glove detects the finger's positions and translates them into key presses. It's currently a work in progress.

Boyd Kane 8 Nov 17, 2022
GUI wrapper designed for convenient service work with TI CC1352/CC2538/CC2652 based Zigbee sticks or gateways. Packed into single executable file

ZigStar GW Multi tool is GUI wrapper firtsly designed for convenient service work with Zig Star LAN GW, but now supports any TI CC1352/CC2538/CC2652 b

133 Jan 01, 2023
This is a python script to grab data from Zyxel NSA310 NAS and display in Home Asisstant as sensors.

Home-Assistant Python Scripts Python Scripts for Home-Assistant (http://www.home-assistant.io) Zyxel-NSA310-Home-Assistant Monitoring This is a python

6 Oct 31, 2022
An open source operating system designed primarily for the Raspberry Pi Pico, written entirely in MicroPython

PycOS An open source operating system designed primarily for the Raspberry Pi Pico, written entirely in MicroPython. "PycOS" is an combination of the

8 Oct 06, 2022
Pi-hole with Inky pHAT ePaper display

Pi-hole with Inky pHAT ePaper display This is my Pi-hole with an ePaper display.

11 Sep 13, 2022
A simple non-official manager interface I'm using for my Raspberry Pis.

My Raspberry Pi Manager Overview I have two Raspberry Pi 4 Model B devices that I hooked up to my two TVs (one in my bedroom and the other in my new g

Christian Deacon 21 Jan 04, 2023
An arduino/ESP project that can play back G-Force data previously recorded

An arduino/ESP project that can play back G-Force data previously recorded

7 Apr 12, 2022
PyLog - Simple keylogger that uses pynput to listen to keyboard input.

Simple keylogger that uses pynput to listen to keyboard input. Outputs to a text file and the terminal. Press the escape key to stop.

1 Dec 29, 2021
2021 Real Robot Challenge Phase2 attemp

Real_Robot_Challenge_Phase2_AE_attemp We(team name:thriftysnipe) are the first place winner of Phase1 in 2021 Real Robot Challenge. Please see this pa

Qiang Wang 2 Nov 15, 2021
ArucoFollow - A script for Robot Operating System and it is a part of a project Robot

ArucoFollow ArucoFollow is a script for Robot Operating System and it is a part

5 Jan 25, 2022
A battery pack simulation tool that uses the PyBaMM framework

Overview of liionpack liionpack takes a 1D PyBaMM model and makes it into a pack. You can either specify the configuration e.g. 16 cells in parallel a

PyBaMM Team 40 Jan 05, 2023
Raspberry Pi Power Button - Wake/Power Off/Restart(Double Press)

Control Raspberry pi with physically attached button. Wake, Power Off, and Restart (Double Press) . Python3 script runs as a service with easy installation.

Stas Yakobov 16 Oct 22, 2022
Custom component for Home Assistant that integrates Candy/Haier Wi-Fi washing machines (also known as Simply-Fi).

Candy Home Assistant component Custom component for Home Assistant that integrates Candy/Haier Wi-Fi washing machines (also known as Simply-Fi). This

Olivér Falvai 61 Dec 29, 2022
OPNsense integration with Home Assistant

hass-opnsense Join OPNsense with home-assistant! hass-opnsense uses the built-in xmlrpc service of OPNsense for all interactions. This project is curr

Travis Glenn Hansen 54 Jan 03, 2023
ROS2 nodes for Waveshare Alphabot2-Pi mobile robot.

ROS2 for Waveshare Alphabot2-Pi This repo contains ROS2 packages for the Waveshare Alphabot2-Pi mobile robot: alphabot2: it contains the nodes used to

Michele Rizzo 2 Oct 11, 2022