I have just finished building a Modkam V4. I have tried both FW and on these two versions I lose connectivity with my Tuya based devices. I have cloned the ieee address of my Modkam V3 Alternate which works perfectly fine with all my devices including Tuya ones. But as soon as I put the Modkam V4, I start to get error message that it cannot ping them. Also it is impossible to repair them.
As soon as I put back my Modkam V3, I get connectivity back. This is really strange, I already had this issue with some FW for the original version of Modkam V3, and they disappeared when I switched to the Alternate version. Now I see the same problem coming back again with :
-Modkam V4
-Sonoff USB 3.0 plus
I've tried all the latest FW on all these devices and I see the exact same behavior on all of them.
-I first loose connectivity to specific class of devices : Tuya plugs, Tuya Remote 3 buttons and Blitzwolf SHP13
-I cannot repair them, the interview of the Tuya plugs fails after Timeout, the Remote control does not even start the interview (no log at all as if it was emitting in a wrong frequency).
-All Xiaomi devices work totally fine with all FW versions, and all coordinators I tested
-As soon as I plug back my Modkam V3 Alternate, I regain connectivity to all Tuya devices, and I can totally repair them, interview never fails.
As I said, I already had this issue with previous versions of FW on the Modkam V3 original version.
What can cause such a behavior inside the FW so that it cannot connect specific class of devices. Is there a frequency range setting or a code multiplexing protocol compatibility ? It is really really strange that these exact same devices come back to life as soon as I plug a Modkam V3 Alternate version.
Coordinator hardware seems out of the equation as I have the exact same behavior with Sonoff USB 3.0 Plus and Modkam V4, except if the issue is coming from TI chip itself.
I don't understand how the FW can affect the ability to conduct proper transactions with the devices (ping, interviews...). I must be missing something.
Hi there
I have just finished building a Modkam V4. I have tried both FW and on these two versions I lose connectivity with my Tuya based devices. I have cloned the ieee address of my Modkam V3 Alternate which works perfectly fine with all my devices including Tuya ones. But as soon as I put the Modkam V4, I start to get error message that it cannot ping them. Also it is impossible to repair them.
As soon as I put back my Modkam V3, I get connectivity back. This is really strange, I already had this issue with some FW for the original version of Modkam V3, and they disappeared when I switched to the Alternate version. Now I see the same problem coming back again with : -Modkam V4 -Sonoff USB 3.0 plus
I've tried all the latest FW on all these devices and I see the exact same behavior on all of them. -I first loose connectivity to specific class of devices : Tuya plugs, Tuya Remote 3 buttons and Blitzwolf SHP13 -I cannot repair them, the interview of the Tuya plugs fails after Timeout, the Remote control does not even start the interview (no log at all as if it was emitting in a wrong frequency). -All Xiaomi devices work totally fine with all FW versions, and all coordinators I tested -As soon as I plug back my Modkam V3 Alternate, I regain connectivity to all Tuya devices, and I can totally repair them, interview never fails.
As I said, I already had this issue with previous versions of FW on the Modkam V3 original version. What can cause such a behavior inside the FW so that it cannot connect specific class of devices. Is there a frequency range setting or a code multiplexing protocol compatibility ? It is really really strange that these exact same devices come back to life as soon as I plug a Modkam V3 Alternate version.
Coordinator hardware seems out of the equation as I have the exact same behavior with Sonoff USB 3.0 Plus and Modkam V4, except if the issue is coming from TI chip itself.
I don't understand how the FW can affect the ability to conduct proper transactions with the devices (ping, interviews...). I must be missing something.