- Sun Jun 12, 2016 4:36 pm
#49085
The straight answer to your questions is that I don't know, because ESP_Basic was a constantly moving target which I struggled to keep up with, and which then changed direction before I was able to get a functional udp network of nodes up and running. I had it almost done on V2, but then the goalposts were moved with V3 causing it to no longer be suitable for the script I'd been developing for my 512K Sonoff relay modules. I've ordered some 4Mb Electrodragon relay modules from china, but the required enthusiasm may take longer to replace.
I don't know what your requirements are, so can't say if the udp networking would be suitable for your needs, but if you are not expecting excessive network demands then it should probably be ok.
UDP is a connectionless non-handshake broadcast method of data transfer. All nodes have a receive port open and receive all broadcasts from all other nodes on that same subnet, and it is down to each node to decide if the transmission is meant for it, or not.
I've created an 'EasyNet' common framework that allows nodes to communicate without any unique network configuration. There's no need to know individual IP addresses, because each node listens to broadcasts for its own name, and if recognised, actions any accompanying command/parameters meant for it. It is down to any sending nodes to request acknowledgements if required, and re-transmit any unacknowledged broadcasts. Receiving nodes return acknowledgements with... 'udpreply message'
CiccioCB has created a very useful UDP_debugger.exe utility which you can download from here...
https://github.com/cicciocb/UDP_tester/archive/master.zipYou can download the Switched Relay script which contains the EasyNet framework from here...
http://www.esp8266.com/viewtopic.php?f=41&t=10327#p48805Click on the top-left ? button to show the Help page which shows the commands it recognises - basically you want to send it appropriate commands from the UDP_debugger utility to check the udp network functionality for yourself, ie: 'node1 blinkip'.
The intention was that PIR and multi-i/o trigger nodes would send event trigger msgs such as 'Zone3 Alert' or 'Frontdoor Visitor' to corresponding relay and IR and voice announcer nodes etc, which would recognise and respond to them as appropriate. But various ESP_Basic growing pains and too many unanswered questions delayed me from getting that far before the switch to V3, and I'm reluctant to return to that situation. I've already done an MP3 Player node as an interim step to a Voice Msg Announcer node, and I've got a couple of external PIR activated solar garden lights ready to be turned into ESP_Basic trigger nodes, so I expect I'll continue with the project again once most of the V3 bugs are ironed out and it remains stable for at least a week, but I won't be considering that for some weeks yet.
If you want any more detail I can post you an EasyNet Demonstrator script I had been working on which contains a lot more info, but be aware that it is a V2 script that probably won't run on V3 which I won't be converting or upgrading.
My plan was (is) to have a second wifi router network just for my 'system' nodes BTW, which has no need of internet connection, and will not impact on the my original internet wifi network computers or vice versa.