atuline / esp8266-fastled

ESP8266 FastLED MQTT Demos

ESP8266 FastLED MQTT Demos

Update: April, 2020

I'm no longer supporting MQTT directly, but am now developing routines around WLED.

Introduction

I'm now converting some of my FastLED demos over to use MQTT messaging in order to have various parameters controlled by an Android phone running an MQTT broker and client.

MQTT Basic Examples

If you're new to MQTT, have a look at my postings at:

• http://tuline.com/getting-started-with-esp8266-and-mqtt/
• http://tuline.com/some-esp8266-and-mqtt-examples/
• http://tuline.com/iot-mqtt-panel-pro-prefixes/

Youtube demo:

• https://youtu.be/j8ajNRYaXZ8

The tutorials go through the steps on how to get MQTT up and running with an Android phone, provide information on these examples, and finally discuss how to configure device prefixes.

Also, experiment with these in the following order:

• mqtt-LED-synchronous - This is the first mqtt demonstration that looks similar to other examples online.
• mqtt-LED - This version supports non-blocking connectivity/re-connectivity. Wasn't easy to get this running reliably.
• mqtt-JSON - This builds upon the previous demo by adding JSON (data exchange) support.
• mqtt-firexy - Our first FastLED/mqtt hybrid that supports fire2012withpalette. If there's no connectivity, you still have fire.
• mqtt-sine - Look at all the parameters you can change just for a single sine wave, including variable phase change around a variable center.

mqtt-mesh (published)

An almost straight migration of notamesh, which features a 'delay' across multiple devices. Looks like they're in sync. Am going to re-think this for mqtt-sync.

mqtt-sound (not published)

An almost straight migration of notasound. Will then re-think this for an unnamed sketch and apply much more programmable sound reaction, possibly some form of lighting ADSR.

mqtt-sync (not published)

Sending synchronization to multiple ESP's, including delays, and then batch processing display sequences. Need to do a few proof of concept sketches first.

Others TBD such as

• OTA updates to demo parameters (not the program, but the parameters for it) using MQTT

esp8266-fastled's Issues

MQTT-sync

@atuline, sorry to post this as an issue on github but thought it ok as this code is no longer supported

I know that you have stopped developing with FastLED+MQTT but I was intrigued as to how far you got with MQTT-sync?

I have a project involving two ESP32’s (each using 16 output level shifting shields from Jason coon) for a grand total of 32x120 (~4000) pixels on the walls of a media room for the kids.

I can load the same sketch on each ESP easily and control them via MQTT on a RPi based Nodered dashboard.

I can map noise and spread across palettes etc but when I run a (simple) example like cylon, I obviously get two sets of cylons.
Out of sync. You get my drift.

I was thinking to declare the full set of pixels on each controller and just show the part of the ‘screen’ that processor is governing. But that seems like a waste of resources, even-though the ESP32 has plenty.

Is there a better way to do this while keeping the two mcu’s time coded with MQTT?

There is a Ubiquiti UniFi AP about 15ft away so connectivity shouldn’t be a problem, but would constant time sync data flood the network? Or would this all have to be on its own private network? I could also set a wireless VLAN which would keep traffic separate.

Just seeking some advice really from a guy who’s been around the block with all this type of stuff.

Just as a side - I’ve seen you’ve migrated to WLED because of the nature of your projects. I still haven’t dipped my toe into WLED but was wondering if I need to modify some of my other projects to be more processor parallel and synced instead of fewer processors doing all work. I’ve had a lot of problems with longer cable runs etc and flickering/artefacts. What is your transition experience between the two platforms? I’m really looking forward to parallel support in WLED so I can integrate it into HomeAssistant :)