Actions
Forum Thread Details
  • Replies 6 replies
  • Subscribers 535 subscribers
  • Views 1030 views
  • Users 0 members are here
Related

Matter\Thread and programming languages

user4517

I've settled on using Python for many of my projects. Python gets support for MCU platforms, but it's patchy and C is already identified as the default language for CSE Matter\Thread (with no mention of other languages). I'm curious to hear what others believe will occur with Python support for Matter\Thread and if the power players (Amazon, Google, etc.) will build solutions that go beyond what will be offered in Python libraries and services (mostly being developed by community members). The power players will likely provide wrappers for their Matter services, but I doubt they will provide the level of local control that is stated in the CSE Matter agreement.

Will hobbyist be able to keep up with Matt\Thread and keep a local control model?

Will embedded Python (e.g., microPython and CircuitPython) keep up with the new standard in a timely manner while keeping local control an option? Will we end up with Python libraries that wrap around power player libraries and services leaving local control in the dust?

I hope local control is preserved with Matter\Thread and I hope that language diversity is possible that encapsulates the full standards.

Parents Reply
  • in reply to robogary

    Hi Gary,

    That's a good article. I just didn't understand what the CSE Agreement was that was being referred to. 

    For what it's worth I'm not a fan of (old) Zigbee, but any attempt to make it more useful by carrying IP is a good thing.

    Normal old Zigbee was (and still is) very popular with manufacturers (more than consumers perhaps!) because it had some built-in security (although that didn't help with interoperability : ( forcing users to use gateways or APIs) whereas BLE didn't define such a security layer.

Children
  • in reply to shabaz

    I believe Thread is a direct improvement to Zigbee since that was the basis. Z-wave has not engaged with the Matter group so I'm not sure what will happen with it. At least they recognize use of the 900mHz spectrum while supporting 2.4gHz and Bluetooth (sort of).

    My real concern is that giving all objects an IPv6 address will lead to a dominance of cloud services wanting to talk directly to these objects like Amazon and Google do today. It's much harder to prevent direct access when IPv6 is used, but I agree IP base solutions are preferred.