Live data from Hacker News

Matter 1.2 – New device types and improvements

csa-iot.org

61–70 of 70 posts

Re: Matter 1.2 – New device types and improvements

#61

Is there a SIMPLE way to have a small python or go program act as a "switch" that shows up in Google home? The last time I tried looking at the matter stuff even checking out the git repo required gigabytes of storage and it seemed the opposite of simple.

If you can do Typescript, matter.js makes it trivial to at least create a virtual matter device. Five minutes to clone the repo, build, run and pair with Google, Apple, Alexa, SmartThings, etc. The one caveat is certification. With Google you need to register as a developer so it allows an uncertified device. The others just give a warning.

See: https://github.com/project-chip/matter.js

Re: Matter 1.2 – New device types and improvements

#63
post #61

Is there a SIMPLE way to have a small python or go program act as a "switch" that shows up in Google home? The last time I tried looking at the matter stuff even checking out the git repo required gigabytes of storage and it seemed the opposite of simple.

If you can do Typescript, matter.js makes it trivial to at least create a virtual matter device. Five minutes to clone the repo, build, run and pair with Google, Apple, Alexa, SmartThings, etc. The one caveat is certification. With Google you need to register as a developer so it allows an uncertified device. The others just give a warning. See: https://github.com/project-chip/matter.js

oooh! that looks perfect. The main repo is a bit much, and much of the examples seem to assume you're running on bare metal embedded

I'd have preferred another language, but what I want to do is ultimately so simple that TS should be fine.

Re: Matter 1.2 – New device types and improvements

#64
post #61

Earlier quoted context omitted.

If you can do Typescript, matter.js makes it trivial to at least create a virtual matter device. Five minutes to clone the repo, build, run and pair with Google, Apple, Alexa, SmartThings, etc. The one caveat is certification. With Google you need to register as a developer so it allows an uncertified device. The others just give a warning. See: https://github.com/project-chip/matter.js

oooh! that looks perfect. The main repo is a bit much, and much of the examples seem to assume you're running on bare metal embedded I'd have preferred another language, but what I want to do is ultimately so simple that TS should be fine.

Yeah - you can even pass your own python, go, bash, etc. "on/off" script as a parameter to the example matter-device so you can get away with no code changes at all. You can get help at the listed discord server.

Re: Matter 1.2 – New device types and improvements

#65
post #64

Earlier quoted context omitted.

oooh! that looks perfect. The main repo is a bit much, and much of the examples seem to assume you're running on bare metal embedded I'd have preferred another language, but what I want to do is ultimately so simple that TS should be fine.

Yeah - you can even pass your own python, go, bash, etc. "on/off" script as a parameter to the example matter-device so you can get away with no code changes at all. You can get help at the listed discord server.

Well you were right, it took not even 5 minutes to get it working. Even with having to register it as a development device. Unfortunately as it turns out I don't have any devices that can act as a matter hub for google home, so after finding and adding the device, it ends up not being able to talk to it anyway :-(

Ironically I have 4 chromecasts, but they are connected to real amplifiers and speakers, so I never felt the need to get one of the smart speakers which can act as a hub.

Re: Matter 1.2 – New device types and improvements

#66
post #64

Earlier quoted context omitted.

Yeah - you can even pass your own python, go, bash, etc. "on/off" script as a parameter to the example matter-device so you can get away with no code changes at all. You can get help at the listed discord server.

Well you were right, it took not even 5 minutes to get it working. Even with having to register it as a development device. Unfortunately as it turns out I don't have any devices that can act as a matter hub for google home, so after finding and adding the device, it ends up not being able to talk to it anyway :-( Ironically I have 4 chromecasts, but they are connected to real amplifiers and speakers, so I never felt…

Yeah, you typically need some sort of hub unless you run Home Assistant. My understanding is that it doesn't need any hub for Matter support.

Re: Matter 1.2 – New device types and improvements

#68
post #39

It is still very hard to find matter devices. We wanted recessed downlights and ended up with Zigbee. My air conditioner just died, would be great if a matter compatible one became available.

What did you pick? I’m looking at the moment..

Hue -- it was the only option that felt 'mature' and well supported. We got a really great price on them and accept that we may swap them out in 3-5 years.

Re: Matter 1.2 – New device types and improvements

#69
post #59
post #39

Earlier quoted context omitted.

What did you pick? I’m looking at the moment..

I’ve been looking too, and the more research I do, the more it looks like the best idea is to get regular dimmable bulbs + zigbee dimmer switches - that’s generally going to be simpler and more reliable, the main downside being lack of any colour temperature / RGB support :(

We tried this first in one room and couldn't get the bulbs with the range that we wanted. Hue really stood out in how dark and bright they could get. The RGB also ended up being much more useful than we thought.

Re: Matter 1.2 – New device types and improvements

#70

It is still very hard to find matter devices. We wanted recessed downlights and ended up with Zigbee. My air conditioner just died, would be great if a matter compatible one became available.

> My air conditioner just died, would be great if a matter compatible one became available. What would you want the API to look like here? I would be very conservative about opening up an API if I was a manufacturer. The reason being that there may be misuses by amateur coders that may increase wear on the product, and leading to increase in warranty claims. I, as a manufacturer, would much rather prefer customers bu…

I want to be able to turn it on/off and set the temperature from Homekit. I can't imagine any fancy automation that would matter beyond that.

Saving money on this is not a priority for me. Ecobee already works with Homekit, I would gladly buy an ecobee AC that did the same.

Post reply on HN