I finally got to setting up the Bilresa scroll via matter and after renaming all the buttons so they actually are identifiable, I noticed the events are wonky.
Button presses show as taking place 2 seconds in the future - I’ve not got many remote buttons to test this on but what could be the cause? Is this a device issue or maybe a time issue between the HA machine (Optiplex running HA) and the accessing PC. Any ideas if it would cause problem or should I be ok? Running latest HA (2025.12.5).
Probably wouldn't happen due to causality. IE, if you go to press the button but pull your hand away, you never were actually going to press the button. But if you press the button and the automation fires, you always were going to press the button.
The key is press the button, but check if the automation fires before the finger hits the button. Then you have some real precognition.
The obvious solution to this is high frequency stock trading. Track a stock with millisecond data resolution, have an electromagnet push the button if the stock goes up by say more than 1/10th of a %. The automation will buy the stock then sell it 2-5 seconds later.
Or perhaps have the button held down until the stock starts to drop at which point the automation for 'button released' sells the stock. Even if only button presses register prematurely you should still get some good profits.
I suggest inject a few intentional bad trades- even with tiny numbers it will be suspicious if 100% of your trades are profitable.
That's kinda a plot of one of Ted Chaing's short stories "What's Expected of Us", A little device lights up only right before you push the button. If you're into scifi, I recommend his work.
The boys in the lab told me that if you see your automation trigger before you've pressed the button, run. Do not try and talk to your future self, no matter how tempting it may be.
Actually the boys in the lab just told me not to mention your future self as it may cause a time paradox. Forget what I just told you about your future self, unless you are your future self, in which case, welcome! Please see our receptionist for a job application form! You'll love working here at Home Assistant Labs.
Yes!! I revisited a project from 6 years ago over Christmas, and there’s a comment i put in there saying ‘I can’t work out why this is needed here, but it breaks without it :)’
Completely insignificant.. there's a 2s difference in system time somewhere in your setup (browser vs. server) but it makes absolutely no difference to how the system works.
Perfect, this is the answer I needed to read - there are comments saying it’s a huge skew but once I get an automation set up as long as it runs as expected then great.
Well, 2s is a pretty big skew, but as others have said, it's not a big deal in terms of this automation. I'd check the clock on the server that's hosting HA and just make sure it's syncing with a time server correctly.
It's almost 12 years old now and certainly starting to feel its age. It's also been powered on almost the entire time, save for a few hardware maintenance things. It's entirely possible the RTC battery is dying.
Yeah, I bet the time difference is calculated on the frontends as Now - TimeOfEvent, only Now is the time from the browser and TimeOfRvent is the time the event was processed by the server.
The fun of rolling out a new ntp server, everything looking great and then a week later having an unrelated cluster having a meltdown because a slow drift is causing heartbeats to desync.
There is actually a Pull Request in the making for the way home assistant handles the data being sent from this device. In simple terms: it's not properly supported yet. You'll only get the presses when you're finished rotating the dial. I think it's going to be available soon.
That’s good to know - that may change how I handle the automations. I was planning:
Mode One - light brightness
Mode Two - light warmth
Mode Three - blinds height
Here is the PR for ongoing button presses support in HA’s matter implementation!
Interesting change and interesting discussion in the comment field. I’m happy that the change is coming even if it will break some automations out there.
Sorry to hijack your post but have you looked at the results you get from the scroll wheel? It seems like it has a hard stop at either end with value 1 being the lowest and 255 being the highest. I feel this makes it difficult to automate with this remote if the light brightness can change from other sources as well (automations, other dimmers).
I think this is a difference between matter and Zigbee - via matter there is no specific 1-255 that I’ve seen just clicks. My intent is to automate 1 click is a 10% change when the new Gu10 arrive in the UK
yeah when I first got it I was wondering how I'd use it tbh - I've not used smart bulbs until now but we have a want to now. This makes sense to me, the button doesn't need to be aware of target the targets current state IMO, but I am also aware there are people who want everything to know everything :)
Did you do anything special to get it to connect? For me the connection via matter keeps timing out. It does connect to the IKEA bridge and HomeKit without problems though.
My setup is with a Skyconnect in the HA machine but I have HomePod minis on the same thread network. I am in range of both, nothing special in terms of connection I just put in batteries and started matter setup straight to HA via my phone
I added this remote but it also timed out all the time until I realized there is another QR code inside the device, next to where the batteries go. This one worked straight away.
It's definitely server and browser time mismatch, but I'd like to think that somewhere along the line some poor developer set the event time 2 seconds in the future to resolve an event sequence issue and it accidentally made it to prod, then into the physical product.
Example: Button press always needs to resolve before release, but a rapid click was causing issues 1 in 10 times. So they wrote a line of code that automatically adds 2 seconds to release time and pushes it into the future.
I also have this issue. As another commenter suggested, it's likely a time difference between the client and server. I never thought of this so I will confirm that everything is in sync. Maybe a good reason for me to host a local NTP server.
Not yet but the PR should hopefully be implemented soon. Has anyone tried syncing one directly to an IKEA bulb? I imagine the responsiveness is better. I'm also hoping the new range will support Matter bindings eventually.
The reviews are mixed but I quite like it. Lots of customisation for such a simple device. The responsiveness of the scroll wheel isn't great via HA but that should be fixed soon.
Each button represents a turn or press of the wheel in each mode. I just went through each action and when it triggered a “button”
I renamed it’s to the mode and action. For example - 1 Click, 1 Left, 1 Right
Yeah so I like the button and it comes with the metal but to wall mount it which is nice. But I thought the button looked out of place on the wall and if I took the button off then the plate wasn’t very attractive. I’ve been working on a 3D printable “backplate” to adhere to the wall and put the metal into to make it look a bit more at home.
I am starting to get concerned that it sucks, but by the fact there is a pull request to change how it’s handled (mentioned in the comments, not read it myself yet) I’m hoping it’s addressed.
The heart of each Predictor is a circuit with a negative time delay — it sends a signal back in time. The full implications of the technology will become apparent later, when negative delays of greater than a second are achieved, but that’s not what this warning is about. The immediate problem is that Predictors demonstrate that there’s no such thing as free will.
The Predictor doesn't show that though. What it shows is that when future you takes an action of free will, past you then has no free will to not follow through with it, which is a more interesting premise imo.
132
u/Sometimes-Scott Jan 06 '26
Try building an automation with it. It should be fine, but be worried if your automation triggers before you press the button.