Govee M1 LED Strip with Matter Support

Hardware
,
1

Wanted to share my initial experience with the new-ish Govee LED Strip Light M1 with Matter support.

After a couple of failed attempts at getting the strip to connect to Home Assistant via the instructions in the Matter guide included with the lights, I double-checked my router and realized that I did not have IPv6 enabled.

According to the Matter guide included with the lights, IPv6 is REQUIRED for using the lights with Matter, which is pretty important info to know before you make the decision to buy these. I didn’t realize this was a requirement, and while I was able to get the light strip connected to Home Assistant via Matter after enabling IPv6 in my router, I’m not sure whether the limited functionality offered by the strip under Matter (literally just on/off, color and color temperature selection, and dimming) is worth the hassle.

In fairness to Govee, they do list the IPv6 requirement under “Preparation for Matter” in the product listing on Amazon, but it’s pretty easy to miss.

The hardware is nice, and well-packaged, so if you’re looking for some nice, albeit pricey, LED strips to start testing Matter support in your Home Assistant, I can say they do work once IPv6 is enabled. And pairing was pretty darn convenient just scan the QR code, and add to HA. There is not a great deal of functionality available via Matter and HA, however, just on/off, color, and color temperature.

While pairing with the Govee app is also convenient, it requires an account, and cloud connectivity. No thanks.

It’s encouraging to see vendors starting to add Matter support to their products, but as long as the majority of the cool features of a strip like this are limited to the vendor’s app, it’s really not a great step forward, IMO.

Anyone else try one of these? What are your thoughts?

1 Like
2

it’s not a huge surprise about IPv6 (and in my opinion very welcome). Because on the Thread side, devices are IPv6 - there is no IPv4 on the Thread side at all. So in order for a Thread device to speak directly to a WiFi / LAN device, it has to be via IPv6.

But more importantly, we are limited to 254 IP addresses on IPv4 - in the majority of home setups. Once you start adding lights, TVs, tablets, phones, smartwatches, ESPHome devices, smoke alarms, smart displays, speakers, thermostats, radiator values, smart blinds - etc etc - you eat up those 254 IPv4 addresses REALLY fast. Additionally the majority of ISP supplied home routers, might be configured for serving 254 addresses, but couldn’t actually cope with 254 devices being attached.

IPv6 has some cool functionality to resolve that, link local addresses, devices can talk to each other, internally without bothering the router (or in fact, needing the router at all - to even get a link local address). If devices DO need to reach out to the internet, the use of IPv6, means that NAT is not necessary (though it still is for the IPv4 devices) which significantly reduces resources required by the router.

As for the matter part of this conversation, matter only has basic functionality right now, that will change as it matures, but right now they are concentrating on adding device support.

1 Like
3

That all makes sense, and this has prompted me to start getting better acquainted with IPv6.

My biggest concern is that enabling IPv6 seems like a pretty big step before I understand how it works. I’m quite leery of what I don’t know about it ending up biting me in the butt either by inadvertently leaving something less secure, or by screwing up my network and ending up unable to reach devices I need to reach.

Any suggestions for a good primer on IPv6 for someone who, while not a networking professional, has a reasonably good understanding of networking in general?

1 Like
4

You don’t need to worry about the reachability issue, your devices behind the router will get an IPv4 address just like they always have, as well as an IPv6 address (or rather several IPv6 addresses) if it’s currently turned off on the router there is a good chance that your local devices still already have IPv6 addresses anyway, that they have given to themselves.

The way a device gives itself an IPv6 address is it chooses one, then it essentially says “hey guys, this is the address I’ve chosen for myself, does anyone have a problem with it?” And it sends that out to the address ff02::01 which means it addresses all devices connected to the same local network. If it doesn’t hear anything back, it assumes everyone is happy with us choice. Because every device does this, then they can all talk to each other, without a router being needed. But where IPv6 has an even better trick, when the router finally does give a device an IPv6 address, the device doesn’t lose its local address it assigned on its own. Unlike IPv4, with IPv6 devices can (and will) have multiple IPv6 addresses than they can use. My Pixel 6 for example right now has a local self assigned address and 2 public IPv6 addresses.

Personally I found this starter video very useful:

1 Like
5

Do you mind walking me through how you integrated the Govee M1 Matter lights into Home Assistant? I have IP6, but am new to Home Assistant. When I try to use the Govee integration, it say’s it no devices found on the network.

Any assistance would be greatly appreciated. Thank you for the help.

6

It’s been a while, and I returned the lights, but as I recall, I had to use the Govee app initially (could be misremembering). There’s a QR code on the device that helps with installing via Matter.

Sorry I can’t provide more detail…FWIW, I found this strip to be far too limited in terms of what it offers in HA to be worth the cost of the strip and hassle of dealing with IPv6 for just this device (not saying IPv6 is bad or anything, just don’t have the need to deal with it apart from the Matter device).

7

Just as a curiosity, did you just give up on getting strips or did you replaced them with something else, and if so what did you go with? I’m looking to replace my Illumi strip with something that’s HA compatible and has functionality. From your description, the Govees wouldn’t satisfy my uses.

8

For the moment, I’ve held off on Zigbee/Matter strips. I have another set of Zigbee controlled RGBWW LEDs, but they’re not individually addressable, so I just generally keep them on one color. They’re OK, but not really what I want.

For general LED strip use, if you’re willing to do a little soldering, a standard WS2811/12 B LED strip and an ESP32 board running WLED firmware is a great solution overall. Only big downside, IMO, is that it’s a WiFi-based solution, so if you’re trying to avoid more WiFi devices, that may nix that as an option.

I have a set of WLED-based lights set up for my son, and another small strip in a home-made edge-lit acrylic sign. Lots of options for colors/patterns, and integrates nicely with Home Assistant.

9

picked these up today (they were on sale and said “matter”, what’s not to love?). The H61E0 is being detected as a light, so… on and off support. That’s it. (edit: no, found the color picker)

Generally, the workflow to use Matter kinda sucks:

  • gotta use the Homeassistant mobile app.
  • in order to get Govee on matter, need to first set it up with the Govee app.
  • govee app has a QR code for passing to HA. Took a screenshot of that.
  • displayed the QR code on another device, used the HA app and scanned that QR code.
11

Yup. Given that IMO the Matter version of the lights isn’t any easier to use (and compared to some Zigbee bulbs I’ve used, actually more complicated), I’m waiting to see if things improve at all. Having to download and use a proprietary app for any given device is not the future I was waiting for with Matter… :wink:

12

Anyone else seeing a weird problem in the latest HA release when you change the brightness of the LED strip, the increase or decrease is very slow and is carried out in single increments!

E.g going from 20% to 80% brightness feels like it is taking 80 seconds.

13

Hi Finbarr,
Yes, I’m seeing exactly the same thing on my matter-integrated Govee M1s. Were you able to resolve this?
When controlling the LED from the HA companion app, I notice that the occasional instruction fails. It’s nothing I can reproduce systematically but it leaves me wondering if the matter integration is production-ready :thinking:

14

Yes. This fixed it for me. Create the file light_profiles.csv in the /config folder with contents:

profile,color_x,color_y,brightness,transition
group.all_lights.default,,,,0

And restart.

15

Cool, thanks Finbarr.
Sorry, hadn’t seen your response before now.

Is that in the custom_components/govee directory or in www/ ?

16

Nope just in the /config folder. See Light - Home Assistant

17

Got it, thanks Finbarr

18

Does anybody know a workaround fix on how to have the strips lower brightness when automation is triggered? The color/tone changes in my automation except for the brightness. If I manually run the “turn on lights” entity in the automation, then the brightness level changes. I’ve tried brightness value, percentage, step value and nothing seems to lower the brightness via automation.

19

I just bought the xmas lights, decided to read nothing before I installed them so this is perhaps not the best way to get them added. I have had them plugged in for 10 minutes so far. However, I did NOT need to use the App:

  1. install Matter on Home assistant
  2. you need the HA companion app on a smart phone to scan the QR
  3. in the companion app on the phone, open settings: integrations : matter
  4. click “add”, then “new”
  5. scan QR on the controller thing

Done. No govee App. no cloud. I’m not sure if they’re individually addressable. The “light” object has some options though:

image
image477Ă—535 18 KB

max_color_temp_kelvin: 6535
min_mireds: 153
max_mireds: 500
supported_color_modes:
  - color_temp
  - hs
  - xy
color_mode: color_temp
brightness: 255
color_temp_kelvin: 5025
color_temp: 199
hs_color:
  - 27.028
  - 18.905
rgb_color:
  - 255
  - 229
  - 207
xy_color:
  - 0.37
  - 0.35
icon: mdi:string-lights
friendly_name: Outdoor XMas Lights 1
supported_features: 32
20

Addressable LEDs typically have 3 or 4 wires, depending on whether they’re just RBG, or RBG and White. I don’t think Home Assistant has anything native that can deal with addressable LEDS.

If you want to delve into addressable LEDs, your best bet is to look into WLED (GitHub - Aircoookie/WLED: Control WS2812B and many more types of digital RGB LEDs with an ESP8266 or ESP32 over WiFi!), which is fantastic for controlling all sorts of addressable LED strips, strings, and such.

From what I’ve seen on the WLED subreddit, there are many Govee products that can be controlled via WLED, and there is a nice integration for WLED for Home Assistant. And WLED can be run entirely locally, no cloud. There is an app available, which can be helpful for managing multiple WLED-based controllers, but it’s not required.

WLED controllers can also easily be synced, so you can set an effect on one, and have all the others match it. Also, as of version 0.15.0, audio reactive support is built in, so if you use or create a controller with a microphone, you can take advantage of built-in sound-reactive effects.

Definitely something that takes addressable LED strips, etc. to a new level.