The logs showed the following error: java.lang.NullPointerException: Cannot get property 'time' on null object on line 122 (method parse) so I commented out line 122 and now the battery level is showing properly.
1 Like
Thank you for the report! I have fixed the bug in the code snippet where it was first published.
Good day everyone. Wondering if I can add anything to the conversation or offer any data that can help. I too have jumped in using several IKEA battery powered Matter over Thread devices. I'm using the IKEA hub as my TBR and using it to commission Matter devices to be paired to HE.
Main powered Matter devices remain stable. Wi-Fi and Thread both. Battery powered Matter over thread devices actually appear stable too, EXCEPT, obtaining the data from them. Like contact open/closed events, or temperature, or humidity. That said, if in HE device details I use the "refresh" command (initialize seems to have no effect) I get a dataset, and HE shows it.
So, it almost seems Sensor events are not being "heard" by HE. Is it something as simple as HE is not "listening" and needs to be told to hear something?
Hi Michael,
Please refer to this post :
1 Like
TY. It's so frustrating that I have actually considered migration away, and I have been using HE from nearly the beginning.
We all hope that the new Hubitat platform 2.4.4 will resolve the issues with Matter device attribute changes and event subscriptions.
2 Likes
I discovered I had an issue with one of my router mesh units. This was causing a lot of issues with my WIFI network. Once I resolved that my network has been rock solid.
So I re-visited the IKEA Thread devices. I paired the contact sensor with Apple Home. Left it sitting on the desk for several days and played with it to make sure it was working ok. No problems.
Yesterday I added it to HE. Seemed to be fine all day. I tried it with both the system driver and @kkossev driver. Both seem to work ok.Then this morning my logs were filled with debug statements just showing endpoints and clusters, etc. And the contact sensor no longer worked in HE. This was on the system driver. Changed to @kkossev driver and same result. The sensor still worked fine in Apple. So had to remove it from HE.
Strange that all was fine for almost all of one day then went south.
I really have a place I wanted to use this. So I ended up with a virtual switch/contact in HE and created 2 automations in Home to sync them. So far so good. Just kinda disappointing that I had to do that.
Iām sorry if I have missed some important info. Iāve read through the thread, but I couldnāt find any information related to my issue.
I have bought a Kajplatsa build and a Myggbett sensor. Both was included in Apple Home on first try but only the bulb, Kajplats, could be included into HE through Matter, my Myggbet seems impossible to include. Any advice?
I had to keep trying over and over. Finally about the tenth try it went thru. But as stated in my previous post didnāt work for long.
The ONVIS mains powered smart plugs didn't really help. The Thread network apparently is deciding their routing isn't needed, yet my IKEA devices keep falling off after 2-3 days. In fact, one of the ONVIS plugs has itself become unreachable.
I guess it isn't just me .. There's an article on The Verge about the new IKEA devices having connectivity issues. That's behind a paywall, but this article is similar.
Right now all my Ikea devices are only paired in Apple Home. Then I used virtual devices in HE with. automations in Home to trigger them. That has been working great. Looking forward to the next HE firmware update which 'supposedly' will have Matter updates.
One thing I just ran across. The EVE app has a thread network analysis. Shows which router and signal strength each device is connected to. I had several Homepod Mini's scattered around and after looking at the EVE info I actually got rid of a couple of them and things seemed a lot more stable.
Just my nickels worth.
1 Like
Update on my system. I have 5 Ikea devices. (Had to buy that many to get free shipping). 2 motion sensors, 2 contacts, 1 button. All are connected to Apple Home and working great for some time now. I quit trying to pair them into HE and using virtual switches to interface.
After a lot of research here is one thing that seemed to help. I had several Homepod Mini's scattered around the house. Originally used them for voice control until that got so slow it was useless. I also have a Apple TV 4k. The TV seemed to always be the primary hub to Home. I unplugged all of the pods except one in the opposite end of the house from the TV. Our house is not all that big. Things started working a whole lot better after I did that. Even the basement got covered good.
From what I could read too many pods can overwhelm the airwaves and in my case it appeared so. Also from my understanding the TV seems to be the main thread radio router as it is wired ethernet and the pod only functions as a repeater unlesss the TV goes down. Using the EVE app it appears that is the case. EVE shows the routing.
I resurected some Google Mini Pods for voice control, which work very fast and reliable. They are old enough they don't have thread radios so no interference there.
I have 8 miniās and 3 tvās in one location and 9 minis and 3 tvās in another, and havenāt experienced anything similar.
I canāt state for sure that multiple pods was the cause. It only affected things once I added the IKEA thread devices. Prior to that there was no problem. Since I didnāt need all of them anymore it was no big deal to remove some. Several things I googled recommended that but other things said not necessary. So never know what to believe. Our main floor is only 1400 sq ft so the 2 devices are fine. One is over the finish part of basement and the other over the garage and they seem to handle everything.
1 Like
I don't have any IKEA Matter stuff, so that is also a big difference.
I'm trying to withhold judgement about the new IKEA devices until they release their Matter over Thread smart plug to build better connectivity. But so far I'm unimpressed. They work for a few days and then drop off.
I bought some Onvis plugs as a temporary workaround, but apparently the Thread network has decided they don't need to route, so they're not.
Do they drop off your TBR?
I havenāt had any drop offs from Apple Home as long as I donāt try to connect them to any other platform.
LOL...and give up one of the key benefits of Matter devices... 
It seems Ikea has some work to do here.
2 Likes
That statement kinda got me thinking...
If I understand right one of the main purposes of Matter is the device is not tied to any one particular platform. If you have HE or Homey or HA or whatever, the idea is the device would be compatible. Assuming the particular platform has got things ready for Matter.
Now my thought is that most folks only have one platform. Thus the Matter device only needs to connect to one platform. I realize there are exceptions, but...
So in my case I only have one automation platform and that is HE. I look at Apple Home as more of an inteface/dashboard type thing than anything else. I don't use it for any automations of any kind except for presence.
So in theory I could get along without it except for one thing... I need a border router for thread devices. And initally when I bought a few Matter devices a long time ago I believe HE didn't have the capability to add them in as the primary. So I needed Home to initially pair them. HE has changed since then so that I don't really need Apple to add in a Matter device anymore.
I guess my point here is Matter really intended to be connected to multiple platforms at the same time? I realize it can be, but is that the original intent.
Just some musings as I continue to tax my old worn out brain trying to understand it all.....
Yes, that is the original intent. The idea was to make it easier for device manufacturers to target one specification, Matter, and have the sensor/bulb/switch/etc...be able to be controlled by a wide variety of controllers. So, it's not really about the end users like us (though we can and do benefit from it). Instead, the primary drivers were the big tech names (Apple, Google, Amazon, Samsung) wanting to commoditize smart home devices.
1 Like