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
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
A DUCO (Duino-Coin) miner for GigaDevice ARM boards.

GD32 Duino-Coin Miner Description Contains the firmware and miner software for mining DUCO (Duino-Coin) on GigaDevice GD32 chips. Supported boards GD3

Maximilian Gerhardt 2 Feb 20, 2022
Using a raspberry pi, we listen to the coffee machine and count the number of coffee consumption

A typical datarootsian consumes high-quality fresh coffee in their office environment. The board of dataroots had a very critical decision by the end of 2021-Q2 regarding coffee consumption.

dataroots 51 Nov 21, 2022
A Python class for controlling the Pimoroni RGB Keypad for Raspberry Pi Pico

rgbkeypad A Python class for controlling the Pimoroni RGB Keypad for the Raspberry Pi Pico. Compatible with MicroPython and CircuitPython. keypad = RG

Martin O'Hanlon 43 Nov 11, 2022
The robot is an autonomous small scale racing car using NVIDIA Jetson Nano.

The robot is an autonomous small scale racing car using NVIDIA Jetson Nano. This project utilizes deep learning neural network framework Keras/Tensorflow, together with computer vision library OpenCV

1 Dec 08, 2021
OpenStickFirmware is open source software designed to handle any and all tasks required in a custom Fight Stick

OpenStickFirmware is open source software designed to handle any and all tasks required in a custom Fight Stick. It can handle being the brains of your entire stick, or just handling the bells and wh

Sleep Unit 23 Nov 24, 2022
Connect a TeslaMate instance to Home Assistant, using MQTT

TeslaBuddy Connect a TeslaMate instance to Home Assistant, using MQTT. It allows basic control of your Tesla vehicle via Home Assistant (currently, ju

4 May 23, 2022
Python apps to assist with Gas Blending

Welcome to DiveTools Gas Blending This tool is for testing and educational use. It is not intended to confirm the mix of breathing gases. If this tool

Tucker 7 Sep 18, 2022
emhass: Energy Management for Home Assistant

emhass EMHASS: Energy Management for Home Assistant Context This module was conceived as an energy management optimization tool for residential electr

David 70 Dec 24, 2022
Volta: A Virtual Assistant which increases your productivity with time as you use it…

Volta Official Documentation Overview & Purpose Volta: A Virtual Assistant which increases your productivity with time as you use it… Volta, developed

Abeer Joshi 1 Jan 14, 2022
Get input from OLED Joystick, Runs command, Displays output on OLED Screen (Great for P4wnP1)

p4wnsolo-joyterm Gets text input from OLED Joystick Runs the command you typed Displays output on OLED Screen (Great for P4wnP1 - even better on Raspb

PawnSolo 7 Dec 19, 2022
Poupool is an overflow swimming pool control software

Poupool - The swimming pool controller Poupool is a swimming pool control software. It is based on Transitions, Pykka and Paho MQTT. The user interfac

Cyril Jaquier 8 Jul 18, 2022
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
A Fast, Easy, and User Friendly way to control Robotics Actuators.

T-Motor Controller A Fast, Easy, and User Friendly way to control Robotics Actuators. View Demo · Report Bug · Request Feature Table of Contents About

26 Aug 23, 2022
Home-Assistant MQTT bridge for Panasonic Comfort Cloud

Panasonic Comfort Cloud MQTT Bridge Home-Assistant MQTT bridge for Panasonic Comfort Cloud. Note: Currently this brige is a one evening prototype proj

Santtu Järvi 2 Jan 04, 2023
Switch predictor for Home Assistant with AppDeamon

Home Assistant AppDeamon - Event predictor WORK IN PROGRESS - CURRENTLY NOT COMPLETE AND NOT WORK This is an idea under development (when I have free

37 Dec 17, 2022
Philippe 1 Jan 09, 2022
Count the number of people around you 👨‍👨‍👦 by monitoring wifi signals 📡 .

howmanypeoplearearound Count the number of people around you 👨‍👨‍👦 by monitoring wifi signals 📡 . howmanypeoplearearound calculates the number of

Zack 6.7k Jan 07, 2023
A Home Assistant integration for Solaredge inverters

A Home Assistant integration for Solaredge inverters. Supports multiple inverters chained through RS485.

Seth 50 Dec 23, 2022
Keystroke logging, often referred to as keylogging or keyboard capturing

Keystroke logging, often referred to as keylogging or keyboard capturing, is the action of recording the keys struck on a keyboard, typically covertly, so that a person using the keyboard is unaware

Bhumika R 2 Jan 11, 2022