HomeKit's temporary failure with environmental automation

A few weeks ago, in the episode of January 10 I was telling you at HomeKit. it is better to create an Automation that contains an environment than to create an Automation with the devices there loose, so it’s always better to create Ambients by grouping devices and actions. This has many advantages, not only the speed with which they are executed, since with an environment all devices receive action at the same time while with a normal Automation they receive it sequentially. We can also invoke the environment with Siri without having to run

automation, etc, in the episode of the 10th I was talking to you about all this.

Well, the point is, During last week, some of these automations containing environments stopped operating for no apparent reason. It was very curious because if you were running the environment manually, it was running well, but if you were running the automation from the little button that is below the automation that says’ Prove this automation ‘, I started running it and I showed an error… and now. That’s right, that the idea of Steve Jobs who said’ It simple works’ and that the user had to get away from the technology behind it is very good, but fucking, a log to know what the hell is failing so that it would come from that mistake…

very well in some cases. But no, the House app says’ Error ‘and fly.

For those of you who use the payment version of Controller for Homekit that you already know is my favorite app to manage devices, automations and notifications in HomeKit, you will know that we have a section called Maintenance where information is shown that can help us diagnose incidents. By the way, these days I’m making a BCP, a Business Continuity Plan for a European organization… and they don’t like the word incidence, they’ve made me change it for issue. Anyway.

The point is that on the Driver’s Maintenance menu for HomeKit you can see for example if you have inaccessible devices, although that the Home app also tells you. If you have low battery devices, that the House app also tells you but when it tells you it’s possible that the device will have 10 minutes of battery, it always says it too late or directly shows it to you as inaccessible without warning you that it had low battery… and also shows it to you in the same House app, huh? It doesn’t even send you a notification of the type ‘Eye that you have some low battery devices, it goes into the app to see what they are…’ is that I don’t expect a notification anymore.

n type ‘You have this device with low battery’, that would already be fantasy, but the Home app doesn’t do that because we have to get rid of the technology and the spent batteries.

Well, you know that with Home Assistant we can also receive this notification from low battery, A few weeks ago I also told you about it here..

Total, that in the Controller Maintenance menu we can find very useful information… but in this case, if you entered the Automations section within the Maintenance menu it did not show you any error, all OK. And if you looked at the section of the Scenes (which is what Controller calls the Environments even if they are the same thing), it also showed how everything was OK.

Controller does have a Log where he gives you all the information on what’s happening, but the truth is that I don’t use it for that very thing, because he gives you all the information on what’s happening… that is, you have all the sensors reporting in real time every second the state of the battery (whether low or not), temperatures, wetlands, negative smoke detection… all of that in real time, it’s like you’re capturing the traffic in the network of devices… and it’s crazy to see something there. I have always been very black-screen made in need of a grep or a tcpdump filter or something to filter only for what I’m interested in… total,

I don’t use the blog at all.

After investigating for a while and checking that there was really no clear reason why I was failing, he gave me for entering Reddit… and bingo, some users complained about the same problem.

You know me, the first thing I thought was’ for nothing happens, we migrate back to Home Assistant, disable HomeKit automations and activate Home Assistant automations’. I mean, what I do whenever I heat up with one of the two platforms… until I heat up with the other one again and I migrate to the first. Good thing in my case this migration is done in 10 minutes by activating and deactivating respectively. But I didn’t do it at the time and I thought ‘tomorrow I do it in a while’… and you know what? That the next day was all right. So yes, without reboot the iPhone or the accessories power plants, without new firmware version, without Apple press release

I’m sorry for being too busy on the fucking robot that they’ve shown in the shape of the Pixar flexus so they can pay attention to the errors on HomeKit’s platform… but something they did to make the mistakes work out alone.

And these things really screw me up. Okay, yeah, it’s not a fart like Home Assistant at the beginning of the year that left us all the zigbee devices inaccessible and we had to do things to get them back. But I don’t know, a page of Apple where they tell you these things, a kind of forum or GitHub where they explain that there is a mistake in a service and that at the same time it is solved… many services offer this information practically in real time. But no, in Apple, we have to get rid of technology. It’s good that nothing has to be done to make it work out, but it would be even better to be informed and know that you don’t have to do anything to make it work out instead of

and have us 1 hour looking for the reason for the failure, changing automations and looking in reddit.

wp: block {«ref»: 1612} /