cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help

Shelly 1PM Gen4 via Matter appears as Sensor in Google Home - How to make it a Light?

Harri35
Community Member

2 weeks ago

Hi everyone,

I'm having trouble getting a Shelly 1PM Gen4 relay to show up correctly in Google Home when connected via Matter.

Here's my setup and what I've tried:

  • The Shelly 1PM Gen4 (firmware version: 1.5.99-g4prod1) is wired to my ceiling lights.
  • I connected it to my Wi-Fi (Nest Wifi Pro, which also acts as my Matter hub) via its web UI.
  • I successfully linked it to the Shelly mobile app and then connected it to Google Home (version 3.30.1.6) using Matter.

The problem is that in Google Home, it almost always adds the device as a sensor instead of a light.

Things I've tried:

  • Setting the device type to "light" in the Shelly mobile app.
  • Trying to set "light" as the "Consumption type" in the Shelly web UI (though this field seems more for energy monitoring).
  • I attempted to add the device to Google Home around 10 times.

Outcomes:

  • Only twice did it initially show up as a light in Google Home.
  • The first time it appeared as a light, I had to factory reset the Shelly device later for unrelated reasons and lost that state.
  • The second time it appeared as a light, it automatically changed to a sensor after about 24 hours.

All other connection attempts resulted in it being added as a sensor from the start.

I've seen conflicting information online about how Google Home determines the device type for Matter relays - some say the Shelly app settings are key, others suggest the device name given in Google Home.

Does anyone know reliably how Google Home determines the device type for Matter devices like the Shelly 1PM Gen4? More importantly, how can I ensure it's added and stays as a light?

Any advice would be greatly appreciated!

Home app screenshotHome app screenshot

 

0 Kudos
4 REPLIES 4

tajennifer
Community Specialist
Community Specialist

a week ago - last edited Wednesday

Hi Harri35,

 

Thanks for posting and for the detailed information. I'm sorry to hear about the situation that you are experiencing with your Shelly 1PM Gen4 on the Google Home app that is not recognizing a light. I appreciate all the steps that you took to solve the situation. Don't worry; help is here. I need to ask a couple of questions to provide the best solution:

  • Have you tried setting up the device in the Google Home not as a 'Matter-enabled device' or as a 'Works with Google Home' device?
  • Have you previously contacted Shelly's support? If not, I recommend doing so to verify if any configurations on their end need to be adjusted, as the Google Home app only relies on the partner app's configuration as well.

Please keep me posted. I'll be waiting for your response.

 

Best regards,

Jenny

Harri35
Community Member
In response to tajennifer

Thursday

Hei Jenny!

 

Thanks for your reply!

I guess this is a Matter-related issue and hopefully will be fixed in the future. Because I would strongly prefer to add it as a Matter device directly, not via Shelly Cloud.

 

0 Kudos

tajennifer
Community Specialist
Community Specialist

Thursday

Hi Harri35,

 

Thanks for the update. I'm happy to know that the device is set up correctly right now. Since you have the device duplicated, we recommend deleting the one that is not showing up correctly.
Also, we appreciate the feedback about the Matter device setup process.

Please let me know if you have more questions.

 

Best regards,
Jenny

Harri35
Community Member
In response to tajennifer

Saturday

I am still hoping to get the device working via Matter. Without the need to go via Shelly backend. Because in case of a network outage, I would be  unable to interact with the device if it is connected via the backend and not directly via Matter. To be honest, this is the only reason I bought the Shelly 1PM Gen4 relay - the Matter support and the inherent promise of the technology to be able to function in the local network. I guess my best chance here is to wait for software and firmware updates, and I hope this will solve my issue in the near future 🙂

0 Kudos