Hello, Home Assistant Community
Introduction
I’m Arek Kuleta, a professional Automotive/IoT software engineer and a user of Home Assistant. While we all share a passion for our setups, I feel that safety often takes a back seat. That’s why I decided to integrate some of the safety methods from my professional experience into our home automation systems.
I’m actively working on incorporating safety practices inspired by automotive standards such as ASPICE, ISO 26262, EGAS, and ISO 21434 into our Home Assistant setups. I am not following every point from them, just trying to tailor it to my needs and available resources.
My aim is to create a secure and reliable environment that safeguards our privacy and ensures the integrity of our connected devices. I’m aware of Home Assistant Supervisor and I’m planning to integrate it into my system.
It’s important to note that these standards were primarily designed for C applications running on ASIL-rated operating systems and ASIL-rated microcontrollers. Adapting them to the Docker and Python environment might be challenging, if not impossible. To assist me in this project, I rely on OpenAI’s ChatGPT. This powerful language model not only aids in generating content but also ensures personal review and authenticity. It allows me to focus more on the technical aspects while providing reliable assistance.
Current status
My journey has already begun with a Hazard Analysis Risk Analysis (HARA), which identifies potential risks involved in home automation.
Based on this analysis, I’ve outlined the system requirements and architecture for a safer Home Assistant setup. To avoid overloading this post, I’ve kept post short. You’ll find short descriptions and examples on my blog, while the full documentation is available on the GitHub repository. Link at the end.
Things to do
We still have a long way to go, with several key areas to focus on:
Calibration: Defining thresholds, constants, and input data specific to each home setup.
Interface Requirements: Adding missing system interface requirements, particularly for sensors.
Hardware Requirements: Defining the necessary hardware to run the safety system effectively.
Software Requirements: Defining functional and non-functional requirements for the software as part of the overall system.
Software Architecture: Designing a robust software architecture, including components, interfaces, timings, data exchange, scheduling, and incorporating the EGAS standard to reinforce safety aspects.
But before I proceed, I will shift my attention to the implementation phase to create a proof of concept. I hope that I will show it in the next update.
Kindly request
Meanwhile, I kindly request your review and feedback on the first part of the project available in the repository. There is a pull request open, so feel free to add comments/issues. You can also add comments here, under the post. Your thoughts and ideas are invaluable to me.
You can find all the current progress, including blog posts and source code, on my blog and GitHub repository. Feel free to explore, provide feedback, and engage in discussions.
Let’s make safety a top priority in our smart homes.
Best regards,
Arek Kuleta
Links
GitHub repo - SafetyConceptBranch