Beiträge von randomname2

  • Latest firmware for Dimmer 2 broke MQTT integration

    Thank you for testing this and reporting back. With the `20210323-110106/v1.10.1-gf276b51` firmware everything is indeed working great again (this is the one I reverted back to with the help of your tool). Swapping the brightness and turn properties does not seem to matter for this firmware version, as I would expect. The brightness is applied though, even with turn set to "off", but the brightness has to be >= 1 and =< 100 for this to work.

    However, the `20210415-131442/v1.10.3-g23074d0` firmware was giving me issues, so I'm holding back on any that specific firmware update until the issue is fixed in a newer firmware (I'm on the lookout for a firmware release newer than `20210415-131442`).

  • Latest firmware for Dimmer 2 broke MQTT integration

    Since I've upgraded my Shelly Dimmer 2 to firmware 20210415-131442/v1.10.3-g23074d0 the MQTT interaction is broken: switching the light on via light/0/set no longer works.

    I've consulted the latest API documentation and made sure I'm following it, but it doesn't work.

    My set command looks like this:

    Code
    mqtt pub -h rabbitmq -p 1883 --mqttVersion 3 -v -t "shellies/shellydimmer-poort/light/0/set" --message '{"turn": "on", "brightness": 50}'

    On older firmware versions the above command still works, for example firmware version 20210323-110106/v1.10.1-gf276b51

    Also, controlling the device via the web UI also still works.

    Besides, receiving status updates (when set via the devices Web UI) also still works and looks like this:

    Code
    Client 'mqttGLXG1GP9@rabbitmq' received PUBLISH ('on') MqttPublish{topic=shellies/shellydimmer-poort/light/0, payload=2byte, qos=AT_MOST_ONCE, retain=false}
Client 'mqttGLXG1GP9@rabbitmq' received PUBLISH ('{"ison":true,"source":"http","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":50}') MqttPublish{topic=shellies/shellydimmer-poort/light/0/status, payload=135byte, qos=AT_MOST_ONCE, retain=false}


    What did I miss?

    Another question: does anyone happen to know why the changelog is no longer updated? Has it been moved?