I have been researching this product and I have got this information:
It works with the Alibaba IoT Platform
Locally it works with CoAP
It has an MXCHIP inside
It is not possible to capture and replay the tunOn/turnOff packets
I have recorded all the traffic about connection, authentication and communication but it seems that as tuya does, this platform uses a DeviceSecret to encrypt the data.
If someone wants to go forward researching about this just let me know.
I have studied also the possibility of replace the MXCHIP with a esp8266 but my knowledge about electronics is not so good to be able to understand how this circuit works if someone can help with this it would be awesome too.
Thanks for the information, I recently purchased an AigoStar QZA ceiling lamp and am trying to add it to HA as well. So far connecting to Google Home works great, but local support (similar to LocalTuya) would be great. I’m going to dig into it more but I’m not familiar with adding unsupported devices in HA.
nope, i sent an e-mail to aigostar [email protected] asking for any info about integration with home assistant or some access to the API.
The Tuya app works exactly like the Aigostar App so if they release the API it would be easy to make something to Home Assistant.
Maybe if more people sent e-mails they will look it up.
Hi, i also have this light, but since some progress was made on alternative firmware for Beken chips I would like to try out. @srborines how did you manage to open it. Can you take some images where clips are so i can open it. Thanks
I have a 60x60 cm panel and I scanned the ipaddress. It say’s philips hue a few times ?!? so maybe some one here has a hue setup to test if they get it working with that.
Scanning 192.168.0.214 [1 port]
Completed ARP Ping Scan at 21:52, 0.27s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 21:52
Completed Parallel DNS resolution of 1 host. at 21:52, 0.00s elapsed
Initiating SYN Stealth Scan at 21:52
Scanning mxchip.lan (192.168.0.214) [65535 ports]
SYN Stealth Scan Timing: About 12.71% done; ETC: 21:56 (0:03:33 remaining)
SYN Stealth Scan Timing: About 26.14% done; ETC: 21:56 (0:02:52 remaining)
SYN Stealth Scan Timing: About 39.66% done; ETC: 21:56 (0:02:18 remaining)
SYN Stealth Scan Timing: About 52.97% done; ETC: 21:56 (0:01:47 remaining)
SYN Stealth Scan Timing: About 65.74% done; ETC: 21:56 (0:01:19 remaining)
SYN Stealth Scan Timing: About 79.12% done; ETC: 21:56 (0:00:48 remaining)
Completed SYN Stealth Scan at 21:56, 228.98s elapsed (65535 total ports)
Initiating Service scan at 21:56
Initiating OS detection (try #1) against mxchip.lan (192.168.0.214)
NSE: Script scanning 192.168.0.214.
Initiating NSE at 21:56
Completed NSE at 21:56, 0.02s elapsed
Initiating NSE at 21:56
Completed NSE at 21:56, 0.00s elapsed
Initiating NSE at 21:56
Completed NSE at 21:56, 0.00s elapsed
Nmap scan report for mxchip.lan (192.168.0.214)
Host is up (0.036s latency).
All 65535 scanned ports on mxchip.lan (192.168.0.214) are closed
MAC Address: 04:78:63:C3:6F:9D (Shanghai Mxchip Information Technology)
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed ort
Device type: specialized|general purpose
Running: DTE embedded, lwIP 1.4.X, Enlogic embedded, Ocean Signal embedded, Philips embedded
OS CPE: cpe:/a:lwip_project:lwip cpe:/h:philips:hue_bridge cpe:/a:lwip_project:lwip:1.4
OS details: DTE Energy Bridge (lwIP stack), Enlogic PDU (FreeRTOS/lwIP), Ocean Signal E101V emergency beacon (FreeRTOS/lwIP), Philips Hue Bridge (lwIP stack v1.4.0)
Network Distance: 1 hop
