Additional information: Same problem when I tried connect H100 and its devices to Google home using Matter.

The H100 and its devices is added successfully, but the devices do not present data. They are unreachable in the Google home gui.

So the problem still seems to come from H100 and firmware update 1.6 1. At least not from Homey pro or Google home.

Futher investigation... Somehow are the endpoints/IDs mixed up after firmware upgrade. The values is sometimes updated in Homey pro, but for the wrong device. The devices is swapped randomly. 

So data is updated over matter, but the firmware is swapping device IDs randomly. Found no way to correct them.

I hope TP-link can solve this. Devices swapping id is not good if you have been login around them. They now behave very strange and very cumbersome to update/swap devices in the logic is a Princess.

  @Wayne-TP 

I have 5 H100 hubs and one of them has auto updated to FW 1.6.1 some time ago but the others haven't and are still on FW 1.5.23. Has the roll-out of FW 1.6.1 been halted due to some problems?

@ts73 I read your post but still decided to update, was feeling adventurous today haha.

It indeed breaks everything in SmartThings too if you have temperature & humidity sensors. Before 1.6.1, temperature and humidity belonged to the same endpoint, which was also nice for smart home platforms that display both attributes in the same device tile. In 1.6.1 they are separate endpoints and now display as different devices too.

So, yes, the endpoints have changed and the device-endpoint mapping known to SmartThings or Homey breaks. They may get data from a sensor and believe it's another device because the only know the source endpoint, or get a motion sensor report and think "what's this if this is a door sensor".

The only solution is removing the H100 from Matter and all the child devices if the platform doesn't delete them automatically. Then add the H100 again, rebuild the automations, etc.

  @mocelet 

Yes, same behavior and I have seen it as a Matter specification change made this happened. Discussed it somewhat with Tp-link support.
A problem that is hard to avoid when specification changes. Someday are one required to handle this. Its kind of avoidable.

Yes, the devices are now doubled. I hade to update my flows in Home pro etc. It did not take too long even if I made som error connection wrong device. One hour or so overall. Not to bad and I just hope the Matter specification does not change too much in the future.

@ts73 I'm not aware of any breaking change in Matter specification, they just chose to expose the T&H sensor as two devices endpoints instead of one as before. Plus, the new update doesn't even support Matter 1.3 so is still running under old specifications.

  @mocelet 

Ok. To be clear. The Tp-link support did not say these changes due specifikation changes (did not deny it either in correspondense). I did some chatGPT-ing and was informed that this could be a reason. So... take this with a grain of salt.

@ts73 The way I see it is that they changed the way to bridge T&H sensors but didn't consider existing setups.

The hub should have been smarter to not change endpoints of unrelated devices like, say, a motion sensor. And, for T&H sensors, knowing it would break integrations, it would have been better to remove the old devices and create new ones so the users don't end in a bad state where the platform thinks something is a device but it's another one due to the endpoint change.