Well at least you know ESP is OK.
The toggle is for an attached relay (if you have one)
Hi @9toejack sorry, I've only just seen this message chain. It might be too late for you to backtrack, but I just wanted to let you know that there was nothing inherently wrong from where you started out.
I have a system in my basement using a WEMOS mini D1 which has an esp8266 processor running the standard Arduino firmware.
I collect the data from there and send it to a Raspberry PI3B running Node-Red and using MQTT. It's been running for about 2 years now.
I used code from this tutorial to get started, but depending on how you are getting on with Tasmoto, you are welcome to have a look at my Arduino code.
I think the only 2 tricky things I found were firstly that the unique HEX code for each sensor required an initial scanning of the network to see what was connected, and then pasting them into an ID array so that I could relate them to a specific temperature. If you swap out a sensor, you have to run it and see what the new code is and paste it into the array. I do this scan on power-up so I can just monitor the serial debug port to see the sensor codes.
The second one (my ignorance) was formatting the sensor value as a string, since that's what MQTT sends, and then converting it back to a number in NODE-RED.
After that it has worked well, and I am more comfortable in 'C' than using yet another OS. One day I might try Tasmoto though.
ah that makes sense, so i can use it to turn a solenoid on or off from there , or use mqtt to trigger it on or off right?
Thats correct, you have a number of GPIO which can be connected to relays sensors etc.
Have you connected any sensors to the ESP yet ?
I appreciate that ill read that one again,
right now its a connectivity issue
getting connected to the wifi has been a pain in the ARSE to say the least.
all the while its been a good learning experience. also a good reminder to pause and reflect instead of pushing on and destruct!
The other reality i have is ,
i ordered 5 more esp's that arrive today.
i could actually use a single esp with each kettle.
collecting temp and then possibly adding my pressure transducers as well.
eliminating all the wires I have connecting everything. it will make the complete "package" more eye candy
however baby steps are needed,
my new esp's just delivered so im going to tamotize another.
Have fun 
Your ESP thinks it's a Sonoff Basic, which is a smart switch with a relay built in. So Toggle on a Sonoff would switch the relay.
You probably need to tweek the configuration so Tasmota recognises all the available GPIO functions.
There is a tutorial on Tasmota with a NodeMCU ESP development board, and the Tasmota docs go through configuring a device not already in the repository.
one done and working at home.
I'm adding the brewery credentials for second wifi info.
so hopefully everything works great when i get it there.
so I had connection issues with the esp's at first with my cell phone.
but I figured out to turn autoconnection off on other WIFI's so it wouldn't try to connect to another service because of the internet issue.
I have a feeling that was my problem at the brewery.
I'll test that theory latter today.
i set up 4 of the new ones.
also did firmware update on all 5
so far so good.
Rabbit hole is shrinking, but possibilities are expanding.
Awesome
Yes, some phones just do that silently and fast, while you are still still busy entering the configuration of the tasmo device and without your browser "complaining" that you are not connected to it anymore. Could well be the case. Disabling auto-connect for the other SSIDs is a good option. My Android phone also complains, that the native tasmo AP has (obviously) no internet and then asks, whether you want it (the phone) to stay or move away.
But you said, that you entered the wifi credentials in the tasmotizer so they will be added during the flashing of the ESP.
Home router worked great.
Took them to brewery. No good!
It's the same exact router.
Maybe it's the guest wifi causing issue but they have different ssid
Also doing testing in an area with no interferences.
All i have to say is holycrap really!
so i once again reset my router at brewery but got to thinking.
House wifi was only caps for the first letter of the name.
brewery wifi was all caps
so i pluged in same ssid as at my house and BAM
all good. now i have readig to figure out the mqtt stuff
and the ds18b20 stuff
2 Likes
Gotta love networking stuff - different vendors implementations of how SSIDs are broadcast can drive you nuts.
Must say i have not had all caps cause me an issue before - but definitely get case right along the way as the ESPs can be finicky with that.
Hopefully you are on track now
Check some of my earlier posts about relevant commands to set at the console also for Tasmota
Craig
Odd I also have all caps SSIDs with tasmota and no problems - still at least its working now
@craigcurtin hey so i need help with network and port forwarding through NAT
is that part of your network expertise?
may be better to go over privately, i dont want all my ip's on the
www
disregard @craigcurtin, my issue was human error.lol
now im going to read the stuff above
but so i dont go down a rabbit hole.
do i start with mqtt with pi and understand that or do i start with tasmota and learn it.
cheers.
start with mqtt on the pi, as this will be the integration part between future Node-Red and Tasmota-devices. Install mosquitto mqtt broker on the pi and download mqtt-explorer on your Client PC (https://mqtt-explorer.com/), then have mqttExplorer to connect to your broker.
I suggest to not bother with user/pwd and TLS security on your broker for a start, as all your setup is inside your LAN/VPN (I hope).
Then enable mqtt on your tasmota devices.
Here is an example how it looks like with a set of three sensors on one device:
once you have that, you can add NR to the game.
