Zigbee has launched a dual-mode chip compatible with the Bluetooth protocol format, aiming to expand or advance its ecosystem. On the surface, this seems like a good strategy, but in reality, we have already attempted a similar approach in the early days of using proprietary 2.4G protocols. At that time, the 2.4G proprietary protocol was also compatible with Bluetooth, but ultimately, we marginalized it ourselves. The reason is that the 2.4G proprietary protocol was originally more efficient than Bluetooth because it did not have to follow the Bluetooth protocol stack, but instead adopted a custom design, akin to a native 2.4G communication protocol. This is similar to the relationship between the Android system and mini-programs: Android apps can run directly on the system, while mini-programs add an extra layer of encapsulation on top of the Android system. Although the custom 2.4G protocol may have been slightly cheaper than Bluetooth in terms of cost, with technological advancements, the cost difference between Bluetooth chips and 2.4G chips has become negligible. More importantly, after the 2.4G protocol became compatible with Bluetooth, its advantages were actually weakened. This is because the capabilities of the Bluetooth protocol stack are already sufficient, and Zigbee’s protocol algorithms are not more advanced than Bluetooth; all functions that Zigbee can perform can also be achieved by Bluetooth. In this situation, this compatibility design cannot gain an advantage in cost, nor can it surpass Bluetooth in performance, making it difficult to avoid the fate of marginalization.