Okay, it appears to be working now as advertised with only power from the USB connector, but I believe that the board has an intermittent connection on it. I can't see any solder joints that look suspect, so most likely it's one of the esp8266 pins.I will just have to handle it delicately. Thanks for the help.
I'm connecting to Vin on the NodeMCU board, not the esp8266 directly. Since the board is powered from a USB port, I assumed (maybe incorrectly) that Vin would also connect to the input of the voltage regulator that outputs 3.3V and/or whatever voltage the esp8266 uses.
I just felt the components and nothing feels hot. But also the module is unusable unless I power it up like this.
Yes, I did follow all the steps listed including the latest 210x drivers.
I found a mention elsewhere to connect up a second UART, so I did that and connected it's 5V line to Vin on the esp8266. After doing this, the module no longer disconnects/reconnects and seems to be stable. So for some reason there is a power issue with my cable or board, which I'll explore.
I recently bought one of the esp8266 modules shown on this site. When I power it up the blue led lights twice and then nothing else, and the USB connection continually connects and disconnects from my PC. I've tried it on another PC and got the same result.
What is the expected power up behavior for this module? Any suggestions on why it's continually recycling the connection?
@ericvdb I am powering the nRF from the 3.3V pin, so I'll try your suggestion and see if it helps. Thanks.
Okay, I was able to get it work properly when the sensor was close by, so this appears to be a combination of a reception issue, and if the sensor gets reset then it seems that I have to reset my ethernet gateway as well. Is that normal?
Is there a clean way to have the enet gateway auto-reset every 12 hours or so?
@Marvin-Roger Sending back a state is something I was looking at doing, in addition to the ack that I thought was supposed to happen. Thanks for pointing me to an example.
I suspect that the best practice is to do whatever works for you, but maybe hek can shed more light on this.
No repeater in my network. Also, I did use a capacitor on the sensor radio, but on my gateway I used a radio card with external antenna so I didn't use a cap.
Okay, I will check the voltage levels although I don't believe that will be it.
Is there any setting in an include file I should check? Or maybe a recently fixed bug (I noticed a few updates since I downloaded 1.5)?
And that's what I see, the ON/OFF buttons don't change as they should, although the action I want (on or off) does happen as it should.
Do I need to add something to send the ack back to Vera?
I'm a little uncertain on how to add an acknowledgement to a sketch running on a sensor. In my specific case, I've modified the RelayActuator sketch a bit to control my pool lights (toggle a relay 3 times for ON, toggle once for OFF).
I'd like to add some sort of ACK to this so that Vera knows whether the command has been received (like the acknowledgement you get when you turn a light on or off), but I'm not sure exactly how to do this.
I see where ACK's can be enabled, but not sure if those are meant to work like the typical Z-wave device acknowledgements. And would this require modifying the ArduinoRelay1 json and XML files?
Guidance would be much appreciated, or maybe point me to an example that already does that. Thanks!