- Wed Aug 03, 2016 4:18 pm
#52057
@joeman2116, have you thought what you are trying to do? - May be best to either control your nodes resources locally with local (dht) sensors, or control the local resources remotely by another nodes sensors, but trying to control something with both local and remote sensors must inevitably result in one sensor conflicting with the other and probably causing unexpected results.
Regarding a PIR sensor node (for sending triggers to a Relay node), the 4 cheap commonly available PIR modules I tried all needed higher operating voltages than the ESP modules, so unless you can find a usable 3v PIR you're going to have to play around with additional supplies and level-matching. You'll also want to build in some sort of periodic watchdog facility to give confidence that your sensor nodes are still online. I was going to achieve this using a 'controller' node (possibly a voice announcer node) that periodically polled around whatever sensor nodes it was aware of.
Anyway, I'm glad you've noticed the EasyNet concept sufficient to see some of the possible potential, cos I don't remember anybody else voicing an interest.
@cicciocb - I hope you are keeping well matey... you are missed.
@Oldbod, from one old bod to another, I appreciate your comments, geezer. Yep, ESP_Basic is here to stay, and that's for sure. The problem is, it took months to progress V2 to the point where it was almost bug free and very usable as A24, but all that effort was effectively abandoned when V2 was frozen in deference to an immature and buggy V3, which also was not adequately documented.
I'm not knocking all the fantastic effort that has been put into every aspect of mmiscools marvellous ESP_Basic, but V3 is already up to Alpha twenty-something, and still largely without appropriate examples, and who knows when it all may be abandoned again in deference for a V4, or V40.
ESP_Basic could (and should) be a great software on great hardware to allow great connectivity usage, which was great incentive for developing something like EasyNet so that anyone and everyone could benefit from effective connectivity whatever their network knowledge, or lack of. Such an easy-to-use network capability could turn an enjoyable and interesting novelty for the inexperienced into a useful real-world interconnected reality, but it requires supported continuity and adequate documentation for that to happen.
Captain mmiscool is doing a marvellous job of keeping his ship afloat, but the limited manpower available from just 1 dedicated man obviously imposes limits on what is possible, and adding new facilities when people still don't have the info to be able to use the existing facilities just causes more and more unanswered questions and unknowns.
ESP_Basic already has excellent functionality and potential, but if it is to be taken seriously and become more than just an enjoyable experimental novelty, it needs its commands and instructions to be properly illuminated by adequate documentation plus corresponding usage examples, so people can use it without having to stumble around in the dark with unanswered questions.
If there is something important to know which isn't documented, the only one qualified to fill in the missing gaps is captain mmiscool, but I'm afraid he's long been stretched far too thin and busy with bug-hunting to be able to fill in all the missing gaps for everyone.
I am saying this from painful experience of having stumbled blindly around in the dark for many wasted weeks with unanswered questions trying to get even the most basic and essential in-built functionality (such as pin interrupts) to work. And this was after me doing the Driving Lessons, all stuff that I'd gleaned for myself, and in an effort to fill in much of the unknowns for others... but then the ship changed direction without warning and left me cast adrift.
So my down-heartedness is not about ESP_Basics failure to no longer run on 512k devices (because ESPs are cheap enough to buy whatever device is required), it's about stability and adequate documentation to allow it to be used effectively by all. I hope and expect that will happen eventually, but probably not any time soon.
Anyway, I'm pleased somebody else has noticed the EasyNet concept - all the required functionality was already all working B.T.W. So now it's a matter of developing the various nodes I need. I'm too occupied by other commitments at the moment (survival), but eventually I will need to progress things again for my own purposes, so I hope to be active again with it at some point.
Regarding a PIR sensor node (for sending triggers to a Relay node), the 4 cheap commonly available PIR modules I tried all needed higher operating voltages than the ESP modules, so unless you can find a usable 3v PIR you're going to have to play around with additional supplies and level-matching. You'll also want to build in some sort of periodic watchdog facility to give confidence that your sensor nodes are still online. I was going to achieve this using a 'controller' node (possibly a voice announcer node) that periodically polled around whatever sensor nodes it was aware of.
Anyway, I'm glad you've noticed the EasyNet concept sufficient to see some of the possible potential, cos I don't remember anybody else voicing an interest.
@cicciocb - I hope you are keeping well matey... you are missed.
@Oldbod, from one old bod to another, I appreciate your comments, geezer. Yep, ESP_Basic is here to stay, and that's for sure. The problem is, it took months to progress V2 to the point where it was almost bug free and very usable as A24, but all that effort was effectively abandoned when V2 was frozen in deference to an immature and buggy V3, which also was not adequately documented.
I'm not knocking all the fantastic effort that has been put into every aspect of mmiscools marvellous ESP_Basic, but V3 is already up to Alpha twenty-something, and still largely without appropriate examples, and who knows when it all may be abandoned again in deference for a V4, or V40.
ESP_Basic could (and should) be a great software on great hardware to allow great connectivity usage, which was great incentive for developing something like EasyNet so that anyone and everyone could benefit from effective connectivity whatever their network knowledge, or lack of. Such an easy-to-use network capability could turn an enjoyable and interesting novelty for the inexperienced into a useful real-world interconnected reality, but it requires supported continuity and adequate documentation for that to happen.
Captain mmiscool is doing a marvellous job of keeping his ship afloat, but the limited manpower available from just 1 dedicated man obviously imposes limits on what is possible, and adding new facilities when people still don't have the info to be able to use the existing facilities just causes more and more unanswered questions and unknowns.
ESP_Basic already has excellent functionality and potential, but if it is to be taken seriously and become more than just an enjoyable experimental novelty, it needs its commands and instructions to be properly illuminated by adequate documentation plus corresponding usage examples, so people can use it without having to stumble around in the dark with unanswered questions.
If there is something important to know which isn't documented, the only one qualified to fill in the missing gaps is captain mmiscool, but I'm afraid he's long been stretched far too thin and busy with bug-hunting to be able to fill in all the missing gaps for everyone.
I am saying this from painful experience of having stumbled blindly around in the dark for many wasted weeks with unanswered questions trying to get even the most basic and essential in-built functionality (such as pin interrupts) to work. And this was after me doing the Driving Lessons, all stuff that I'd gleaned for myself, and in an effort to fill in much of the unknowns for others... but then the ship changed direction without warning and left me cast adrift.
So my down-heartedness is not about ESP_Basics failure to no longer run on 512k devices (because ESPs are cheap enough to buy whatever device is required), it's about stability and adequate documentation to allow it to be used effectively by all. I hope and expect that will happen eventually, but probably not any time soon.
Anyway, I'm pleased somebody else has noticed the EasyNet concept - all the required functionality was already all working B.T.W. So now it's a matter of developing the various nodes I need. I'm too occupied by other commitments at the moment (survival), but eventually I will need to progress things again for my own purposes, so I hope to be active again with it at some point.
