Shelly's Compatibility with Apple HomeKit: Firmares

This is not the first time we’ve talked about the Shelly’s compatibility with Apple HomeKit, in fact the entry of how to flash the Shelly to make it compatible with Apple HomeKit is one of the most visited on the blog. However, not only do we have the possibility to put the Mongolose firmware we were talking about in that entry, but there are other firmars that allow us to integrate the Shelly with the HomeKit devices.

What is a firmware?

If you’ve reached this page you’ll know what a firmware is, but just in case. The firmware is, as it were, the operating system that runs a component. On many devices it is possible to update and we can change the behavior a little, unlock functionalities, etc.

The original firmware that Shelly devices carry is compatible with Google Home and Alexa, but not with Apple HomeKit. It was a few years ago, but it seems that for an Apple license issue, Shelly was forced to take off the support… and until today. Shelly’s people say he’s working on it to return Apple HomeKit’s support native (and official).

But in the meantime, users can flash the device to make it compatible by replacing the original firmware. To not repeat what we already commented on in the entry on flashear Shelly to make it compatible with Apple HomeKit, we will save the rest of the details in this.

In the other entry, I explained step by step how to install the Mongolose firmware in the Shelly. This firmware is very good, works properly, has many extra features and, of course, includes support for Apple HomeKit. But he’s not the only one! There are currently many people who are updating the Shelly to install the firmware Home Access Architect (HAA). The veteran’s out there too. Tasmota firmware that so many joys have given us with the SonOff devices.

The differences between them will depend on your real needs, as I always say, but the main difference is that Mongoose is much more ‘user-friendly’. I still use the Mongolose firmware because it’s the one I know the most, it’s very simple for me to have the web interface and I already move through it with loose if I need to change any parameter. In addition, the update is very simple. However, the HAA Firmware is more complicated, although it allows more options. On the one hand, it promises energy savings as it reduces the speed of the processor by being better optimized, so it consumes less and is less heated. I mean, it’s not like the Shelly gets hot with Mongolos.

e, if you touch it with your hand notes it’s a little hot (and therefore on and running) but it’s not so hot as to melt a cable or burn to the touch much less! And of course it’s not going to give you any trouble, no matter how much funnel you got it in the wire.

On the contrary, HAA is MUCH more complicated to manage. The configuration is based on JSON files that interpret firmware… and it seems that they are written in Hebrew! For non-programmers like me but that we like to tamper is quite difficult to understand. It is true that they have a very good wiki and very active forums where the most experienced users are able to make a JSON file tailored to your needs if you make the request, but still I feel too ‘corset’ to be comfortable with this firmware. However, the partner @ J

ASF of the Telegram group is a in love with this firmware xD

In addition, to flash a Shelly with the HAA firmware you need a FTDI adapter that allows us to overwrite the original firmware by the firmware HAA. It is only the first time, since once flashed it is possible to update it without any problem, but it complicates the process a little bit.

There is also an intermediate firmware between Mongolose and HAA that allows us to download HAA and flash the device without having to connect it to anything… but I don’t know, I see it already get too much… we have to update it first to Mongolose, then to the intermediate firmware, then to HAA… so I stay directly with Mongolian and get integration with HomeKit which is the end we are looking for from the beginning, right? If what you’re looking for is’ simply ‘this compatibility, don’t worry that you’re not going to give up any basic functionality and you’re not going to be’ short ‘much less and it’s 100% reliable.

wp: block {«ref»: 1612} /