I want to support your evaluation of supporting the Shelly Plug Gen 3, at it do not need very much of a change to make it work.
Please forward this to a developer - as this is the solution (implementation time marginal) for my problem
Fact1:
Shelly introduced a new Generation 3 of the plug. Gen3 is supporting additional functions, but also support the old function of the Generation 2 (Gen2)
Fact2:
You are using data from the Shelly Cloud - there are two different Interfaces
--> Zendure added already the Generation 2 Interface ( Shelly Plus Plug and Shelly 3EM Pro )
Fact3:
The access of functions for API Access for Generation 2 and Generation 3 are equal
Fact4:
Very likely your programming interface is, that you are using - hint
--> Welcome! | Shelly Technical Documentation
"...Throughout the documentation the placeholder <shelly-id> is commonly used. It must be replaced by the corresponding shellydevicemodel-XXXXXXXXXXXX string, for example shellypro4pm-f008d1d8b8b8....
What Zendure is very likely doing, is filtering the device list from my Shelly Cloud connection about the models
--> And here is the opportunity where a Developer simply need to add
--> If we follow the example above - it is the deviceSSID - documentation for the 4PM above: https://kb.shelly.cloud/knowledge-base/shelly-pro-4pm-v2
--> the current Gen 2 Plug is identified (Device SSID) as - ShellyPlusPlugS-XXXXXX - https://kb.shelly.cloud/knowledge-base/shelly-plus-plug-s-v2
--> the new Gen 3 Plug is identified (Device SSID) as - ShellyPlugSG3-XXXXXXXXXXXX - https://kb.shelly.cloud/knowledge-base/shelly-plug-s-mtr-gen3
Solution: Add ShellyPlugSG3-XXXXXXXXXXXX as accepted device to the filter in your app (when you want to add it
in the App: Profile - More Services - Shelly - Authorize Device - Add (+)