Payload b'ON' does not relate to configured on/off values about mqtt-io

[CWempe]

Never mind.
I used the wrong module stdio instead of raspberrypi.

[CWempe]

After #13 and #15 were fixed, I retried this.

The issue occures with raspberrypi, too.

config

mqtt:
  host: localhost
  port: 1883
  user: "***"
  password: "***"
  topic_prefix: test

gpio_modules:
  - name: raspberrypi
    module: raspberrypi

digital_outputs:
  - name: lights
    module: raspberrypi
    pin: 21
    on_payload: "ON"
    off_payload: "OFF"

output

MQTT client: Received PUBLISH (d0, q0, r0, m0), 'test/output/lights/set', ...  (2 bytes)
Received message on topic 'test/output/lights/set': b'UP'
Payload b'UP' does not relate to configured on/off values.
MQTT client: Received PUBLISH (d0, q0, r0, m0), 'test/output/lights/set', ...  (4 bytes)
Received message on topic 'test/output/lights/set': b'down'
Payload b'down' does not relate to configured on/off values.
MQTT client: Received PUBLISH (d0, q0, r0, m0), 'test/output/lights/set', ...  (4 bytes)
Received message on topic 'test/output/lights/set': b'DOWN'
Payload b'DOWN' does not relate to configured on/off values.

[flyte]

I believe I know why this happens - the old Python 3 string/bytes mismatch. I'll issue a fix shortly. Thanks for another bug report!

[flyte]

@CWempe Please could you try with version 0.0.11 and reopen if it's not fixed. Cheers!

[flyte]

If nothing else, the new log message should provide better information now, if it's not fixed.