That’s a tricky one. There have been some recent changes that havent been released yet.
If you replaced your settings.h file with the one from here:
and added: #define USE_WEMOS_D1_MINI to the list of board types then it should fix it.
I thought that previously you were seeing these zeros in the web dashboard or app, not in the serial monitor. Seeing zeros in the serial monitor won’t be because of data invalidation, it’s probably because you are reading the sensor too often.
But when i activated the NodeNMCU board in code the relay turns on when i give Wemos D1 Mini power. I doesent work with the switch, but the relay turned on and the led blinked.
And when i activated Sparkfun board in code the temperature shows without “0”. But still, the relay does not respond with that board activated.
So it must have something to do with the code?
What a big mess this is going to be when i start to convert my other devices, include my garage door opener,…
Okay, you probably need to take all the files for that Edgent example, and drop your code in to it.
I guess it depends if you want all of the Edgent dynamic provisioning and Blynk.Air features.
If not then it’s much simpler if you go for the non-dynamic provisioning route by adding-in your template ID and name to your own sketch and changing any code that uses Notifications, Time Input etc.
But for the other units i have i think i do what you says about non-dynamic. I just not interested in Blynk dashboard etc. I have only used the app before, and i guess it is that i like best.
Okay. I do not think i fully understand how all that works regard to “provisioning” etc. I wish i just could use my old code. Instead i have to use ALOT of time to recode all my units.