Great work! some suggestions for enhancement thou... (specially when getting many nodes and I/Os) 1. GPIO out Device (and PWM) for MQTT. Mainly for not mixing up I/Os. possibility to name a subscribe topic and map to pin ( bedroom/shades/command) , map "words" to 1 and 0.. up=1 down=0, pub...

more then 32 espeasy?
possibility to disable all communication exept MQTT (no need for unique unit #.) (same unitnumber crasch espeasy)
alternativly increase number of units to >32 (the old 640k problem? )

Feature request: Output-device (binary) and disable of "commands" to not defined GPIO.. (only MQTT actions) too easy to make mistakes and to remember wich GPIO is connected to what HW. ability to report configured output GPIO status to MQTT. disable change of state on non configured GPIOs/...

any solution that will not limit number of nodes to 31 is good! Is there any workaround?
i dont really understand what it is used for any how... do a clean MQTT installation need unitnumber at all?

Request: only accept to set I/O with incoming MQTT topic. (no commands) i am new to the output device and it is not so well documented, but if i understand right it would be possible to let the esp to subscribe to a "realworld device" like "hallwaylamp". this will make it possibl...

Hi ! running build 105 and when setting (yes i know it should be unique number! ) same unitnumber to multipel nodes will make them to restart with intervals of just a few minutes.. (works fine if unique #). as i run openHAB MQTT i have a big question of the reason for unit # over all? what is it use...

Hi! Anders From Sweden here.
Using mainly nodeMCU´s.
Moving from housebot and xAP to openHAB and MQTT.
Thnx for a good forum and and a great app!
kind regs Anders