Ikea Alpstuga time sync (Matter issue?)

Hi all, just installed the Ikea Alpstuga Air Quality Monitor.

It is supposed to get the time from the network or Matter Controller?? But is living in the wrong timezone.

Location / Timezone of my Homey is correct. Time stamps on my timeline are also correct.

I did some searches, looks like this is a Matter issue as it is mentioned in the Home Assistant forum. Somebody even created a little Matter Time Sync thingy.

Any suggestions?

How do they connect? If it’s “Matter-over-WiFi”, I think that it just uses your IP address location and regular NTP to fetch the time, since it can do anything on the WiFi network as soon as it’s configured. If it’s a Matter-over-Thread device, it likely requires the controller to implement it

I believe they are Matter over Thread. Anyway to confirm this?

I just checked and it appears that they are Thread devices. AFAIK it’s not possible to get the time via Thread so this needs to be implemented by the controller (Homey in this case) which probably doesn’t have support for it yet.

is this a device specific function or is this a general omission in the Homey implementation?

I think it’s a device specific function, but since I don’t have experience with Thread I don’t know for sure.

The latter, it looks like the Matter implementation (this isn’t a Thread issue) for Homey simply doesn’t support setting the time synchronization cluster.

Sometimes the synchronization works, sometimes not. Today I had zu switch off the homey and at the same time the alpstuga. After reconnection the time is not synchronized. But I remember when I made the paring the time was shown correctly afterwards? Strange!

Same here. After initial pairing, time has synced (so there is some functionality there) but successive reboots did not do a time sync

I ended up creating a flow to cut the power through the plug and 23:59 and the waiting 58 seconds and giving it power again.

I activate a variable each 15 days or so to do a “Time Sync” at the next midnight, I was thinking of doing the same on daylight savings changes, but never got to. :slight_smile:

Same here. Time was OK after initial pairing. After disconnecting the power and moving to a different part of the room it’s now out of sync.

2 Likes

does that work to sync the time of the device?

I don’t have it plugged into a smart plug but could I just do the time sync every so often?

I have never created a flow with that.

Yes it works perfect. I enable it every 15 days or on every homey restart (it could be a short power outage).

I created a boolean variable called “Must sync clocks” and I enable it on those circumstances. at 23:59 every night, if the variable is set y wait 50 seconds, then power off the plug, then wait 8 seconds and power on (it takes about 1-2 seconds to boot). After than clear the variable “Must sync clocks”

With the latest firmware, this issue seems to be solved and also the measurements look more reliable. I live near the Hoogovens and before the upgrade I never ever got I a poor AQI alert. Now I sometimes do.

OTA updates via Homey are despite all announcements not possible. However, if you share the device via Matter sharing to Homekit, I do get an update every now and then.

The time gets updated?

Thats great!! Will check later today.

El El vie, 6 mar 2026 a las 14:58, Nils Kijkuit <notifications@athom.discoursemail.com> escribiĂł:

Hi all, I’ve been struggling with the same problem, and found a possible workaround.

First of all, my Alpstuga’s behaviour after power loss or reconnection (I moved it several times
) is wildly inconsistent. Sometimes it immediately synchronises to my timezone (UTC+1) as set by my Homey Pro (using the ‘Location’ setting), sometimes it synchronises but to UTC+0 instead of my timezone, and sometimes it doesn’t synchronise at all displaying 00:00 instead. As others have mentioned, using the clock buttons to manually adjust the time doesn’t work - it either resets to 00:00 or synchronises. From what I’ve found on other fora, this is as intended by IKEA.

Whenever one of the latter two issues is the case (time displayed is UTC or 00:00), what seems to be working for me is simply changing my Homey’s location to one timezone ahead (UTC+2 in my case). Strangely, if I then manually adjust the time with Alpstuga’s buttons, after 10-20 seconds it decides to synchronise to my timezone UTC+1. After an additional minute I change my Homey’s location setting back to my home address, and after that Alpstuga keeps displaying my timezone.

Sadly, it only synchronises the hours and minutes, not the seconds. It is mildly annoying that on my desk, my phone and PC switch to a new minute within 2 seconds of each other whereas Alpstuga lags behind about 45 seconds


I should note this workaround nevertheless means time synchronisation still doesn’t work as it should - and this now seems to be a Homey-specific issue as users on other fora using Apple TV and Home Assistant say their issues have been resolved with a recent OTA update for Alpstuga. So also to answer some questions above, this does not seem to be an issue with the Alpstuga itself or MoT.

why botter, add the sensor to another Matter controller (like AppleTV, HomePod) by using the Share Matter Device functionality. I see an update coming every now and then. And since it is at version 1.0.15, time gets resynced after a power outage or repair connection (it still looses connection every week or so)

Because for people like me, the entire idea of getting a Homey Pro was having a universal hub and Matter controller not part of any ecosystem like Apple, Google, or IKEA
 Just because Homey hasn’t properly implemented OTA updates and time sync (yet) doesn’t mean everyone should have to buy a second controller to fix those issues.

1 Like

I am with you! No OTA support is a big omission. So that root cause needs a fix asap indeed.

But in case you have an AppleTV or Homepod laying around, this could be a more robust fix for now.

And the idea of Matter is to be able to support multiple controllers.

1 Like

Or just wait a few months for Homey to implement the OTA updates.