Saturday, February 7, 2015

ESP8266 and OpenHAB (Part 2)

ESP8266 and OpenHAB (Part 2)

Improving MQTT Auto-connect 

In the last blog one of the issues I mentioned was the LUA code being 'finicky' about reconnects, I made some updates based on code I found on www.esp8266.com to address this as well as move some of the configurable aspects to variables.

Updated mqtt.lua


 --Init  
 DeviceID="Light_FF_Bath_Ceiling"  
 Broker="192.168.0.32"  
 --GPIO0 is connected to switch with internal pullup enabled  
 gpio.mode(3,gpio.INPUT,gpio.PULLUP)  
 --GPIO2 is connected to LED via resistor, initially off  
 gpio.mode(4,gpio.OUTPUT)  
 gpio.write(4,gpio.LOW)  
 m = mqtt.Client("ESP8266", 180, "user", "password")  
 m:lwt("/lwt", "ESP8266", 0, 0)  
 m:on("offline", function(con)   
    print ("Mqtt Reconnecting...")   
    tmr.alarm(1, 10000, 0, function()  
      m:connect(Broker, 1883, 0, function(conn)   
        print("Mqtt Connected to:" .. Broker)  
        mqtt_sub() --run the subscription function  
      end)  
    end)  
 end)  
 gpio.trig(3, "down",function (level)  
    local PinValue=gpio.read(4)  
    --Change the state  
    if (PinValue==1) then  
      --The read resets the output to 0, put it back  
      gpio.write(4,0)  
      print("Light was on, turn off")    
      m:publish("/openHAB/in/" .. DeviceID .. "/state","OFF",0,0)  
    else  
      gpio.write(4,1)  
      print("Light was off, turn on")    
      m:publish("/openHAB/in/" .. DeviceID .. "/state","ON",0,0)  
     end  
 end)  
 -- on publish message receive event  
 m:on("message", function(conn, topic, data)   
    print("Recieved:" .. topic .. ":" .. data)   
      if (data=="ON") then  
      print("Enabling LED")   
      gpio.write(4,gpio.HIGH)  
      m:publish("/openHAB/in/" .. DeviceID .. "/state","ON",0,0)  
    elseif (data=="OFF") then  
      print("Disabling LED")   
      gpio.write(4,gpio.LOW)  
      m:publish("/openHAB/in/" .. DeviceID .. "/state","OFF",0,0)  
    else  
      print("Invalid - Ignoring")   
    end   
 end)  
 function mqtt_sub()  
    m:subscribe("home/openHAB/out/" .. DeviceID .. "/command",0, function(conn)   
      print("Mqtt Subscribed to OpenHAB feed for device " .. DeviceID)  
    end)  
 end  
 tmr.alarm(0, 1000, 1, function()  
  if wifi.sta.status() == 5 and wifi.sta.getip() ~= nil then  
    tmr.stop(0)  
    m:connect(Broker, 1883, 0, function(conn)   
      print("Mqtt Connected to:" .. Broker)  
      mqtt_sub() --run the subscription function  
    end)  
  end  
 end)  

Improving the feedback of the OpenHAB item graphic


Another issue I had mentioned was my concern that the state of the switch changed in OpenHAB independent of whether the ESP8266 actually processed the request and made the update. One way to improve this is to disable the autoupdate property of the switch item. This will wait until the ESP8266 responds before updating the graphic indicating the light is on or off (unfortunately the toggle switch still changes). So the light bulb picture on the left doesn't change until the ESP publishes the state update but the toggle graphic on the right still updates immediately. So if your broker is off the switch shows on but the light shows off

For reference here is a screenshot when working








To fix this, open the items file that defines the switch
C:\openhab\configurations\items\demo.items

Find the entry for the Light_FF_Bath_Ceiling and add {autoupdate="false"} to the end as so:

 Switch Light_FF_Bath_Ceiling           "Ceiling"           (FF_Bath, Lights)     {autoupdate="false"}  

I find you need to refreh the browser before it works correctly


Open Issues

At this point the basics work pretty well, some major open issues though as far as resiliency:

  • The LUA mqtt code will crash if it tries to send or receive more than one message at the same time. This can happen if the button is pressed at the same time as the every 3 minute status update occurs.
  • Not very resilient to wifi outage (LUA Panic crash)
  • Rebooting the module sometimes doesn't start the code correctly
  • The bootloader outputs to GPIO2 upon boot so you will see the light flicker on reboot.


ESP8266 and OpenHAB

ESP8266, MQTT and OpenHAB


Here is a quick little demo on how to use the ESP8266 as an ultra cheap ($3) sensor/control node for OpenHAB.

Setup

ESP8266 (ESP-01) with nodemcu LUA firmware (1/24/2015 build or later)
Mosquitto (or equivalent) mqtt broker running on your network (stock config)
OpenHAB installed and running the demo site (add all MQTT modules)

Circuit

This represents an independently controlled device that you also want to also be able to view/control in OpenHAB. The ESP-01 only has 2 available GPIO pins so this setup connects a button to GPIO0 (must be high on boot) and a LED on GPIO2. Standard power, enable and serial connections not displayed.
Basic circuit - Switch on GPIO0, LED on GPIO2

Procedure


Load the following code on the ESP8266

(See updated post for latest code)

This code is pretty basic and is hard coded to control one of the OpenHAB demo items (FF bathroom ceiling light). Before uploading replace the two instances of the mqtt broker IP with your value. This assumes you have a working LUA instance (1/24/2015 build or greater) and it is already configured to connect to your wireless network.

I used ESPlorer to load the files 

mqtt.lua

gpio.mode(3,gpio.INPUT,gpio.PULLUP)
gpio.mode(4,gpio.OUTPUT)
gpio.write(4,gpio.LOW)

m = mqtt.Client("ESP8266", 180, "user", "password")
m:lwt("/lwt", "ESP8266", 0, 0)

m:on("offline", function(con) 
     print ("reconnecting...") 
     print(node.heap())
     tmr.alarm(1, 10000, 0, function()
          m:connect("192.168.0.32", 1883, 0)
     end)
end)

gpio.trig(3, "down",function (level)
      local PinValue=gpio.read(4)
      --Change the state
      if (PinValue==1) then
         --The read resets the output to 0, put it back
          gpio.write(4,0)
          print("Light was on, turn off")    
          m:publish("/openHAB/in/Light_FF_Bath_Ceiling/state","OFF",0,0)
      else
          gpio.write(4,1)
          print("Light was off, turn on")    
          m:publish("/openHAB/in/Light_FF_Bath_Ceiling/state","ON",0,0)
       end
end)

-- on publish message receive event
m:on("message", function(conn, topic, data) 
     print("Recieved:" .. topic .. ":" .. data) 
if (data=="ON") then
          print("Enabling LED") 
          gpio.write(4,gpio.HIGH)
          m:publish("/openHAB/in/Light_FF_Bath_Ceiling/state","ON",0,0)
     elseif (data=="OFF") then
          print("Disabling LED") 
          gpio.write(4,gpio.LOW)
          m:publish("/openHAB/in/Light_FF_Bath_Ceiling/state","OFF",0,0)
     else
          print("Invalid - Ignoring") 
     end 
end)

tmr.alarm(0, 1000, 1, function()
 if wifi.sta.status() == 5 then
     tmr.stop(0)
     m:connect("192.168.0.32", 1883, 0, function(conn) 
          print("connected")
          m:subscribe("home/openHAB/out/Light_FF_Bath_Ceiling/command",0, function(conn) 
               m:publish("Debug","Starting",0,0, function(conn) print("sent") end)
          end)
     end)
 end
end)

init.lua

dofile('mqtt.lua')


Test the circuit and mqtt

If you just uploaded the code you need to restart the device and ensure it reports Connected and Sent to the serial out. (LUA is finicky and you may need to reboot a couple times).
At this point it would be good to verify the circuit and MQTT components work. The switch should turn the light on and off and you should see your broker receive messages for each change. (If using Mosquitto run it in verbose mode to see the messages coming in/out. (use -v)).



Configure OpenHAB demo to connect to MQTT and process the ESP messages


Add these lines to the mqtt config section in  
C:\openhab\configurations\openhab.cfg (if under windows)
Replace the IP and port with your MQTT broker details

mqtt:broker.url=tcp://192.168.0.32:1883
mqtt:broker.clientId=openhab
mqtt-eventbus:broker=broker
mqtt-eventbus:commandPublishTopic=home/openHAB/out/${item}/command
mqtt-eventbus:statePublishTopic=home/openHAB/state/${item}/state
mqtt-eventbus:stateSubscribeTopic=/openHAB/in/${item}/state


The lines above create an eventbus which allows you to control all OpenHAB items via mqtt. You can also skip the bus and individually connect a single item to mqtt but this is an easier way to start.


Test it all

Open the demo OpenHAB site (replace localhost with your OpenHAB values)

http://localhost:8080/openhab.app?sitemap=demo

Expand FirstFloor ->Bathroom
If you toggle the Ceiling light it should toggle the state of your led, if you press the button it should control the led and update the page.

Next Steps

OpenHAB seems to assume things work, for instance when you change the light state it actually changes the website state before it receives confirmation from the ESP, this seems less than reliable. I wonder if its possible for it to be in a pending state until the ESP process the change and sends back updated state details. (See Part 2 for details on how this can be fixed)