As far as what end device to start with, you’re picking a very difficult one. I don’t know if that’s what you wanted.
The edge drivers which are easiest for community developers to create for are the ones for Zigbee or Z wave devices.
Sengled makes devices of different protocols. The Zigbee ones can connect directly to a smartthings hub and do use edge drivers.
The Wi-Fi ones, however, use a cloud to cloud integration. No edge driver. That’s true of most Wi-Fi devices with the exception of matter-Compatible ones. Which the model you linked to is not. (And, again, if it uses matter, it probably won’t need a custom edge driver.)
So I don’t know if you meant to link to a Zigbee model, in which case, sure, that might be a good starter device.
But for a nonMatter compatible Wi-Fi device, you have to check to see if it has an open API that you can get to you by LAN. THESE TEND TO BE CUSTOM TO EACH MANUFACTURER (AND SOMETIMES TO SPECIFIC MODELS), WHICH IS VERY ANNOYING, AND IS PART OF THE WHOLE IMPETUS FOR MATTER, TO GET RID OF THAT ISSUE. WITH ZIGBEE AND ZWAVE, THERE IS AN INDEPENDENT THIRD-PARTY STANDARD FOR COMMUNICATING WITH HOME AUTOMATION DEVICES. WITH WI-FI OTHER THAN MATTER, THERE IS NOT. (Sorry that’s all in caps, my dictation program flipped and I’m too tired to fix it.)
So… Were you looking for something easy or something hard? You didn’t say much about your technical background, so I’m not sure what direction this conversation needs to go in at this point.
Here’s the official schema for the new smartthings architecture. I’ve added the two text labels.
A) is how the current official sengled to smartthings Wi-Fi integration works.
To make it use an edge driver, you would have to shift it to B), and I don’t even know if it’s possible for that model. It might not be.
So, if you’re just looking for a “hello world“ kind of project, I think a different device would be better.
If you’re looking for something really challenging to show that you can fill a missing market niche, then it might be exactly what you want.