Adventures with Matter protocol on Tasmota #17872
Replies: 84 comments 336 replies
-
|
This next message keeps track of what's already implemented, what's missing and what will not be implemented: What is already implemented:
What's not yet implemented:
Not in scope
|
Beta Was this translation helpful? Give feedback.
-
|
This looks great! I got it running on my ZigbeeBridgePro but then read there is not yet support for bridge mode. Any idea when this might be coming? :) |
Beta Was this translation helpful? Give feedback.
-
|
It's too early for bridged mode. We're still focusing on simple devices. But indeed bridged mode will be interesting to connect all ESP8266 devices as well. |
Beta Was this translation helpful? Give feedback.
-
|
Good to know thanks, can't wait to try it out when it comes. In the mean time i'll try it out on some non bridged devices. I saw that Google home lets you scan a matter barcode now, interested to see if it lets you control devices directly. |
Beta Was this translation helpful? Give feedback.
-
|
Here what it looks like with The chip-tool command is:
|
Beta Was this translation helpful? Give feedback.
-
|
What is "0x7283" ? |
Beta Was this translation helpful? Give feedback.
-
|
It's the identifier-id assigned to the node. It can be almost any 32bits number. You just can't have two nodes with the same id. This value is just random |
Beta Was this translation helpful? Give feedback.
-
|
Tip: If and when come to the point that want to test both commissionings a Tasmota Matter device inside some other open-source Matter Server/Controller implementations and/or testing to commission other virtual Matter devices inside Tasmota then check out these projects: node-matter (Matter protocol client / server for node.js) Home Assistant (Matter integration with Matter protocol client / server ) PS: Note that both node-matter and Home Assistant have the ability to act as either a Matter server/controller or a client (or both). |
Beta Was this translation helpful? Give feedback.
-
|
I tried generating a new Certification Declaration with device_type_id=0x0100 but it fails the same way |
Beta Was this translation helpful? Give feedback.
-
|
One user had success with uninstal/install Alexa App but me not so far. It wooulf maybe a try to downgrade ALexa App to the version from end december ... we did succesfull tests on 8.1. roughly and there such a december version was current. But ok "good to hear" that I'm ot the only one affected. BTW: node-matter Hithub version controller should at least du susccessfull commisioning! |
Beta Was this translation helpful? Give feedback.
-
FYI, Home Assistant posted a new blog post with a status update regarding its Matter support, and in summary, they have done big updates to their documentation on Matter, (and the next upcoming release version (Home Assistant core 2023.3 will also get experimental integration support for Thread Border Router in Home Assistant) https://www.home-assistant.io/integrations/matter https://www.home-assistant.io/blog/2023/02/08/state-of-matter-and-thread/ https://www.home-assistant.io/blog/2023/02/08/state-of-matter-and-thread/#matter https://www.home-assistant.io/blog/2023/02/08/state-of-matter-and-thread/#thread |
Beta Was this translation helpful? Give feedback.
-
|
Yes, and Home Assistant added a note which highlights a need of Matter which is a big problem in not small or secured LANs. -> mDNS
|
Beta Was this translation helpful? Give feedback.
-
|
And will produce all lots of fun with docker :-) |
Beta Was this translation helpful? Give feedback.
-
|
What are the system requirements (e.g., MCUs)? |
Beta Was this translation helpful? Give feedback.
-
|
No, not ESP8266. What might become feasible would be for one ESP32 device with Tasmota to act as a gateway to Matter, for multiple ESP8266 devices. |
Beta Was this translation helpful? Give feedback.
-
Matter devices use BLE for commissioning. ESP32-S2 does not have Bluetooth. Will an ESP32-S2 board able to be configured as a working Matter accessory when flashed with the Tasmota32 MATTER version? |
Beta Was this translation helpful? Give feedback.
-
|
In Matter, BLE is optional and mostly used to configure the Wifi credentials with a mobile app. This is not needed in Tasmota that has its own way of configuring Wifi. We don't support BLE commissioning in Tasmota, because the BLE code from esp-idf is too large. We only support "on-network" commissioning. This means that the device is already on the Wifi network, and BLE is not needed. Matter on Tasmota does work on ESP32-S2. But be aware that S2 has less memory, hence more limited. Especially using ESP32-S2 as bridge would not be viable. |
Beta Was this translation helpful? Give feedback.
-
|
If I understand correctly, that means that a Tasmota Matter device cannot be configured right from the start by the final user like a commercial device just by flashing a QR code or entering a passcode directly in the user's home automation mobile app (e.g. Apple Home); the user must first open the Tasmota control panel, choose his SSID and enter his Wi-Fi credentials first, before he can finally add the device to his mobile app? Thanks for the warning about memory. I ordered a LOLIN S2 MINI development board but also a LuatOS ESP32 C3-CORE that will be more suitable for tests than the S2 I think. I also ordered an ESP-C3-12F (C3FN4, 4MB) chip that I plan to try on a MOES Rotary dimmer, unsoldering the incompatible WB3S chip in it. I know the Tasmota firmware for Matter is specific. Can you tell me if the code for the configuration is the same as for versions swapped with an ESP8266 (configuration code described on the Tasmota template page for that device)? I will then test it in the Apple Home app. I will report my findings here for the community. |
Beta Was this translation helpful? Give feedback.
-
Right. Matter for Tasmota is designed to be an extension of Tasmota. We don't plan to have Matter-only devices. For this you can use esp-matter or other on-the-shelf solutions. Also we don't have plans to have Tasmota Matter-certified, since this would be needed for each hardware device. ESP32C3 and ESP8266 templates are different, but it should be easy to remap the pins to ESP32C3. |
Beta Was this translation helpful? Give feedback.
-
|
@Apollon77 a warm welcome here Mr. ioBroker ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, didn't know I earned that name ;-) |
Beta Was this translation helpful? Give feedback.
-
|
just a little bit working with iobroker in the past makes your name weirdly familiar 😆 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Oh. You also need |
Beta Was this translation helpful? Give feedback.
-
|
Maybe this is need too: |
Beta Was this translation helpful? Give feedback.
-
|
It's not necessary. Matter support does enable the needed mdns pièces |
Beta Was this translation helpful? Give feedback.
-
|
Home Assistant and Chip Tool.
Google Home fails |
Beta Was this translation helpful? Give feedback.
-
|
Good. Do you have the Tasmota logs of Google Home failing? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for bringing matter into Tasmota. I was waiting patiently this to happen. When can I expect a berry example to add matter support to custom device? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your kind message. It will probably require a month or two. |
Beta Was this translation helpful? Give feedback.
-
|
I have designed two esp32 devices, basically switches. One is 4 Gang Switch and another one is 4 Speed Fan control. Both the device drivers are written in berry. |
Beta Was this translation helpful? Give feedback.
-
|
No luck connecting to Home app 16.3.1. FYI. 00:00:00.002 HDW: ESP32-D0WDQ6 |
Beta Was this translation helpful? Give feedback.
-
|
Only work with chip-tool
|
Beta Was this translation helpful? Give feedback.
-
|
I finally got chip-tool compiled on MacOS after a few false starts. They have a few relevant script bugs. Can you help me with the command line for chip-tool for a Tasmota device over WiFi? I can't quite figure it out from the chip-tool Wiki.
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Change ip address |
Beta Was this translation helpful? Give feedback.
-
|
./chip-tool pairing ethernet 0x7283 20202021 1021 192.168.1.122 5540 [1676340404302] [56522:171048869] [TOO] Unknown command: ethernet +-------------------------------------------------------------------------------------+ pairing is not a command with ethernet? fresh git pull. tried everything I can think of without luck. |
Beta Was this translation helpful? Give feedback.
-
|
They may have changed the commands. It should be |
Beta Was this translation helpful? Give feedback.
-
|
Commissioning success. Session established. Nice work!
./chip-tool pairing onnetwork 0x7234 20202021
Kevin
… On Feb 14, 2023, at 2:53 AM, s-hadinger ***@***.***> wrote:
They may have changed the commands. It should be onnetwork, try to get the options for this command
—
Reply to this email directly, view it on GitHub <#17872 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4WTTCXMFFFGFQ6M5ZQUUTWXM2WRANCNFSM6AAAAAAUQYNQYQ>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
I wonder if this will ultimately become a blocking factor, where let's say Apple does not allow uncertified matter products to be added to their home app and the only way would be is to have it certified in order to get a valid cert. Matter is good for manufacturers, not for the DIY community. |
Beta Was this translation helpful? Give feedback.
-
|
From what we know is that the "Matter alliance" decises to allow uncertified devices to be added when the user is "asked". So Apple does it that way already and I would assume it stays that way. Google is a bit more complex to allow it but also possible and ALexa works too. |
Beta Was this translation helpful? Give feedback.
-
|
I use DIY HomeKit accessories from ESP8266 devices flashed with the HAA firmware (esp-homekit) and would like to try the Matter implementation of Tasmota with ESP32 devices. I can confirm that, from the Apple side of things, there is a warning in the Apple Home app that pops up when one tries to add such a "non approved" HK accessory, but the user just has to acknowledge the message and proceed with no error or issue afterward. It's a simple two-step process (clicking + to add a device, then flashing QR code or type the device passcode, and voilà). |
Beta Was this translation helpful? Give feedback.
-
|
Google requires that you first register the VendorID/DeviceID in your Google Home Dev console. |
Beta Was this translation helpful? Give feedback.
-
|
Let us hope the do for Matter as the do for Homekit. The allow. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed. The certification scheme is clearly not well suited for DYI. |
Beta Was this translation helpful? Give feedback.
-
|
Reverse proxy. And easy Google Assistant / Alexa integration. |
Beta Was this translation helpful? Give feedback.
-
|
Sells zigbee matter dongle "SkyConnect" |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestions. But we don't plan to make a business out of Tasmota. It's still a hobby project for the contributors. We'll explore some options. |
Beta Was this translation helpful? Give feedback.
-
|
0xFFF1, 0xFFF2, 0xFFF3 and 0xFFF4 are Test Vendors. The Test Vendor IDs are reserved for test and development by device manufacturers or hobbyists. Commissioners SHOULD NOT commission devices using one of these VIDs onto an operational Fabric under normal operation unless the user is made fully aware of the security risks of providing an uncertified device with operational and networking credentials. I've recently read the Matter specs and one of the notes was the one above. I don't think they would restrict devices but the user will be notified about it, which I personally don't mind. |
Beta Was this translation helpful? Give feedback.
-
FYI, Kodi/XBMC is not a company, Kodi/XBMC is still a profit hobby project with only unpaid volenteers, but with their foundation being a legal entiry does open some doors that otherwise would be closed. |
Beta Was this translation helpful? Give feedback.
-
|
There are some major improvements with the latest PR:
Multi-fabric is not yet supported, this is still a blocking point for Google/Apple compatibility. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the new logging format. Below is a commissioning done with chip-tool: |
Beta Was this translation helpful? Give feedback.
-
|
The current code size increase for Matter is 209KB. It will continue to increase moderately. |
Beta Was this translation helpful? Give feedback.
-
|
Testing with 2 same esp32 2 relay devices, both devices have same template.. I compiled with #define USE_MATTER_DEVICE Web installer works fines and shows "Current Configuration" field. I don't understand why my own build didn't work while the web installer worked perfect. 
|
Beta Was this translation helpful? Give feedback.
-
|
This commits fixed https://github.com/arendst/Tasmota/tree/31b93f8d4820c51431911a97d80bdfc34c334c0e thanks |
Beta Was this translation helpful? Give feedback.
-
|
Is this a typo ? _X20and_X20condiguration vs _X20and_X20configuration |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thanks for the fix. |
Beta Was this translation helpful? Give feedback.
-
|
version number not updated? still Tasmota 12.5.0.4 by Theo Arends |
Beta Was this translation helpful? Give feedback.
-
|
No, we don't change the version number for each fix. |
Beta Was this translation helpful? Give feedback.
-
|
After having flashed a new build, you can see update level (timestamp) in |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the great job ! I'm using an ESP32 with a BH1750 attached. The luminance is working well on Tasmoata Device, and is published as a accessory Matter (iOS 16.5). But when the luminance shows 152 lux on Tasmota : on iOS Home app, it shows only 1.04 lux : Is there a know bug ? |
Beta Was this translation helpful? Give feedback.
-
|
TSL2591 or TSL2561 does provide low luminosity decimals. While I haven't made a calibration-style check, with TSL2561 I do see plausible values increasing from zero in steps around 0.01 lux in the early dawn (resolution 0.001, but I'd not expect the accuracy being that good). Neither of these included in default precompiled builds. |
Beta Was this translation helpful? Give feedback.
-
|
do you have an idea how to do such a calibration? |
Beta Was this translation helpful? Give feedback.
-
|
I've not got much calibration info, without a good reference to compare to. And most "environmental" references can vary a bit depending on details. My view on those cheap sensors is that I'm not so much looking for a "lab" measurement to make a claim that I know the "real" value, but instead something allowing me to see a reasonable range of change across normal conditions, which for a luminosity sensor obviously goes from darkness to full daylight, with a reasonable progression in between. My expectation is that those TSL sensors are better than messing with a LDR and calibration of that.... |
Beta Was this translation helpful? Give feedback.
-
|
I pushed a new fix to conform to spec. But considering |
Beta Was this translation helpful? Give feedback.
-
|
@macjl See #18847, I'm actually fixing the formula so it's close enough to the standard, but also usable for low lux values. Just substract |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
There is a new version with reduced logs and polished UI, allowing to add/remove endpoints without rebooting. Here is for reference a pairing of a simple ESP32C3 with RGB led, from an iPhone/AppleTV: |
Beta Was this translation helpful? Give feedback.
-
|
Testing your Matter 2023-06-13T21:41:02 build on Google home now. I have one remote Tasmota relay and one remote OpenBeken LED strip as well as a temperature sensor in the ESP32. Seems to be working fine! I was able to rename and move the devices around the Google Home with no issues. It was a bit confusing what to enter into the Google Home Dev pages for a gateway device and the two remotes. But Google does not seem to really care what is on that page and gets it config from the Matter pairing steps. The querying of the remote devices by the Matter bridge worked fine, though I did readjust the device 'types' after the initial automatic query. Again, great work, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this. Indeed the Google console is only useful to declare de vendor/device ids. Do you have more information on how the bridge wrongly detected remote devices ? |
Beta Was this translation helpful? Give feedback.
-
|
@s-hadinger @openshwprojects I let the 12.5.0.4(matter) 2023-06-06T17:41:20 run for several days with the OpenBeken device all attached to Apple HomeKit. It has been solid, responsive to HomePods voice requests. A simple case I'm sure, but I am very happy and impressed by your work. I will move forward and try your newer build of the Gateway and will try and write up my experiences with some Apple and Google and a bit more complex a setup. Again, thank you for your fine and useful work! |
Beta Was this translation helpful? Give feedback.
-
|
I flashed from web installer. {"NAME":"Test3","GPIO":[33,0,0,0,32,576,0,0,0,0,0,34,0,0,258,257,0,0,0,256,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1} With alexa, only the 1st relay is visible, the 2nd and 3rd relays are not. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure I captured everything but this is everything that was in the console.
These are the screenshots I was able to take in the Google home app. 1st there are the 4 devices that quickly get removed to just the one device under "in your home" |
Beta Was this translation helpful? Give feedback.
-
|
I don't see anything wrong in the logs, I will try on my side. |
Beta Was this translation helpful? Give feedback.
-
|
It's all working fine on my side, on iOS with Nest mini. The only thing is that I need to restart the Google Home app to make display of new devices to appear faster. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible that a particular template could cause this bug? I've been playing around more with this and have gotten it to work with the esp32-devkit template but as soon as I set it to use the linkind dimmer switch template found here https://templates.blakadder.com/linkind_WS2400101.html I get the issue I mentioned before. |
Beta Was this translation helpful? Give feedback.
-
|
It does not sound plausible but who knows |
Beta Was this translation helpful? Give feedback.
-
|
Guys, My idea was create 8 dummy switches using tasmota matter in a esp32 and pair them with Homekit and Alexa. If I setup first in Alexa, comission OK, but gets just the First Relay. There is some limitation in Alexa to multiple gang switches? Because im not getting this right. Im from brazil, sorry for the bad english. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I've not tried Alexa yet, only HomeKit and Google Home. But as I understand if from reading this thread, you are correct Alexa only support one 'device' currently. |
Beta Was this translation helpful? Give feedback.
-
|
Alexa currently only supports 1 device, only on endpoint 1. |
Beta Was this translation helpful? Give feedback.
-
|
@ad-borges Off topic. |
Beta Was this translation helpful? Give feedback.
-
|
@Jason2866 Sorry. Deleted |
Beta Was this translation helpful? Give feedback.
-
|
Sunday 2023-Jun-25, not finding a Tasmota32 Matter build here???? https://github.com/Jason2866/Tasmota-specials/tree/firmware/firmware/tasmota32/other FYI as well , someone should check the links at the main Tasmota github as well, this leads to a 404: https://github.com/arendst/Tasmota-firmware/tree/main/release-firmware |
Beta Was this translation helpful? Give feedback.
-
|
@deepcoder The "standard" development builds do include matter by default since last week. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. It doesn't harm to have an aggregator endpoint. Why would you want to change anything else? |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm, Just followed this advise how to check whether bridge mode is used. |
Beta Was this translation helpful? Give feedback.
-
|
This advise is outdated, it was only to distinguish between two versions. I'm repeating myself again: THE ONLY DIFFERENCE is the DeviceTypeList. |
Beta Was this translation helpful? Give feedback.
-
|
Just flashed the 13.0.0.1-2023-06-28T13-02-19 firmware and am starting to test. A couple items right out of the gate. Wiped out existing configuration in Google, turned off Matter on Tasmota32, deleted '_matter_device.json. Rebooted and flashed. Just a RGB LED and DS18 temperature physically on the ESP32 gateway device. SetOption8 1 applied for fahrenheit I added to Google first, added fine, however only the one 'device' added. No Gateway, Not LED, no temperature. The device that added came up as just a RGB Light. I was able to rename it and add it to a room. Synced Google Home and was able to iOS and voice commands to Google Hubs to control light. Then for kicks, I decided to try and add to Apple HomeKit. Turned reopened commissioning on the Tasmota32 bridge and then went to iOS and in HomeKit added a device. It worked!!!!! HomeKit added three devices, bridge, light and temperature. I was able to renamed all three and place them in a room. I am able to control the light from iOS and by voice via HomePods. Apple reports the correct temperature in fahrenheit, matches what is displayed on the Tasmota32 web page. Changes devices on HomeKit reflect in Google Home and the opposite as well. And you have to like this, even though Google Home did not show adding the temperature device and it does NOT show up on the iOS Google Home app, if I ask the Google Home speakers what the 'Den Temperature is', it tells me the temperature. However it reports the temperature in celsius! And it tells me the state of the light in the den as well. if I ask Google for the state of den light, it tells me the light state, but does not report the temperature. I will continue to test and see how robust this release is. Thank you again for your work and help! Let me know if I can report an think of use to you. |
Beta Was this translation helpful? Give feedback.
-
|
This is weird. Thanks a lot for your feedback. It definitely sounds like a bug in the Google iOS app. |
Beta Was this translation helpful? Give feedback.
-
|
Nothing has changed in Matter. The way it is included in standard Tasmota32 is the same as it was in the extra matter Tasmota32 version. So it is a coincedence. |
Beta Was this translation helpful? Give feedback.
-
|
@Jason2866 I don't understand why there is not a 'standard Tasmota ESP32 latest development' image here???? Everything else, however no 'standard'. I am trying to test your Matter implementation, there used to be a specific image for this. However, as you relayed to me, this has been integrated into the 'standard Tasmota32'. Well, that is what I want to test! Thanks for your work and help, give me a straightforward set of steps to download this latest build of the 'standard Tasmota32' image. |
Beta Was this translation helpful? Give feedback.
-
|
It is included in all tasmota32 builds starting with v13. |
Beta Was this translation helpful? Give feedback.
-
|
@darkxst Thanks for your reply, the whole Tasmota web environment is in need of a bit housekeeping, and that is not good for the 'average using' IMHO. I was able to find the latest 'standard' development build at this link: however, at this link: https://github.com/Jason2866/Tasmota-specials/tree/firmware/firmware/tasmota32/other there is no tasmota32.bin . I am trying to not introduce other variables. IMHO, the average user that want to expose a Tasmota device to Matter does not want to first face the 'wall' of all the other options in Tasmota... |
Beta Was this translation helpful? Give feedback.
-
|
The average user is probably using the Web Installer or at the very least the official repos. All of which will come with Matter now. |
Beta Was this translation helpful? Give feedback.
-
|
Standard development builds are specifically not to to be found in Tasmota-specials, but in http://ota.tasmota.com/tasmota32/ You also have both development, release and "unofficial" special builds here: |
Beta Was this translation helpful? Give feedback.
-
|
The behavior has changed in Tasmota 13. When I now add my Matter accessory to Apple Home, it needs to create a bridge first, then the accessory itself. My accessory is a single light, the additional bridge adds unnecessary clutter to HomeKit. |
Beta Was this translation helpful? Give feedback.
-
|
Message to all. Matter has now achieved official support since Tasmota v13. This discussion was exploratory, and it's getting too long. I am now closing this discussion. New questions or discussions around Matter needs to happen on new (and shorter) discussions. Thanks to all, it's been fun. And it's only the beginning! |
Beta Was this translation helpful? Give feedback.
-
|
Should Tasmota Matter also work with Samsung SmartThings? I can not get it to work. It won't connect successfully: 
|
Beta Was this translation helpful? Give feedback.
-
|
Did you get it to work in the end? |
Beta Was this translation helpful? Give feedback.
-
|
No. I used Edge Tasmota to connect it with Smartthings. |
Beta Was this translation helpful? Give feedback.
-
|
Ok thanks. That's what I'm using now but liked the idea of using Matter - everything else Matter I've tried runs well with ST. Had seen another guy on the ST community site. |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know how to use the virtual contact sensor to match the status of a real relay? |
Beta Was this translation helpful? Give feedback.
-
|
Please open a new discussion, and provide more information about what you are trying to achieve |
Beta Was this translation helpful? Give feedback.
and others
-
The time has come! Tasmota support for Matter protocol is progressively building. This thread will allow you to follow progress.
This first milestone implements device commissioning over Wifi. It works with the reference tool
chip-toolbut is not yet validated on Alexa and not tested on iOS.To compile you need to add
#define USE_MATTER_DEVICE. Once compiled with Matter support, you need to doSetOption151 1to enable Matter support, or use the WebUI. The code is almost entirely in Berry code solidified in Flash, the impact on RAM is very low.Tasmota is constantly in Provisioning Mode. When pairing Tasmota, you will need either the Manual Pairing Code (11 digits) or the QR Code:
Beta Was this translation helpful? Give feedback.
All reactions