![]() ![]() The binding docs lists the type of support (ie the channels, and the clusters linked to these channels) - in general any device that supports this should work in the binding. The whole concept is that standard devices should work. So you’re saying that we shouldn’t really worry about any lists or databases? Instead they try to explain in docs how zigbee compatibility works in simplified layman’s terms like this: ZHA integration in Home Assistant has solved this problem by simply not listing any devices in its docs. The custom quirks implementations for zigpy implemented as ZHA Device Handlers for Home Assistant are a similar concept to that of Hub-connected Device Handlers for the SmartThings Classics platform as well as that of Zigbee-Herdsman Converters (formerly Zigbee-Shepherd Converters) as used by Zigbee2mqtt, meaning they are each virtual representations of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms. The ZHA Device Handlers that are made can then be reused by all users in future versions of Home Assistant. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. ZHA Device Handles do this by transparently, acting as a translator, translating and converting non-compliant device messages and instead present them to the application as coming from a virtual compliant device. Such a custom “ZHA Device Handler” are Python scripts that internally are also referred to as a “quirk” because they fix “quirks”, like deviations from the standard specifications. ![]() The few devices that deviate from the Zigbee specifications set by the Zigbee Alliance may therefore require proper bug reports with debug logs from users to assistant the developers in writing custom ZHA Device Handlers for all of a device functions to work properly with the ZHA integration. The ZHA implementation in Home Assistant relies on a library called “ ZHA Device Handlers” to resolve issues with Zigbee devices that do not fully conform with the Zigbee standards. Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub softwares, including but not limited to open source Zigbee implementations such as ZHA, Tasmota, Zigbee2MQTT, and ZiGate. The fact remains, however, that some hardware manufacturers do not always fully comply with each set specification, which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for ‘ZHA exception and deviation handling’ that this implementation features. There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the Zigbee Alliance should technically be compatible with this ZHA integration. The following devices are supported when connecting Pokémon GO to a Poké Ball Plus or the Pokémon: Let’s Go, Pikachu! or Pokémon: Let’s Go, Eevee! games.The problem is though that if people think it is a definitive list, then we end up with people thinking that the binding only supports a small number of devices - which is exactly what stated above Conversely, it is possible that other devices that are not listed below will work with the app.The list below is not a guarantee that all supported devices will work with Pokémon GO.When connecting an Android smart device to Nintendo Switch, the operating system (OS) on the smart device must be 5.0 or higher. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |