Haptique OS beta is live now

Haptique Beta is live. It arrived.

The first Haptique OS Beta is now live for the community.
This beta brings three major pieces together:

1. Haptique OS

Haptique OS is the new local runtime for Haptique.

It runs on your own machine and gives you a local control layer for devices, automation, integrations, and the Haptique experience without depending on a remote cloud server for day-to-day operation.

2. Local Fleet Server

This beta also includes the local Fleet Server path.

That means the configuration apps and Haptique RS90 can communicate with your own local Haptique server instead of relying on the current hosted Haptique RS90 server.

In practical terms: users can set up and operate locally, without needing internet access or our hosted server for that configuration/control flow.

3. Haptique Music

Haptique Music is also part of this beta.

This is our local music and media layer inside Haptique, including local library support, playback control, player discovery, outputs, queues, radio, and the foundation for deeper local music server features.

What we want feedback on

Please test it in real setups and share:

  1. What system you installed it on
  2. Whether your config app connected successfully
  3. Whether your Haptique RS90 connected successfully
  4. What devices, integrations, or music outputs you tested
  5. What worked well
  6. What failed, broke, or felt confusing
  7. What you want us to prioritize next

This is a beta, so expect rough edges. The goal now is to test the full local Haptique path in real environments: Haptique OS, local Fleet Server, Haptique RS90/config apps, and Haptique Music working together.

Thanks for being part of this. This is a big step toward Haptique running fully local, with the cloud no longer required for the core experience.

Your licenses will be released to your email address this week as we build the user database so for now you can connect your Haptique with local fleet server running on any machine and connecting Haptique and Config app pointed at the IP address of the machine running HOS. Look forward for an email to get your license copy for the Haptique OS. We also have discord community now for realtime discussion.

To participate in the beta do I need to have a RS90? I ordered a RS90x and am holding out for that. Having said that I would love to participate in the Haptique OS Beta. I have a NAS and use Home Assistant so Haptique OS has a lot of potential.

You don’t need RS90, HOS is independent of Hardware and can be hosted anywhere. It also works as RS90 web server and also add new features to the RS90 if you have one. If no than you can use HOS mobile app, Apple Home App, Mac menu bar app etc.

1 Like

Here is an article on how to connect your Haptique OS instance to RS90.

1 Like

Thank you for the replies :grin:. I requested the HaptiqueOS beta but haven’t received it yet. I can see KS backers get the perpetual license indefinitely and 1 year of Remote license. I assume that allows one to use their phone or Apple device as the remote. Is that right? Is that limited to one year with the hope that the RS90x will be delivered by then? What happens if at one year the RS90x still isn’t in production?

The 1 year license is for Remote controlling, meaning if you are not home and not on LAN but want to control over internet.

For Local use of Mobile app, Apple Home, Macbar App and HOS Server + Haptique Music is all covered under perpetual one time license.

We have already added all our customer be it Kickstarter, Indiegogo or via Webstore. Also all from the waitlist so check here and it should show your license. - https://myhos.haptique.io/

And the process is documented here - Getting Started | Haptique® OS

How to deploy on Docker?
As I’m quiet familiar with docker I wasn’t able to deploy a server using the docker container.
It appears that some environment variables are expected but I couldn’t manage to find any documentation regards that.

According to the log this are the required variables:

variable not defined - Error: APP_NAME 
variable not defined - Error: APP_SECRET_KEY 
variable not defined - Error: APP_URL 
variable not defined - Error: PORT 
variable not defined - Error: APP_MASTER_PASSWORD 
variable not defined - Error: DB_BACKEND 
variable not defined - Error: JWT_SECRET_KEY 
variable not defined - Error: JWT_EXPIRATION 
variable not defined - Error: JWT_REFRESH_SECRET_KEY 
variable not defined - Error: JWT_REFRESH_EXPIRATION 
variable not defined - Error: IR_BASE_URL 
variable not defined - Error: IR_MAC 
variable not defined - Error: IR_LANG 
variable not defined - Error: AWS_S3_SECRET_KEY 
variable not defined - Error: AWS_S3_ACCESS_KEY_ID 
variable not defined - Error: AWS_S3_REGION 
variable not defined - Error: AWS_S3_BUCKET_BASE_URL 
variable not defined - Error: AWS_S3_BUCKET_NAME 
variable not defined - Error: SMTP_PORT 
variable not defined - Error: USER_NAME 
variable not defined - Error: USER_PASSWORD 
variable not defined - Error: SMTP_SERVICE 
variable not defined - Error: MAIL_FROM 
variable not defined - Error: ADMIN_EMAIL 
variable not defined - Error: MAIL_ENCRYPTION 
variable not defined - Error: APP_SUPPORT_EMAIL 

Could you please provide some information about that?
Once I got the server up and running, I’m happy to share feedback.

Thanks for flagging the env issue, we are woking on it today to solve and make the experience straight forward via Docker hub release.

I installed the docker image on my Synology NAS using Container Manager. But I’m not able to access it via http/://localhost:8080. Container Manager says HaptiqueOS is running (the app is live). I’m not sure what to do. When I look at the Container for ccsfr-haptique-os-server everything looks fine, except the Network Gateway and IP address are very different than my network. Please help.

New update pushed on Docker hub now you can install directly.

Use Docker Desktop and run exactly this:

docker pull ccsfr/haptique-os-server:latest
docker run -d --name haptique-os -p 8080:8080 -v haptique-os-data:/app/storage ccsfr/haptique-os-server:latest

Then open http://localhost:8080/os.

On first launch, Haptique OS opens directly to the setup screen. Create your admin account in the browser and continue into the app. You do not need to set environment variables, generate secrets, or preconfigure a password.

The Docker volume haptique-os-data keeps your admin account, local database, uploaded files, and runtime secrets between restarts. If you remove the container, your data stays as long as you keep that volume.

To stop and start it later:

docker stop haptique-os
docker start haptique-os

Have you got this fixed?

Hi @ccsfounder ,

Here is my installation detail :

Hypervisor Proxmox VE
VM Type KVM — UEFI (OVMF), q35 machine
CPU 2 vCPU (1 socket, 2 cores)
RAM 4 GB
Disk 20 GB (local-lvm, virtio-scsi)
Network VirtIO — bridge vmbr0
VM IP 192.168.10.xxx/24
Operating System Debian GNU/Linux 13 (Trixie)
Kernel 6.12.94+deb13-amd64 (2026-06-20)
Architecture x86_64
Docker Engine 29.6.0 (build fb59821)
Docker Compose v5.1.4

My side the docker run command works, but I add --network host (required for mDNS/SSDP/UPnP discovery).

docker run -d --name haptique-os \
  --network host \
  --restart unless-stopped \
  -v haptique-os-data:/app/storage \
  ccsfr/haptique-os-server:latest

After, I was able to connect to http://192.168.10.xxx:8080/os and activate my licence.
I was able to add integration related to discovered devices, but no time to test them for the moment.

Haptique Web App is also working (http://192.168.10.xxx:8080/admin).

I’ve got the following error on http://192.168.10.xxx:8080/os/media-services :

[startup:error] subsystem=runtime class=bundled_asset exit=1 OS Media Web bundled assets are missing. evidence={"assetFamily":"os-media-web","candidates":["/os-media-web/dist","/app/apps/os-media-web/dist","/os-media-web/dist","/os-media-web/dist","/os-media-web/dist"]}

Issue pairing RS90 with Android App :
I follow the documentation. ( Pair Haptique RS90 | Haptique® OS
RS90 screen with QRcode (Local IP sever already changed and same as Android App).
On android App, scan the QRcode and the application crash.
I’ve tried several time, and always same issue.

I was able to add my IR-Extender.

Question :

  • Where can I find devices added from OS/Integration ?

Thanks for your help.

Regards.

David

Hi @daangel27,

The issue looks to me is Haptique Music runtime error. There is new version 1.1.9 published today try that and confirm.

HOS integration to be exposed on the RS90 you need to use Fleet devices. It is explained here.

Basically devices(Logical devices) of HOS are expose to Fleet which is RS90 devices via this page. Just a checkbox and they will be showcased on the Config app and web, than you can manage them the way you manage others.

How do I change the default port 8080. I can’t seems to find in the UI .Also I can’t see a thing

  1. Can’t seem to be able to delete old project
  2. Project set up wizard is not really visible
  3. not clear how to change port
  4. adding a room > I can’t see how to add the device to this room (they are already added)
  5. it really feel the UI is not linked and some card are not even the same size.
  6. We should be able to either build a list of device then add them to a space or when adding a device it i should be clear how to. This is currently too confusing with special naming convention. (at least for me). Maybe it set for professional .
  7. I do think you need to write down in a clear manner what needs to be done and make it available via the UI. it feels very all over the place and looks like different stuff added together.

Hi @ccsfounder ,

OK Noted.

About 1.1.9, there is no amd64 package available, only arm64.
Thx

Ok will address that.

Hi,

Will address the light mode issue as this is because the UI is retaining the dark mode in few areas as I can see. Try to use the Dark mode from the Dashboard.

  1. There is no provision to delete the project - Will provide this under UI update.
  2. Setup Wizard - Will also be optimised.
  3. Ports are by default 8080,8081 and 8082, will provide manual way to change it.
  4. Rooms are called Spaces in the Haptique OS. You can check the sidebar and build Spaces.
  5. Please share more info on Discord chat.
  6. You have to first add integrations, which brings Logical devices and then you add them to spaces(rooms).
  7. There is a small visual tour and Documentation here - Overview | Haptique® OS.

You may want to post on Discord more often as there is channels for each purpose. Discord.

1.1.9-r3 Now has the x64 version. Fresh install it.

Haptique OS 1.2.0 RC3 is ready for testing.

If you install it, please share:

  • your device/platform
  • what you tested
  • what worked well
  • what broke or felt confusing

We’re especially interested in feedback on setup, AI provider connection, music playback, HomeKit startup, updates, and first launch.

Download the latest beta: Haptique® OS Server Downloads

If you’d rather chat in real time, there’s also an active Discord thread in the community server.

Docker Hub tag update is available for Haptique OS 1.2.0 RC3.

If you’re testing the container flow, please try the latest tag and reply with:

  • your platform
  • whether pull/startup worked
  • any install or update issues
  • anything confusing in first launch

We’re especially interested in Docker-based beta feedback right now.