That's exactly how it's build. Nabu Casa has never been able to see any user data. You can read more about it here https://support.nabucasa.com/hc/en-us/articles/2650888200758...
2,080 karma · joined August 27, 2012
Open the Sendspin live demo in your browser: https://www.sendspin-audio.com/#live-demo
Some more info on Kalman implementation here https://github.com/Sendspin/time-filter/blob/main/docs%2Fthe...
We currently use Lit for the framework on top (you do need one, that's fine). For state management we just pass props around, works great and allows community to easily develop custom cards that can plug into our frontend.
The downside is lack of available components. Although we're not tied to a single framework, and can pick any web component framework, the choices are somewhat limited. We're currently on material components and migrating some to Shoelace.
I talked more about our approach to frontend last year at the Syntax podcast[2].
[1] https://www.home-assistant.io [2] https://syntax.fm/show/880/creator-of-home-assistant-web-com...
So with the limited resources that we have, we currently only consider bigger donations valued $10k or more. We've had monetary donations from DuckDuckGo and Espressif so far.
Not everyone might know, but last year we started the Open Home Foundation as a non-profit in Switzerland and I donated Home Assistant to it[1]. It's fully funded by users. There are no investors involved.
We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.
~Paulus, Founder Home Assistant & President Open Home Foundation https://github.com/balloob
[1]: https://www.openhomefoundation.org/blog/announcing-the-open-...
It sends out BLE packets when pressed, which can be picked up by Home Assistant via a Bluetooth adapter or using a Bluetooth Proxy. You can make the latter with any ESP32 and https://esphome.io/projects/?type=bluetooth
If you want to go a step further, look for devices made for ESPHome or devices made by Shelly. Both have local APIs and are very hackable.
(disclosure: I am the president of the Open Home Foundation and ESPHome is one of our projects and I am also a board member of the Z-Wave alliance)
Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.
We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.
~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob
[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...
The way the world works, you need to be either a company or a non-profit to be able to partner with the industry. Just being an open source project is not enough.
Since the launch of the foundation, we see a large uptick in companies and universities reaching out to partner with Home Assistant. A lot of manufacturers are very happy to see that an independent platform is being established as alternative to the big tech platforms. Universities want to collaborate on energy and privacy research for the smart home. We've also seen some industry donations (ie DuckDuckGo) to support our work.
Now the community should be able to create such things, as our automation engine is very powerful.
I think the challenge in general with room presence detection is that these systems are not very common/reliable yet for us to aim to standardize.
(this can also be seen on our roadmap update https://www.home-assistant.io/blog/2024/11/15/roadmap-2024h2... )
Where we see the most pushback is from industries adjacent to the smart home, as they don't appreciate the openness. Think garage doors, cars, or cloud data providers for info that can be useful in the home.
When someone complains, like Mazda [1], we pull their integration and communicate their stance to our shared users, and people considering buying into their products. We don't fight for access, as a manufacturer with a cloud service will always be able to find a way. If it is a local device though, our community tends to find a way[2]
[1]: https://arstechnica.com/cars/2023/10/mazdas-dmca-takedown-ki... [2]: https://www.home-assistant.io/blog/2023/11/06/removal-of-myq...
Some backwards incompatible changes like requiring a new Z-Wave JS version are also able to be managed automatically by Home Assistant. However, because of choice, there are many ways Home Assistant can be installed and we're not always responsible for the installation.
I believe that we can do better in knowing what integrations you use, and mapping that against the integrations that require changes.
Inside Home Assistant the processing is delegated to integrations providing Speech-to-Text, command processing, Text-to-Speech. You can make custom integrations for all of them
It allows you to turn a cheap microcontroller into a voice assistant, bluetooth proxy or media player directly from your browser.
Last Saturday we announced that ESPHome is now owned by the Open Home Foundation. The Open Home Foundation fights for privacy, choice, and sustainability for smart homes. And for every person who lives in one. Learn more at https://www.openhomefoundation.org/blog/announcing-the-open-...