Athom makes beta of Homey Web App available – Image and sound – News

I have written several Apps for homey. And recognize the “problem” and partly be the cause. The reasons can be very diverse, but I think it is good to consider.

Developer does not have the same device model to test with.

Developer himself no longer uses the device.

Manufacturer changes API or protocol.

It takes quite some time to develop. Which is sometimes not available.

Etc etc.

Most of the apps just work really well. Many different equipment is supported by this approach, including obscure niches. This would not be possible without this approach. Of course it is a shame if that one feature or model is just not supported. Often there is just a solution and it takes time. For the developer but also for the person who would like to see the type or feature supported.

I have received devices several times from both manufacturers and fellow homey users to add support. If I can continue to use the device, the chance that it will remain well supported is again greater than when I return the device. The knife cut on both sides.

My experience with manufacturers is also very variable. For example, in the beginning of Homey I had an App ready for Honeywell lyric thermostats. I was unclear about the use of the API key, limit of x per hour. I have tried everything to get in touch with Honeywell about using that key. I had been running that App at home for months and I still had no clarity, so I decided not to publish the App.

I had regular telephone and direct contact with another manufacturer, NEEO (RIP). I must have been the first to have access to new software and SDK releases so that I could start my translation to Homey before the software was released as beta.

These are clearly two extreme examples of how a developer can work together to create an App. It will be clear that this has direct consequences for an app.

–