Not posted for a while. I tend to push on development of mqttcogs during the summer as I use it to monitor and control my watering in my garden. I spent quite a bit of time pushing on development of mqttcogs, I just haven’t had the time to detail exactly what I’ve done. I will do, when I’ve tested it some more and finalised a few odds and ends.

Here’s a brief bullet point list of some new features.


Added two new tabs (third tab contains the settings)

  • Ability to view the last n mqtt received messages
  • Ability to view the last n log messages

Editing – a Thing

Rather than just using short codes to display mqtt data. I added in the concept of a ‘Thing’. You can now create a ‘Thing’ and set associated thing properties – in particular, the associated mqtt topic.

When you edit a thing, you create a post like any other but have the option of inserting ‘canned’ mqttcogs shortcodes into the editor really quickly.

You can also replace the ‘hard’ mqttcogs topic with the thing slug if you wish. This is pretty neat as it allows you to replace a sensor, you only need to update the mqtt topic at the post level rather than each shortcode that uses it.

I’ll admit that this bit is not finished. The reason is that I also want to be able to associate the Thing with a geographic location or shape. So you can include a GeoJSON fragment as well. This can be used if you decide you want to use a leaflet map.

I’ll post some more when I’ve tidied these up and tested them…

Here’s a quick example.

No Comments

You can leave the first : )

Leave a Reply

Your email address will not be published. Required fields are marked *