Send MQTT messages in the 'Chill Projection Screen' rule

[slopjong]

The switches

Switch chill_zone_screen_button_up
    "Screen up"
    { channel="mqtt:topic:chill_zone_screen:up", autoupdate="false" }

Switch chill_zone_screen_button_stop
    "Screen stop"
    { channel="mqtt:topic:chill_zone_screen:stop", autoupdate="false" }

Switch chill_zone_screen_button_down
    "Screen down"
    { channel="mqtt:topic:chill_zone_screen:down", autoupdate="false" }

defined in level2.items can be removed if we changed the rule

rule "Chill Projection Screen"
when
    Item chill_projection_screen received command
then
    switch(receivedCommand.toString.toUpperCase){
        case "UP": {
            chill_zone_screen_button_up.sendCommand("ON")
        }
        case "STOP": {
            chill_zone_screen_button_stop.sendCommand("ON")
        }
        case "DOWN": {
            chill_zone_screen_button_down.sendCommand("ON")
        }
    }
end

to

rule "Chill Projection Screen"
when
    Item chill_projection_screen received command
then
    val mqttActions=getActions("mqtt","mqtt:broker:mosquitto")
    switch(receivedCommand.toString.toUpperCase){
        case "UP": {
            mqttActions.publishMQTT(".../on");
            Thread::sleep(1000)
            mqttActions.publishMQTT(".../off");
        }
        case "STOP": {
            mqttActions.publishMQTT(".../on");
            Thread::sleep(1000)
            mqttActions.publishMQTT(".../off");
        }
        case "DOWN": {
            mqttActions.publishMQTT(".../on");
            Thread::sleep(1000)
            mqttActions.publishMQTT(".../off");
        }
    }
end

by using the MQTT binding v1 in parallel. Then the three rules handling the item changes of the three switches could be removed.

Additionally the sleep isn't necessary if the ESPs are configured by pulsing the output.