I’ve been meaning to update the blog – and I just keep getting sidetracked with the many interesting possibilities of Node-Red…. so – I put a short video together here. Should be something of interest in it.
https://www.youtube.com/watch?v=xoQ_Fs31xtM
Pete
Node-Red on The Raspberry Pi
Yes. I found that an issue when using multiple units, so I started with an initial device name ‘xx’ to which it also subscribed to as a topic. Writing to the topic xx with a payload of Name’newname’, rewrites the config variables to flash. On a reset its name becomes ‘newname’ and re subscribes to ‘newname’.
(can be renamed again via the newname subscription)
Having a common subscription along with ‘newname’ etc, allows all or individual module addressing.
I also wanted to have the modules capable of closed loop networking with a Pi as an AP + broker, or out to a cloud service (ie. m20cloudmqtt.com) via an alternate AP, so on boot up, if a pin is held down, the module toggles between two config sets, which get reflashed. I use the second wireless AP as a network extension to attach anywhere it needs to be.
Grant you, not as nice as a webUI, but sorts my issues.
Hmm yes food for thought. A pal of mine is at home right now trying to get the original HTTPD software working which would make the ESP8266 act as a router until you set everything up in it – that would be a good solution but for the fact that the original web software never did work properly on a “clean” esp8266 board. I’m hoping he’s fixing that. I think he’s planning on using a pin also to reset.
I love what you’re doing. Keep it up. Have you see the espHTTP server FW? http://www.esp8266.com/viewtopic.php?f=6&t=376
I’m wondering if it would be worth it to try to allow the device name, topic subscriptions, etc to be configured via a webUI. Just a thought.
Yes a friend of mine is working on that so that we can start from scratch with a unit up to having it talk to an MQTT broker all without having to recompile every time.