Matter: Is there a HomeSeer technology roadmap or even a plan?

[ksum]

What is matterhorn lol?

can’t get a definition other than a mountain in Switzerland

According to Interesting facts about the Matterhorn

The Matterhorn has three common names. The German name Matterhorn derives from the words for “meadow” and “peak.” The Italian name (Cervino) and French (Cervin) likely originated with the Latin word for forest, silva, though some believe it comes from the Italian and French words for “deer.”

Anytime I think of The Matterhorn, I think of this:

[Sgt. Shultz]

"What is matterhorn lol?"

It is the peak you climb to shout your praises of the new protocol from...

[pistacheL0]

What is matterhorn lol?

can’t get a definition other than a mountain in Switzerland

[Sgt. Shultz]

If you wanted to tout the new protocol you would use your..., Matterhorn...

[joegr]

I think it just means you don't matter.

don't matter / doesn't matter

[kenm]

If you don't want to use the new protocol, does that make you..., anti-matter?

I think it just means you don't matter.

[Sgt. Shultz]

When people who are matter and people who are anti-matter come together it gets explosive...

You might even say they tend to annihilate one another...

[John245]

If you don't want to use the new protocol, does that make you..., anti-matter?

No.

In my case I currently see no use case to use Matter. And my roadmap for HomeSeer wiill cover a period of 3 years Time enough to see if at that time matter is mature.


---
John

[Sgt. Shultz]

If you don't want to use the new protocol, does that make you..., anti-matter?

[upstatemike]

I think you are making 2 assumptions here that aren't true -

1. The devices are using iPV4.
2. The IPV4 IP range is the same as defined on a homeowner's DHCP server and relies on that DHCP server.

IPV6 doesn't work anything like IPV4 in this regard. It can be deployed where you don't have to make decisions on network assignment or supply a DHCP server. Only one or a handful of gateway devices would need IPV4 and IPV6 assignments to bridge to your existing IPV4 network.

You are correct about my assumptions. This is why I keep poking at things until I eventually understand them.

[mterry63]

This info about Thread caught my attention:

"Every device on the Thread network gets an IP address, making it easier for a device to broadcast data to a local network or (optional) cloud without having Wi-Fi built in"

"And Thread's maximum number of devices, 250, is but a fraction of ZigBee's theoretical 65,000"

As folks move from switch based automation to bulb based solutions using options like Hue, they see the number of IoT endpoints increase exponentially. Even a moderately large house with lots of TVs, Sonos or other networked music devices, Alexa in every room etc. are quickly going to run out of IP addresses to build out their bulbs and switches. Why would a new standard design in such a low limit to expansion?

I think you are making 2 assumptions here that aren't true -

1. The devices are using iPV4.
2. The IPV4 IP range is the same as defined on a homeowner's DHCP server and relies on that DHCP server.

IPV6 doesn't work anything like IPV4 in this regard. It can be deployed where you don't have to make decisions on network assignment or supply a DHCP server. Only one or a handful of gateway devices would need IPV4 and IPV6 assignments to bridge to your existing IPV4 network.

[JimSpy]

Couldn't they think of a better name than "Matter"? What's the matter with them?

...and I include that corny joke to illustrate the ubiquity of the word "matter" in everyday language, which will lead to nothing but confusion. It's just going to make people...madder!

[Demusman]

just look at the solution we have to use now - jowie's plug in to talk to that dresden-elektronik bridge....what a cludge.

You don't have to use that plugin, HS has their own Zigbee plugin that works great.

[ksdehoff]

We've all been to this party before. I wish them luck and will watch from the sidelines with enthusiasm while we wait for the new ecosystem to shake itself out. I for one am sick and tired of paying into cloud services just to have my perfectly good hardware go tits up because its not making enough money for some corporate giant or well-funded start up. For sure zigbee is alot more immature and unreliable than zwave is - just look at the solution we have to use now - jowie's plug in to talk to that dresden-elektronik bridge....what a cludge. I've got a few hundred dollars in zigbee hardware thats all garbage

[kenm]

I can't say for sure, but one of the reasons products don't have an Ethernet port is because of the battery of compliance tests that are needed as soon as you connect a copper cable to a device. WiFi has an entire set of compliance tests that must be run and connecting anything more than a wall wart (that's safety testing, not RF compliance) requires another set of tests for both RF emissions and immunity to RF interference. If a device has an HDMI port, it likely also has an Ethernet port since it's the same set of tests.

Again, not saying this is the only reason for lack of hardwired devices, but it's one reason.