M5 Stack Core2 questions

[cerietke]

I just came across your project and it very much seems to do what I have been looking for and thinking about creating (in much simpler form) myself. I'd of course like to save myself the time. I have a bunch of M5 Stack Core2's (M5s). I use NodeRED, but considering this all works through MQTT I doubt that will be a problem.

There are a few things I was planning to do that quickly going through the documentation I couldn't tell if they were possible:

• Would it be possible to set up openHASP to act as one simple button on just a touch?
  To elaborate: I am using the M5s in place of light buttons, I have one default action at a touch, which so far is just to toggle the nearby light. I'd like to still be able to do this, while having some way (say a (long) touch of a certain area) to get into the menu structure and control more devices. This both for convenience and so that other people can still control my lights just fine.
• A lot of extension modules are available for the M5s, I have some LED modules, motion sensors and relays. Could these still be used?
  To elaborate: the LEDs would be nice, but I can live without them, the motion sensors I was intending to use to track myself around my home and activate light accordingly (maybe eventually have music follow me too), they would be a greater loss, and the relays I really need to control some traditional lights and/or reset smart lights, I can't do without them.
• Can I control screen brightness through MQTT?

Thank for any insights you can give me!

A sample of how one of my M5s is set up:

[nagyrobi]

Answers quickly:

• yes
• leds and relays yes, sensors not yet, but hopefully soon
• yes

[cerietke]

I'm lost.

I've attached one of my old relays, have also tried LED unit and the newer relay,

I use MQTT Explorer for testing MQTT. I can get a state report bij sending this:

I can't seem to be able to get the state to on from MQTT. I have tried every variant I could come up with for the command t o send.

Next I set up a switch and coupled that to a group the GPIO pin is in. I can now see that the GPIO pin state changes actually get through, however, no effect on the connected relay or other module. Anybody any idea?

[cerietke]

I got some help on the M5Stack forums, however I am running into a wall. At this point when I reboot the relay is off, I can then turn it on, but I have not managed to turn it off again. My attempts can be found starting here: https://community.m5stack.com/post/16314

Any idea what might be the problem?

[fvanroie]

This sounds like this question.
Can you please post the serial log when you try to enable/disable a GPIO output?

[cerietke]

Isn't that in the screenshots in a later post there? If not, happy to try to provide it, but what exactly are you looking for/where do I get it from?

[fvanroie]

External links and screenshots of the logs actually make it harder to troubleshoot the issue in a quick manner.
You can copy/paste the serial or telnet log as text here on Github by clicking on the <> Insert as code icon:

MQTT RCV: hasp/lanbon_l8/command/output12 = {"state": "on"}
MSGR: GROUP 1 value 1 (0-1)
MQTT PUB: output12 => {"state":"on"}
MQTT RCV: hasp/lanbon_l8/command/output12 = {"state": false}
MSGR: GROUP 1 value 0 (0-1)
MQTT PUB: output12 => {"state":"off"}

Please try to send the {"state": false} message to output32.

[fvanroie]

@fvanroie said in GPIO ports for the grove connector?:

So I'm left thinking there is a bug in the command parser or the documentation isn't clear...

I can confirm that this problem is a parser bug. It currently only accepts unquoted boolean values of true/false or 1/0 instead of the usual range of: on/off, true/false, 0/1, yes/no which might be quoted or not.

This is particularly confusing since the state is always reported as on/off.

Thank you very much for bringing this issue to my attention. I have pushed a fix to GitHub and it is available for testing from the Actions tab and updated the documentation.

[cerietke]

I can confirm that state: true/false and 1/0 work for the relay I had connected and the version of the software I had loaded. As I am working right now I'm not going to rewire for the SSR relay or update the software (yet). I can potentially do that after work if there's a benefit to that.

[cerietke]

The SSR relay works as well.