Just got a couple of Grillpats plugs and they are excellent so far. At a fraction of the price, Eve should be worried.
Hi! Any idea if they will be certified? It will be in a month a year or never?
Thanks!
No endpoints have connected to my Grillplats according to the connection path information in the app.
But my thread mesh network continues to be stable. Very strange.
Thread behaviour still feels like a bit of a mystery to me.
My Grillplatt shows up as a router (in the Eve app) with an active path out, while the Onvis consistently appears as an endpoint. Even stranger, the Alpstuga sensor usually shows as a router/leader, but I’ve seen it appear as an endpoint at least once.
I followed the advice here to remove multi-admin because I was getting poor responsiveness and effectively results improved considerably. Since then, I’ve re-shared all my powered devices to both SmartThings and Apple Home without any issues.
In fact, just yesterday I shared 8 Myggbett contact sensors, and so far everything is working perfectly.
It would be great if ST provided a detailed visualization of the thread mesh similar to Eve. Effective tools to monitor and troubleshoot thread networks are lacking.
Anyway, not sure why my Grillplats are not showing any connected devices. But my network continues to be rock solid and very responsive. So I am assuming they are acting as thread routers.
IKEA dubbelkisel MoT led driver looks like it’s on the way soon.
Title is a bit misleading. It’s matter over thread so not really “hub” free if it’s dependent on a matter controller and thread border router.
If only I could buy IKEA devices in Brazil.
This new MoT lineup looks amazing, at great prices.
lol, was just about to post this myself. My klippbok actually updated on 5th may
Looks like firmware update 1.9.15 is now available for IKEA Bilresa dual button remote through SmartThings if you poll via AWA, or possibly just initiate from within the device card on the app, if the prompt to upgrade appears when you open it.
Curiously, the presentation used for the Bilresa dual button (stock driver) doesn’t define the badge://sw_updatable badge that is usually displayed when a firmware update is available.
Odd, I have three bilresa remotes, 2 updated fine but the third keeps failing to complete. It’s in the same room as another bilresa that succeeded
I have eight. Only one has ever updated the available version and that had also gone on to update. I may have requested the check in the AWA but if I also pressed the install button it wasn’t with an update shown as available. The others have all had checks requested on the AWA at least once.
As with my Onvis plugs which took months (on and off) to get updated, I don’t really know what my expectation should be. I was imagining something more obviously automatic and quicker.
Mine is prompting via the ui on the device card to update. The two that updated needed a couple of tries. The third thus far isn’t updating successfully, I’ve tried about 10 times thus far.
I had the same issue. I had to reset and re-pair one BILRESA before it updated successfully.
Are your updated BILRESA showing the Connection path correctly?
Back when I installed the test firmware version in the scroll wheel it started showing a broken path. Now the dual buttons with updated public firmware also display a broken path. The only one still showing the path is the one not updated.
Not that I care about the diagram, it works and that’s what is important, just curious.
Also broken path here
Broken paths only when they are children of a Thread <= 1.3 device. When connected to a Thread 1.4 device, the path looks fine.