ETS on a Mac

Thanks Michael. I have turned this off after the first boot of ETS.

Hello ETS creators,

5 years later, this topic is still open and there is no yet solution. Please advise on your plans to create ETS for mac owners.

I too would love ETS for Mac and I was suprised that it's not supported. The whole point of KNX is automation and convenience so to then not have a convenient programming software is a shame.

waiting for it

we all waiting for this for years... what's the plan

I join the petition: When will ETS be available for Mac?

I'm sure someone from the developers and marketing looking at that, but maybe the cloud usage could be the solution. Even I can't use all PC apps on the new MACs it is possible with AWS (Amazon Luna) to run in a cloud based environment. At home, I also use an own home server to run ETS and some tax calculation tools (windows native) on a MAC. The problem is if like to work elsewhere with that software. 

So, how about a cloud based service ;) -> creates new business (maybe)

Running ETS is the only reason I keep a Windows computer. All my other devices are Mac. This Windows computer is now 12 years old and will need to be replaced only to be able to run ETS.

Any progress? I will for sure NOT buy a Windows machine just to be able to use ETS/KNX. And I don't want to pollute my Macs by installing Parallels and having a Win11 VM on them. 

I had to buy a Windows laptop ONLY to run ETS, what a pity. I don't understand why ETS can't run on Mac or Linux: it's based on C#, which is portable. I'm guessing it's because Windows-specific libraries are used? But why? There are portable libraries for everything. If the ETS code is well structured, it can't be too hard to replace the Windows-specific libraries with portable ones.

It's tempting to move to Koolenex. Fully free and open source, works on every platform, and you have the choice between a simple Web interface or writing little scripts for repetitive tasks. I hope this project gains enough traction to motivate the ETS team to improve portability and scriptability.

I'm not going to write another comment asking for macOS support. But I would like to understand how to get some transparency on that topic? I.e. what is driving the decision to not add macOS support? Is this at all considered? There seems to be disconnect in the brand's declared strive for openness and the silence on topics like this. I'm NOT saying it "non-open" to not support Mac.

It's just non-open to have a 5 year old thread that's still active and not taking a stance.

Yes, there is progress (@Fermin Sanchez et al) and yes, the overwhelming feedback and number of requests here as being considered (@Leo Selig et al).

ETS on Mac is one of the most requested "features" and I can confirm that it is on the shortlist for a future ETS Version. We are working on it, but the expectation is not only to have ETS on a Mac, but also to maintain the decades of backwards compatibility to millions of KNX installations out there.

I truly appreciate your interest and your feedback. You all here are what drive the developments, although it might not always seem like that or be as quick as you would prefer. And I hope you understand that this is as open as I can be about this here.

Best regards to you all!

Excellent news, thank you!

Cloud-based is a TERRIBLE idea. Your smart home should have local-only services.

Just write it well in a multi-platform language and it isn’t a problem.

Target the JVM and it will run everywhere.

Windows is for playing games and nothing else.

Thanks for the update. Regarding alternative platforms, web based apps are flexible options nowadays, but getting a native mac app is likely still the preferred option, in my opinion.

ETS on VMware works great on a macbook, but a ETS osx version would definitely be great. 👍

Glad to hear MacOS is on your roadmap. However, a web-based solution doesn't feel like a good technical choice, unless it can run fully locally.
Since I believe that ETS is written in C#, which is a language that can be used to write perfectly portable apps, couldn't you just identify the non-portable libraries your codebase currently relies on and fix that? It feels like much less work (or AI tokens) than rebuilding everything from scratch. A big rewrite is almost never a good idea.

If ETS is released as a portable application, please also consider providing a native Linux version. Moving from one proprietary platform to another is not a sustainable approach in today’s technology landscape. I would also strongly prefer a solution that does not depend on Java, as Java-based desktop applications often introduce unnecessary security, maintenance, and deployment challenges in professional workplace environments.