# Not auto-uodate on breaking changes

**URL:** <https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994>\
**Category:** Ideas & Suggestions\
**Created:** [October 17, 2026, 1:18pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994 "2026-10-17T13:18:19Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![CoonHouse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coonhouse/32/2764_2.png) [@CoonHouse](https://community.homey.app/u/CoonHouse)\
**Post date:** [October 17, 2026, 1:18pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/1 "2026-10-17T13:18:19Z")

</div>

Is it for app developers possible to prevent auto-update of their app when there are breaking changes? And sent a push notification instead?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [October 17, 2026, 1:21pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/2 "2026-10-17T13:21:11Z")

</div>

Not possible, the only way I can think of is to add a permission (which stops auto update) but that doesn’t send a notification. In my own apps, I do use a cloud service which all installations connect to, where I can remotely push timeline notifications, but you do need a VPS server for this

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 17, 2026, 1:23pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/3 "2026-10-17T13:23:45Z")

</div>

MANY years ago developers asked Athom to allow for apps to use proper [semver versioning](https://semver.org/) and then not auto-update apps when the major version (backward-incompatible changes) changed. Like many suggestions, it went nowhere.

---

<div class="post-metadata">

**Author:** ![CoonHouse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coonhouse/32/2764_2.png) [@CoonHouse](https://community.homey.app/u/CoonHouse)\
**Post date:** [October 17, 2026, 1:42pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/4 "2026-10-17T13:42:35Z")

</div>

You mean all installations are connected (websocket?) to your VPN? And you then send a message when there are breaking changes?

---

<div class="post-metadata">

**Author:** ![CoonHouse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coonhouse/32/2764_2.png) [@CoonHouse](https://community.homey.app/u/CoonHouse)\
**Post date:** [October 17, 2026, 1:45pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/5 "2026-10-17T13:45:06Z")

</div>

To bad.

It should be something like NPM. Only upgrade on minor updates.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [October 17, 2026, 1:58pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/6 "2026-10-17T13:58:05Z")

</div>

> [@CoonHouse](#):
>
> You mean all installations are connected (websocket?) to your VPN? And you then send a message when there are breaking changes

Yes, true. The installations generate a random ID when it’s installed, and it uses that ID to connect to the WebSocket. On startup the app sends the version to the server. It also sends a ping every 30 seconds to keep the connection open. With the admin portal, I can create notifications that all installations on a specific version will receive. Online installations will get it immediately, the offline installations will receive it when they reconnect.

I can share the code for the backend (VPS side) if you’re interested.

---

<div class="post-metadata">

**Author:** ![CoonHouse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coonhouse/32/2764_2.png) [@CoonHouse](https://community.homey.app/u/CoonHouse)\
**Post date:** [October 17, 2026, 2:21pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/7 "2026-10-17T14:21:19Z")

</div>

Thanks, that would be great.

---

<div class="post-metadata">

**Author:** ![CoonHouse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coonhouse/32/2764_2.png) [@CoonHouse](https://community.homey.app/u/CoonHouse)\
**Post date:** [October 17, 2026, 2:25pm UTC](https://community.homey.app/t/not-auto-uodate-on-breaking-changes/160994/8 "2026-10-17T14:25:04Z")

</div>

Wat zijn de verdere use cases voor de VPN? Of is het vooral statistiek?
