search

FezVrasta / node-red-matter

Create Virtual Devices with Ease for the Matter Protocol!
43 stars 9 forks source link

Google home prints out no certified matter device after scanning QR Code #5

Closed Stephan-4711 closed 1 year ago

Stephan-4711 commented 1 year ago

Hi,

as you see error above

I used your examples and and added one of my devices Debug log in node red shows:

15.9.2023, 10:11:02node: Light 1 msg : string[29] "No server or aggregator found" 15.9.2023, 10:11:02node: Light 2 msg : string[29] "No server or aggregator found" 15.9.2023, 10:11:02node: Outlet 1 msg : string[29] "No server or aggregator found"

FezVrasta commented 1 year ago

Could you please delete your flow, and just add a single Matter Device Status node, associated to an aggregated device with its bridge and let me know if everything works?

Stephan-4711 commented 1 year ago

after deleting everything in side the flow and just left one Matter device status node, there is another error message. No connection to device possible (or something similar, I translated from german)

FezVrasta commented 1 year ago

No errors on Node-RED? Try enabling the debug log level, restart Node-RED, and try to pair, then post here the logs

Stephan-4711 commented 1 year ago

I activated the debug log:


2023-09-15 14:44:40.038 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: eth0
2023-09-15 14:44:40.057 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: docker0
2023-09-15 14:44:40.085 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: hassio
2023-09-15 14:44:40.118 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: vethf616138
2023-09-15 14:44:40.141 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: veth6d300b7
2023-09-15 14:44:40.173 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: vethd114d66
2023-09-15 14:44:40.190 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: veth45d4ce5
2023-09-15 14:44:40.212 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: veth5aee0c2
2023-09-15 14:44:40.228 DEBUG MdnsBroadcaster Announcement: Commission mode  mode: 1 qname: 68567706C820FC1B._matterc._udp.local port: 5459 interface: veth427d04b
2023-09-15 14:44:40.340 DEBUG MdnsScanner Found commissionable device 68567706C820FC1B._matterc._udp.local with discriminator 1329/5 ...
2023-09-15 14:44:43.996 DEBUG MessageExchange New exchange protocol: 0 id: 34781 active retransmit ms: 300 idle retransmit ms: 5000 retries: 5
2023-09-15 14:44:44.004 DEBUG MessageExchange Message « id: 0/34781/186938097 type: 0/32 reqAck: true payload: 1530012022eda8ed98812d7687114dc765d64301c61bfa82a7723b20d67672f89a7171a32502b9f6240300280418
2023-09-15 14:44:44.014 INFO PaseServer Pase server: Received pairing request from udp://fd14:2107:e190:4c12:15d7:201c:8578:9d5b:41004
2023-09-15 14:44:44.045 DEBUG ExchangeManager Message » id: 0/34781/2342555713 type: 0/33 acked: 186938097 reqAck: true payload: 1530012022eda8ed98812d7687114dc765d64301c61bfa82a7723b20d67672f89a7171a3300220e6bff62c3d5093268075434e02c7acb38d614ecab5d77140a98b85814ad6fc7025032f5535042501e803300220413710175020baa7f1f07e877651a07cdd7462d9d354a40950dd6e9264c027b81818
2023-09-15 14:44:44.130 DEBUG MessageExchange Message « id: 0/34781/186938098 type: 0/16 acked: 2342555713 reqAck: false payload: 
2023-09-15 14:44:44.148 DEBUG MessageExchange Message « id: 0/34781/186938099 type: 0/34 acked: 2342555713 reqAck: true payload: 153001410407d5c7e2f7bc1c88d6f5a2eb3d2638754cfe07a5c231efcee1a0f36b4bcc34867d7c705c3223edfb21caa1029921c3cdc93bd77cfb4b454bad50f474d9dd4f4c18`
FezVrasta commented 1 year ago

Thanks, these don't look complete though, they should be much longer. I don't see any error here.

Stephan-4711 commented 1 year ago

It's the debug log and I restarted whole system after activation

Apollon77 commented 1 year ago

Seems like the controller found the device basically but then do not continue the pairing. What controller you tried?

Apollon77 commented 1 year ago

Ps: aahhhh google and not certified? Did you added the device details to the google dev console? Google requires this for non certified devices like the node red flow does. See https://github.com/project-chip/matter.js#google-home-ecosystem

(But the log should be longer in any case!)

@FezVrasta maybe please Link to th we page vm also officially in repo.

Stephan-4711 commented 1 year ago

Oh I didn't know that. I'll try tomorrow or Sunday for Google and alexa. I have the required hardware. Did you had this link anywhere in your git? Then I'm sorry I did not see that.

Stephan-4711 commented 1 year ago

Ok, that was the problem. I can see inside node red, that the virtual devices ist switching. But because of deleten the samples as told, I'm now not able to bring it back to a connected devices. I'm new to node red and don't have programming experience. Can you give me a tip, how to connect all the needed things to make a switch working again?

FezVrasta commented 1 year ago

I'm not quite following what's going on. This project is still in its early days so I'm not sure it's suitable for people with no coding experience

Stephan-4711 commented 1 year ago

I'm just missing a sample config inside the wiki and also if there is a way to add not every device it self. As far I was understanding the matter parts it looks like it should be possible to add a "bridge" for all devices I like to add to google home?

Is there a way to bring back the sample configurations without reinstalling the node red matter package?

FezVrasta commented 1 year ago

You can import the example flow at any time https://flowfuse.com/blog/2023/03/3-quick-node-red-tips-5/#:~:text=Click%20on%20the%20%22Examples%22%20button,to%20your%20Node%2DRED%20workspace.

Stephan-4711 commented 1 year ago

Thanks, thats working for me now.

I tried to add the "matter" device to google and alexa at the same time. If using the Philips Hue Hub this is possible. Node red Addon is me giving this output, after I connected to google home:

This device is already paired, you won't be able to pair it with other controllers until you decommission it from the paired controller first.

will that be chaged, that I can connect the matter devices to all Voice Controllers?

FezVrasta commented 1 year ago

Unfortunately pairing the same device to multiple controllers isn't supported but it's something I'd like to enable eventually.

Apollon77 commented 1 year ago

I will add this soon to matter.js ... so stay tuned, controller will get a bigger overhaul API wise