GPIO ports for the grove connector?
-
@cerietke said in GPIO ports for the grove connector?:
Personally I wouldn't mind the MQTT only route as that's essentially how I'd be using them, however it would be nicer if it was built in.
It's not really about being nice to have but rather the benefit vs. time to develop, test and support this feature. Normally there is a discussion on Github or Discord (or this forum). Then if there is enough interest from the community we add a feature request on Github and see who can implement it.
Note that there are numerous other ideas and requests floating around, so this will take some time. The only way I see to expedite your request is to try coding this as a custom plug-in first...
If there were more core2 users of openHASP that could go faster but I don't see that currently. Maybe it's a bit like the chicken and egg problem. I might consider posting about openHASP in the Projects section to gauge interest.
-
For the M5Stack Core2, Grove Port A uses I2C on GPIO 21 (SDA) and GPIO 22 (SCL). However, when using a Pb.HUB, you're communicating with the hub over I2C, and each connected unit (like relays or RGB) is addressed virtually via the hub.
Since openHASP doesn't natively support Pb.HUB devices, you can’t directly control GPIOs through it. Instead, you’d need custom firmware or integrate via ESPHome or Arduino to bridge Pb.HUB control with openHASP.
TL;DR: GPIO 21/22 for I2C, but control of devices via Pb.HUB needs extra handling outside openHASP.
