TAPO H200 connect to Hubitat with Matter

I have been trying to connect some Tapo Matter devices to Hubitat. The P125M plugs and S505 Switch connect great using the instructions (Connect to Google home first, then add to Hubitat with Matter code generated in Google home). They respond to to commands and update status, even when status was changed locally at the device.

I can also connect the H200 hub this way and even a Motion sensor connected to the H200 but the Motion sensor doesn't update status in Hubitat. Google home sees the status update just fine. When I pull the motion sensor in using Matter, it sets the device type to "device". I tried to change that to "Generic Matter Motion Sensor" and "Generic Matter Switch" but it still doesn't change state when motion is detected. Google home see it just fine.

Same for the Tapo T310 Temperature Sensor

I also tried the Tapo integration App created by @djgutheinz (tpLink_Hubitat/Docs/releaseNotes at main ยท DaveGut/tpLink_Hubitat ยท GitHub) on Hubitat but it doesn't recognize the H200 Hub.

I have a work around to use a Virtual switch in Hubitat and have google trigger it with an automation, but that would not make it "local Control"

Any ideas?

Did you run the "Configure" command after changing drivers?

Clicking the "Configure" button doesn't appear to do anything.



Correct, it will not appear to do anything, as everything it does is behind the scenes.

But does it have any effect on device behavior? And anything interesting in "Logs" at any time?

dev:1742024-12-22 01:00:40.650 PMdebuggetting device info in 10 seconds...

dev:1742024-12-22 12:56:29.675 PMinfoMotion Garage Matter-2.3.9a: [method:updated, logEnable:true, debugLogOff:scheduled]

dev:1742024-12-22 12:56:15.926 PMerrorjava.lang.NullPointerException: Cannot invoke method refresh() on null object on line 33 (method refresh)

dev:1742024-12-22 12:56:14.653 PMerrorjava.lang.NullPointerException: Cannot invoke method refresh() on null object on line 33 (method refresh)

dev:1742024-12-22 12:56:12.400 PMerrorjava.lang.NullPointerException: Cannot invoke method refresh() on null object on line 33 (method refresh)

dev:1742024-12-22 12:53:09.463 PMwarnconfigure()

dev:1742024-12-22 12:51:32.207 PMwarndescription logging is: true

dev:1742024-12-22 12:51:32.205 PMwarndebug logging is: true

dev:1742024-12-22 12:51:32.204 PMinfoupdated...

dev:1742024-12-22 12:51:25.588 PMdebugon()

dev:1742024-12-22 12:51:17.475 PMwarndescription logging is: true

dev:1742024-12-22 12:51:17.473 PMwarndebug logging is: true

dev:1742024-12-22 12:51:17.472 PMinfoupdated...

dev:1742024-12-22 12:50:19.147 PMwarnconfigure()

dev:1742024-12-22 12:50:07.390 PMwarnconfigure()

dev:1742024-12-22 11:35:28.866 AMwarndebug logging disabled...

dev:1742024-12-22 11:05:28.841 AMwarndescription logging is: true

dev:1742024-12-22 11:05:28.839 AMwarndebug logging is: true

dev:1742024-12-22 11:05:28.836 AMinfoupdated...

dev:1742024-12-22 10:48:18.646 AMinfofingerprint endpointId:"03", inClusters:"0003,0406,001D,0039", outClusters:"", model:"Tapo Smart Hub", manufacturer:"TP-LINK", controllerType:"MAT"

dev:1742024-12-22 10:48:18.644 AMinfofingerprint endpointId:"01", inClusters:"001D", outClusters:"", model:"Tapo Smart Hub", manufacturer:"TP-LINK", controllerType:"MAT"

dev:1742024-12-22 10:48:08.485 AMdebuggetting device info in 10 seconds...

1 Like

What is dev:174? It looks like the Tapo Smart Hub. Are you adding the outlet directly to Hubitat or trying to use it via the Tapo hub as a sort of Matter Bridge? I don't know if the latter will work, though it might (you'd just need the Generic Matter Bridge driver if that's what you did, since the device you added is not a Matter outlet itself). If it's just the outlet, the log entries are quire confusing, as there is nothing about refresh on line 33 of that driver.

Dev 174 is the motion Tapo Motion Sensor(T100) that is connected to my H200 Tapo hub and added through MATTER integration into Hubitat

I also have the H200 hub integrated through matter (Dev 173) This hub has a few sensor attached and they are all working in the Tapo app and Google home but nothing shows up in Hubitat

It looks a lot more like that is the hub, not the sensor. Have you tried the Generic Matter Bridge driver instead?

I misremembered that this model number was an outlet, so ignore that particular comment above. :slight_smile: Those normally have a way to get added directly, no hub; this sensor might be different and need to be added via a Matter bridge, but I have no experience with it so cannot say for sure.

Yes I did. No change. I may just need to gat the H100 Hub since that has been tested by @djgutheinz

That will work. The H200 Hub uses a different protocol than any of the devices in this integration (it uses a ssl-based AES protocol that complicates matters greatly). It appears to be similar to the Tapo Cameras. After Christmas I will by one and work the protocol.

Added note to top that the integration does not currently support the H200 nor the connected H200 cameras.

Dave

1 Like

The Tapo integration app is sweet - thanks for all the work.
I got a H200 Tapo Hub and a few sensors (Thanks Santa) been scratching my head trying to get it working with Hubitat, to no avail.
Would love to hear about progress...

Thanks

1 Like

@tennesseedutchboy , you can try the custom package Matter Advanced Bridge with the Tapo Smart Hub, the logs are showing a motion sensor device.

P.S. Never believe what ChatGPT 4o mini model is saying .... :angry:

ChatGPT apologies...

Working next year - however I will have to invest some $$ from my fixed income. The H200 local LAN implementation uses the same security protocol as the camera (since it stores camera clips from the connected, battery powered, cameras). Sometime next year (once I get fully on-my feet again).

The matter implementation may be all that you really need, depending on the connected devices to the H200 and if they have been implemented in the custom bridge.

The custom package [Matter Advanced Bridge] worked ..
Installed T200 as ordinary Matter device and then changed over to the Bridge Driver.
I have working Motion Sensors.
Thanks for the info.
Happy New Year

1 Like