Hmm what about devices connected via addons like Music Assistant, or Z-wave JS UI ?
If not I think half or less of my devices will be counted.
1 Like
Thanks for this initiative. Would be great to make it clear in the docs that custom component data is filtered out. (will save some lifetime of custom component devs as they don’t need to analyse the analytics component source code)
Would also be great to add some dev-docs around DeviceAnalyticsModifications and how to use this to prevent the upload of “senseless”-device data.
But again, thanks for this initiative.
Z-Wave might be included, I don’t think Music Assistant would be included because its not a “native” integration for devices (you could have a cast device in MA, but also the cast integration setup in HA).
They mentioned in the latest HA Podcast that no information from mqtt or addons (now apps) will be collected.
I guess it is a start… but at least in my system that means only around half of my devices will get counted.
I could not complete the survey because it compels me to “sign in with Google”. That means creating a Google account. Google is a rapacious advertising company that aims to collect and sell as much of my own personal information as possible. I will never have a Google account.
It doesn’t actually require you to sign in. Maybe you are already aware, as you said “compels me”, but still, it’s not required. And if you are just annoyed by HA using Google technology, well, I get it, but there are tons of similar examples, starting with HA being based on github, which is owned by Microsoft, and every HA instance by default connects to github. I don’t know, would you feel better if the survey was using MS Forms? I’m not sure I would.
How else are you going to know when to brush your teeth??
2 Likes
like daily routine 
I was hoping HA can actually brush the teeth for me…
2 Likes
This database is nice! My goodness, I’d love to see what APsystems has delivered so far, but so far I’m only seeing results from the official integrations. Will custom integrations be included as well?
I really like what the OHF has done here. Kudos to you.
One addition I’d like to see to the Grafana dashboard is the ability to filter by a country or territory of sorts.
It is certainly the case that same devices are more used in some areas than others, whether it’s due to popularity, availability (cost and ease of importing, if applicable), or practical or legislative constraints. Otherwise, places like the USA or Europe will simply dominate the statistics, making it less useful to those of us in other areas.
4 Likes
Here is my take on this topic I think, there should be a clear distinction between hardware (device) and the associated software. I have a few examples to describe what I am thinking:
I have Unifi networking and camera setup. The hardware (say the cameras) are not working well with home assistant. They don’t even talk to home assistant at all. The Unifi Protect application (the software) running on the NVR or Gateway (which is again a separate device) is talking to home assistant. Basically ANY camera what can be adopted into the Unifi Protect software will “work with” Home Assistant. (Yes, you can in theory set up a generic camera in HA and feed it with the RTSP stream, but in my head that is not “working with”. In that sense everything what has pretty much any kind of protocol what has a generic device assiciated with can “work with”)
On the other hand, I also have a few BIDI tubular motors with a 433MHz receiver. They don’t “work with” home assistant at all (yes there are some cloud based bridges to integrate them, but again, it is not the device which works with HA, but another device and it’s software). I did integrate them with some custom hardware (ESP) and software. Is it now an ESP device in the database, or is it the BIDI motor?
On the other other hand there is Govee for example. They do “work with” HA, right? Well, it really depends. You can say, they have a way to be LAN only, but the LAN API they provide is limited to pretty much the functionality of a dimmer switch (and it is a steaming pile of sh*t of an implementation IMO). It does work, but honestly not well. They proudly offer a cloud based API, which is working better, but now it is not local anymore. It can be integrated using Matter too, personally I did not try it in the the latest firmware versions, but older ones were limited to pretty much to the LAN API capabilities, however using say Google Home they have way more functions available. Clearly, the software is capable to handle pretty much all functions, they are just not made them available on all platforms/protocols. Are Govee lights “work with” HA? Does it work well?
And there are the appliances which are artifically limited to be cloud only, or even actively blocked to be used outside of their apps (with no reason in my opinion - no “security” is not a reason for cloud only options) - frankly most appliances and cars I have experience with are in this category.
I don’t have a good solution to this, but in case of for example Govee the verdict can be very different depending on which platform and protocol is used and it all depends on their firmware only, the actual device (the light) is pretty much irrelevant there. How it is categorized as one device? Especially in cases when the controller can be replaced with a third party solution which actually is working with HA very well (WLED), but is it the same device then? I’d argue no, but also I’d argue that not all WLED controllers are the same device then.
Don’t get me wrong please, I am not against this database and I am happy to see that it is being built, just I have a few questions about the actual implementation and representation of the collected data. I really hope that the different limitations of the devices based on their stock firmware (maybe even per version) and the actual platform/protocol they can be integrated will be visible and evaulated independently.
2 Likes
Watched the release party now so I can answer my own question - Ultimately that is the intention, but we started with the core integrations