Replies: 2 comments 5 replies
-
|
Hi @intui , According to our testing, this Google account registration is no longer required. However, in the past, we have seen similar errors in the Google Home app when the data model was incorrect or had something unexpected. Can you share some details about whether you using one of the default products or have you customised and/or created a new one? If it is a custom one, is it possible for you to share the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for answering, @chiragatal , ######################################################## Starting console: 2025-04-03 9:18:48 AM W (11134) wifi:(he)attach, station, phymode:11ax W (14232) wifi:ACK_TAB0 :0x 90a0b, QAM16:0x9 (24Mbps), QPSK:0xa (12Mbps), BPSK:0xb (6Mbps) W (14307) wifi:(he)attach, station, phymode:11ax W (15317) wifi:(he)attach, station, phymode:11ax |
Beta Was this translation helpful? Give feedback.
-
|
From the logs, in the next step the device should receive the Wi-Fi credentials from the phone, and that has not happened. So it indeed seems like an error with the Wi-Fi network. Can you ensure that the device, the hub, and the phone all are on the same 2.4 GHz network? Can you also temporarily turn off the mobile data on your phone to ensure that the phone does not switch to that instead? And then try again. If it still does not work, then to debug the problem more, would it be possible for you to try with a different Wi-Fi network? Or maybe setting up the device in a different ecosystem first and then adding it to Google, just to see if this works. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for getting back to me @chiragatal . |
Beta Was this translation helpful? Give feedback.
-
|
Hi @chiragatal |
Beta Was this translation helpful? Give feedback.
-
|
Hi @chiragatal, I tried an Aeotec Hub in the meantime and didn't run into the Wifi connectivity problems. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @intui. The root of the issue appears to be an incorrect or outdated data model. I have enabled the Could you please download it, rename it to data_model.zap, and place it in your codespace at the following path: I believe this update should resolve the issue you encountered. I tested the data model on my end with both Google Home and Apple Home, and it worked as expected. Also, please make sure you're using the latest version of the codespace, a recent change was merged that fixes the data model creation and is required for this to work properly. Let me know how it goes or if you need any help! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
I'm currently struggling to setup a device in Google Home.
Everything works fine in Codespaces as described in esp-lowcode-matter/README.md. When I try to setup the device in my Google Home Network after scanning the QR Code, and confirming to setup an uncertified device, it says that a connection with my WLAN is not possible and I should connect to a 2.4 GHz network even though I'm connected to a 2.4 network.
device_setup.md says under Google - Requirements:
Since the device has test certificates, your Google account needs to be registered to be able to setup the device. You can share your Google email ID with us, and we can enable your account.
Is this the cause of the setup problem? If yes, how can I share my Google account name with you?
Thanks for your help & looking very much forward to getting creative with the very promising lowcode approach.
Greetings, Wido
Beta Was this translation helpful? Give feedback.
All reactions