Group Details Private

Contest Winner

  • RE: Glowing/pulsing yellow LED?

    @raptorjr said in Glowing/pulsing yellow LED?:

    MKRNB 1500
    It helps if you post a wiring diagram and a sketch.

    posted in Hardware
  • RE: Is there an inbuilt way to tell that a node is "off network" from the nodes perspective?

    I actually created a message queue for this. It will go on retry when it gets a didn't reach parent. So I know when the communication is gone. I'll add a communication up event to it. And I should be done. I won't know it it reaches the gateway. But I can add a visual indicator for when the repeater is out. That's sufficient for me.

    posted in General Discussion
  • RE: My Wemos D1 mini adventures - Interrupts on pins D3 and D4

    While we're at this topic. Does any one know what the NRF24L01+ does with it's interrupt pin? I'd like to hook it up to the other pin - d4 in this case. Does it pull high when there's a new message or is it pulled up by default? Which I hope

    posted in Hardware
  • RE: Is there an inbuilt way to tell that a node is "off network" from the nodes perspective?

    It's something I'm looking for as well

    posted in General Discussion
  • My Wemos D1 mini adventures - Interrupts on pins D3 and D4

    Hi all,

    Recently I started to experiment with the Wemos D1 mini as a MySensors node, with a NRF24L01+ radio. As most wouldn't go this route, since it has built in WiFi. I did, because for one WiFi was not available for the particular node I'm developing. And second I don't really like my HA to run on WiFi. There are many reasons I have for this. But my main concern is the amount of time it takes to reconfigure all your nodes when the ssid and or password on your router have changed. But let's not start a topic on this. In this topic I just wanted to share some tips and tricks I discovered which some were hard to find on the internet and others I came up with my own solution. I'll keep adding tips and tricks to this topic if I discover new ones.

    The Mini D1 doesn't like it when you declare an interrupt handler like you'd normally do.

    volatile bool interruptReceived= false;
    
    void handleInterrupt() {
      interruptReceived = true;
    }
    

    If you're lucky it compiles. But it will not work. You'll receive a strange bootloader error and the Mini will not boot. The reason for this is that the Mini expects handlers to be stored in the IRAM space. Just add a compiler directive and your interrupt handler will work just fine.

    volatile bool interruptReceived= false;
    
    ICACHE_RAM_ATTR void handleInterrupt() {
      interruptReceived = true;
    }
    
    void setup() {
        pinMode( interruptPin, INPUT_PULLUP );
        attachInterrupt(digitalPinToInterrupt( interruptPin ), handleInterrupt, FALLING ); 
    

    Be carefull with using interrupts on D3 and D4

    So the ESP2866 does a lot of funky things during bootup. It will pull some pins HIGH and LOW to check if it should go into program mode or not. It probably uses it for more reasons, but I'm by no means an ESP expert. The D3 and D4 pins are pulled up high by the Esp, with a - I believe - 10K resistor. Whenever you connect anything to it, that will cause these pins to be high during booting, the Wemos will not finish the boot mode and your sketch is never loaded.

    I wanted to attach an MCP23017 port extender to my Wemos and use the interrupt to refresh the values. So I didn't need to poll the MCP23017 all of the time and kept CPU time available for other tasks. The problem with this, is that the MCP23017 pulls it's interrupt pin HIGH when there's no interrupt - which is always the case when the chip power's up. So connecting the interrupt pin to D3 or D4 caused my Mini D1 to not exit boot mode.

    I could have simply used D3 and D4 as SDA and SCL pins for the I2c communications and use D1 and D2 as interrupt pins. But not all libraries like that. So the easiest way to get around it was a simple and cheap hardware solution. I connected a diode (doesn't matter which one you take. Just take a low 1N400x one) and that did the following:
    The HIGH value of the MCP's interrupt pin is blocked by the diode. When the MCP pulls the interrupt pin low current can flow between the interrupt pin (INPUT_PULLUP) on the Wemos Mini and the MCP's interrupt pin. This made sure the MCP is never able to pull the pin on the Mini high. And the problem was actually solved - easy peasy. I can use D3 and D4 as interrupt pins.

    Here's the schematic. In my case I use the mirror mode on the MCP's interrupts. So I only need to connect one of the MCP23017's interrupt pins to the Wemos.
    Schermafbeelding 2021-10-09 om 15.49.36.png
    I also run the MCP23017 on 3.3V so it's the same as the Wemos mini.

    posted in Hardware
  • RE: RGB night lamp

    Looks awesome. Might be fun to put it outside before your front door on 31th October. Still have a Halloween project on my ever growing bucketlist xd

    Blynk is awesome for controlling Halloween projects.

    posted in My Project
  • RE: WeMos D1 Mini Gateway + Relay

    Also posting the wiring helps others to help you. Fitzing is easy for this task

    posted in Troubleshooting
  • RE: WeMos D1 Mini Gateway + Relay

    What type of relay are you using? You can only use one with opto couplers. You can regonise it, because it has a vcc and a jd-vcc pin. Power the jd-vcc with 5v and vcc with 3v. The vcc is for TTL lvl control and the jd-vcc powers the 5v relay. Without this version you can not hook up a relay to a 3.3v microcontroller. Because the high state is barely high enough to drive a normal 5v relay

    posted in Troubleshooting
  • RE: WeMos D1 Mini Gateway + Relay

    @anderBAKE Be careful to which pin you hook up the relay. Most Mini D1 pins are shortly being pulled up during boot up. That short spike can damage the device you've connected to the relay. It's why I avoid using the Wemos D1 mini with relays. I believe d0 is one of the pins that's not being pulled high during boot up - but not sure.

    posted in Troubleshooting
  • RE: 💬 Relay

    @mfalkvidd I'm in an older version I discovered. Ran across more small differences.

    posted in Announcements