So I have added an ESP8266 to one of my EmonTX devices which is too far to broadcast to my EmonBase. I’ve connected it to the Wifi and configured the MQTT section to push the data over.
In the EmonESP configuration, I see the 4 power inputs, voltage and pulse counter inputs. It states that it is connected to the MQTT.
On the EmonBase, I have a new input node listed that matches the name given in the MQTT setup of the ESP8266, however, only one feed exists named espwifi3484, rather than what I expected which is the 6 inputs seen in the EmonESP.
Note however, that this wasn’t updating until I rebooted the ESP8266. It connected and provided the result attached, however, it has stopped pushing any data to the MQTT again and the data is not updating in the emonbase.
I can still connect to the ESP8266 web interface without issue, however, my key/value pair list appears to have disappeared???
If I choose reboot on the ESP8266 via the web page config (as I did during my comments above). Does this only reboot the Wifi piece and not the Tx or both?
I’ve been and unplugged and restarted the USB and 9V AC supply… Only had a blue light on the Wifi module before, got activity from the red LED inside the Tx now as well.
I can see the following details in the log on the ESP8266 page now.
It needs a power-down (as you did) or the reset push-button pressed to restart the emonTx. You can’t do it from the ESP via the serial input unless your sketches provide for the ESP to send and the emonTx to receive a serial command that will restart it.
This emonTx shouldn’t be transmitting on the R.F. band (depending on the sketch you’re using) so as far as I’m aware, there’s no mechanism whereby it can interfere. The other two might however be jamming each other. If this is happening, I’d expect it to happen for a short period, then they’d be OK for a while, as the transmissions should be at the same rate but won’t be exactly.
