Wait, you have a delay of seconds on your doorbell notification? Wow, over here that would probably mean the UPS guy at the door has already run off the driveway and you can now go and pick-up your packet elsewhere ... (Joking of course - but not by much)
This is a great project! Your title makes it sound like you have given up on ESP-NOW. It seems you are making the best of both worlds, ESP-NOW and WiFi.
I was using espnow before. I was using it mostly for the reason it is really fast to send and receive a packet (i've measured under a millisecond) and also because this system works without using a wifi so in some cases making the hub reliable may be desirable. I have not yet made a hub myself, i was using it to control lights to the rythm of music with a ps2 controller. So i don't know if esp now hubs will fail sometimes, but it seems to me its possible to make a very reliable system.
Good name for your project, I want to make a rain sensor alert for my wife, when the washing is on the line so if it starts to rain then it tells my wife to rush out and take the washing in, so speed is the main goal, so would you use Wi-Fi or NOW? So joined your channel as it looks interesting thanks Bob in the UK I wanted to purchase your sensor but see it is not available??
If you use ESP32 on your hub I think you will need only one module for both receiving ESP NOW messages and connect to AP and send data to MQTT broker. Why are you instead using 2 ESP8266?
Running espnow on esp32 with continuous data transfer heating esp board. Are there any specific requirements to throttle up data sending rate for optimum heating??
But wifi is super unstable if you live in an urban area. I tried bluetooth BLE but i cant find a freaking good library that can provide easily a simple host BLE (Python, Node, C#). Everything in C# seems targeted for Xamarin lately, the same with Kotlin and Android. With this I mean send the data from the ESP32 to my NAS server with bluetooth
I was seriously surprised by the cost of your contact sensor. It's like 4 times as high as I expected it to be. What drives the cost so high? This just seems like a dev board with a microswitch, which is like a $1-2 component. Very discouraging, since my product would be basically the same thing with about 5 microswitches and would also require a 3d printed part.
I understand this might not be for everyone. I made all the schematics and full source code for the ATtiny and ESP8266 (sender, receiver and gateway) available to everyone for free. You're welcome to use my design and code to build your own.
@@MrDIYca Thanks. At this time, the lowest cost solution for my system seems to be using I2C GPIO boards, combined with small custom PCBs to hold the microswitches. I'll take a look at your microswitch and how its attached, to see if I can get a board that fits the niche I'm trying to fill.
Hi thanks for this project. I'm trying to start one by one and ..to start first with attiny...i uploaded your code tested . but in deep sleep its consuming 300uA . not sure why is that? is that's how your code supported to work for attiny in deep sleep? i just power attiny and used a switch input that's all..all.othe pins are floating or untouched
Well I have designed my own made a Wemos d1 mini deep sleep wake shield if you define mac address in wifi settings in your code you can connect and send message to home assistant MQTT broker as low as 500ms not fast as ESPNow ofcourse but you dont have to deal with a ESPNow to mqtt hub anymore😉 cause even I mod my Wemos d1 mini's for less consumption in deep sleep mode which is 17uA but The hub does not sleep and it is always open. Acorrding to datasheet of esp 8266 modules ex: wemos d1 mini ESP12F can consume around 75 to 80mA when in Wifi Station mode so long term battery powered hub is not possible solution. I highly recommend you to try connectting with defining AP MAC address configuration you will see it will connect to your AP about 500ms or 600ms depends on your Router configuration also make sure to configure wifi Channel on your Router and on sensors wifi configuration code
![ESP-NOW explained: Wireless IoT communication made easy! | Tutorial] #EdisTechlab](/img/n.gif)
Wait, you have a delay of seconds on your doorbell notification? Wow, over here that would probably mean the UPS guy at the door has already run off the driveway and you can now go and pick-up your packet elsewhere ... (Joking of course - but not by much)
This is a great project! Your title makes it sound like you have given up on ESP-NOW. It seems you are making the best of both worlds, ESP-NOW and WiFi.
I was using espnow before. I was using it mostly for the reason it is really fast to send and receive a packet (i've measured under a millisecond) and also because this system works without using a wifi so in some cases making the hub reliable may be desirable. I have not yet made a hub myself, i was using it to control lights to the rythm of music with a ps2 controller. So i don't know if esp now hubs will fail sometimes, but it seems to me its possible to make a very reliable system.
Good name for your project, I want to make a rain sensor alert for my wife, when the washing is on the line so if it starts to rain then it tells my wife to rush out and take the washing in, so speed is the main goal, so would you use Wi-Fi or NOW? So joined your channel as it looks interesting thanks Bob in the UK
I wanted to purchase your sensor but see it is not available??
Thank you! Personally, I would just use Wi-Fi; you're only losing a couple of seconds. Unfortunately, I'm sold out.
+1 for PCBWay
If you use ESP32 on your hub I think you will need only one module for both receiving ESP NOW messages and connect to AP and send data to MQTT broker. Why are you instead using 2 ESP8266?
It is the same issue with ESP32. In theory, it can be done - you can watch this segment ua-cam.com/video/AqpCiIf_XJM/v-deo.html
@@MrDIYca Very well explained. I have missed that part of the video. Thank you.
Running espnow on esp32 with continuous data transfer heating esp board. Are there any specific requirements to throttle up data sending rate for optimum heating??
I like the idea, but isn't a shelly door sensor the same with already a optimized fast response time?
But wifi is super unstable if you live in an urban area. I tried bluetooth BLE but i cant find a freaking good library that can provide easily a simple host BLE (Python, Node, C#). Everything in C# seems targeted for Xamarin lately, the same with Kotlin and Android. With this I mean send the data from the ESP32 to my NAS server with bluetooth
I was seriously surprised by the cost of your contact sensor. It's like 4 times as high as I expected it to be. What drives the cost so high? This just seems like a dev board with a microswitch, which is like a $1-2 component. Very discouraging, since my product would be basically the same thing with about 5 microswitches and would also require a 3d printed part.
I understand this might not be for everyone. I made all the schematics and full source code for the ATtiny and ESP8266 (sender, receiver and gateway) available to everyone for free. You're welcome to use my design and code to build your own.
@@MrDIYca Thanks. At this time, the lowest cost solution for my system seems to be using I2C GPIO boards, combined with small custom PCBs to hold the microswitches. I'll take a look at your microswitch and how its attached, to see if I can get a board that fits the niche I'm trying to fill.
Hi thanks for this project. I'm trying to start one by one and ..to start first with attiny...i uploaded your code tested . but in deep sleep its consuming 300uA . not sure why is that? is that's how your code supported to work for attiny in deep sleep? i just power attiny and used a switch input that's all..all.othe pins are floating or untouched
Very educative video
Can you make on iot 32/64 channel home automation with esp32 or esp8266
not as-is, but you can always extend the I/Os
set a static ip in the code, and the esp will connect much faster most of the time
these numbers were with a static IP ( DHCP was longer but not by much)
I used static ip and saved the wifi channel.
I got down to 200ms from sleep to send out a tcp message
could you not use esphome to code it
not familiar with esphome
Well I have designed my own made a Wemos d1 mini deep sleep wake shield if you define mac address in wifi settings in your code you can connect and send message to home assistant MQTT broker as low as 500ms not fast as ESPNow ofcourse but you dont have to deal with a ESPNow to mqtt hub anymore😉 cause even I mod my Wemos d1 mini's for less consumption in deep sleep mode which is 17uA but The hub does not sleep and it is always open. Acorrding to datasheet of esp 8266 modules ex: wemos d1 mini ESP12F can consume around 75 to 80mA when in Wifi Station mode so long term battery powered hub is not possible solution. I highly recommend you to try connectting with defining AP MAC address configuration you will see it will connect to your AP about 500ms or 600ms depends on your Router configuration also make sure to configure wifi Channel on your Router and on sensors wifi configuration code
Can you explain more on how you used the AP MAC address to connect to Wi-Fi? Did you mean using a static IP instead of DHCP?
can you make some documentation on that or explain more ?
I'm interested in this can you share how you made esp consume only 17uA in deep sleep mode?? can we connect in discord or telegram??
@@MrDIYca yes static address with channel of ssid defined this makes Connecting to wifi about 500ms depends on the Router though
@@the-matrix-has-you thanks can I text you in discord or telegram???
Tic Tac Sensor
I kind of like it :)
👊 promosm