Replies: 4 comments 26 replies
-
Furthermore, when I try to connect via the GHSAFM-TC Android app (found under one of the Google developer doc), the app just hang and report "Something went wrong" From Tasmota console...
|
Beta Was this translation helpful? Give feedback.
-
Please try again with latest version. Also make sure that Tasmota is on the same LAN than your app and your gateway |
Beta Was this translation helpful? Give feedback.
-
Update. Was busy earlier, and finally have time to test 13.2.0.2. It works much better, very close to my expectation. I was even able to add another ESP8266 based Tasmota device to the ESP32 Tasmota that I was testing Matter. I was able to see all the switches (and one temp reading too). Except, one of the switch was showing offline in Google home, but it works the whole time on the ESP32 main screen. I have a feeling is during the matter connection phase, if there is some sort of timeout, it will remain offline in Google home. I will have to experiment it more to see what's the cause. I have even tried briefly, using Google home (on my phone), disconnected from my home network, and I was still able to control it. |
Beta Was this translation helpful? Give feedback.
-
I am still having this problem even running tasmota 14.4 |
Beta Was this translation helpful? Give feedback.
-
I am very excited about the Matter integration, especially with ESP32 it acts as a bridge to older ESP8266 Tasmota devices (provided upgraded to 13.0.0)
However, I am unsure if I have misunderstood how it works or if something is missing. After following the instructions here I was able to add my ESP32 Tasmota device under Google Home, it has knowledge about my other ESP8266 Tasmota devices. But that's where it ends. Other than the Matter bridge, everything shows as offline.
Also, is it possible to name my "bulbs" and "outlets"?
The two "outlets" are the relays on Sonoff Dual R3.
The other two "bulbs" are each ESP8266 Sonoff.
Beta Was this translation helpful? Give feedback.
All reactions