Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sonoff Dual R2 Ver 1.0 #286

Closed
xoseperez opened this issue Nov 23, 2017 · 21 comments
Closed

Sonoff Dual R2 Ver 1.0 #286

xoseperez opened this issue Nov 23, 2017 · 21 comments
Labels
enhancement New feature or request minor

Comments

@xoseperez
Copy link
Owner

Originally reported by: Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts)

I've just received a pair of these from Ali Express, and realised that they were a little different to the original Dual's. Despite the resistors/capacitors around the esp chip looking similar (sorry - forgot to take a picture of the back), GPIO 0 is now pulled out to a pre-populated header on the board marked as 'BUTTON 0' and not seemingly not connected to the resistor as in the previous version. Much easier to flash at least 😄

I've attached a jpg showing a yellow jumper grounding GPIO0 in prep for flashing

I flashed the modules with the latest dev branch last night (using platformio), but have only tested that the relays work. They do connect to the wifi, and have connected fine to MQTT and my NTP server, and I can confirm fauxmo works too. I'll update this when I get a chance to test the buttons.
@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

On testing today (had to go out for mains cable), I've found that the R2 is a different beast altogether, there is no serial chip between the esp module and the relays as I think was the case in the original model. The esp chip is an 8285. There is a bi-colour status LED labeled D5 that is green when switch 1 is on, red with switch 2 (so far at least, not sure if that's the same as the original).

I'll do a bit more testing then submit a pull request, unless there are any objections?

@xoseperez
Copy link
Owner Author

Original comment by decoddeki (Bitbucket: decoddeki, GitHub: Unknown):

Hi Colin,

did you managed to get relays to work? I just received R2 version, flashed it with espurna-1.10.0-itead-sonoff-dual.bin. It connects to the Wi-Fi and MQTT fine, but relays don’t seem to work.

Any suggestions?

Thanks, Dejan

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

I've not gotten around to testing the button (and button headers) but the relays work fine. If you're up for a bit of testing yourself, there's not that much to it...

https://bitbucket.org/ColinShorts/espurna-sonoff-dual-r2
https://bitbucket.org/ColinShorts/espurna-sonoff-dual-r2/downloads/espurna-1.10.0-itead-sonoff-dual-r2.bin (freshly built, untested)

Let me know if it works for you!

@xoseperez
Copy link
Owner Author

Original comment by decoddeki (Bitbucket: decoddeki, GitHub: Unknown):

Flashed espurna-1.10.0-itead-sonoff-dual-r2.bin. I only get single switch:
slika1.jpg

Am I doing something wrong?

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Let me check, I've probably made a minor mistake in the config.

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Yup, sorry about that - had a definition for a dummy relay that was causing the issue. I think I must've been half way through testing something.

I've uploaded the image to my own running one and can confirm both the switches are visible again. Please download a fresh bin file.

Cheers,
Colin

@xoseperez
Copy link
Owner Author

Original comment by decoddeki (Bitbucket: decoddeki, GitHub: Unknown):

Thank you Colin, it works now. Now I only have to figure out how to get buttons to work :)

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Thanks for testing. I don't currently have a use case for the button(s), but I'll give it a bash today if I get a chance. What are you planning to use, the front panel button by itself, or the gpio buttons from the side header?

@xoseperez
Copy link
Owner Author

Looks like they have greatly simplified the board. You don't need to define a specific BAUDRATE for this and you can enable serial debug since there is no second micrcontroller. Also, can you check if BUTTON0 in the header is tied to physical button? A would bet it is, so the configuration would be:

    #define MANUFACTURER            "ITEAD"
    #define DEVICE                  "SONOFF_DUAL_R2"

    // Buttons
    #define BUTTON1_PIN         0
    #define BUTTON2_PIN         9
    #define BUTTON1_RELAY       1
    #define BUTTON2_RELAY       2
    #define BUTTON1_MODE        BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH
    #define BUTTON2_MODE        BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH

    // Relays
    #define RELAY1_PIN          12
    #define RELAY2_PIN          5
    #define RELAY1_TYPE         RELAY_TYPE_NORMAL
    #define RELAY2_TYPE         RELAY_TYPE_NORMAL

    // LEDs
    #define LED1_PIN            13
    #define LED1_PIN_INVERSE    1

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

I'm struggling to see using the naked eye (I should really invest in a magnifying glass), but I'm pretty confident that that button 0 on the header is tied to the esp module directly on the via next to R9 (gpio0). button 1 comes out at the esp (gpio9) from a via just on the top edge of the physical button, and the button itself is connected directly to gpio10. I'll try to attach some pictures from my phone in a second (with the front one mirrored to make it easier to follow the tracks).

Assuming that the physical button is on it's own gpio pin, and the header pins go to their own - how would you normally set them up?

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Rear view zoomed on traces

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Front view zoomed on traces

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Front view zoomed on face and mirrored.

@xoseperez
Copy link
Owner Author

It's hard to say by the pics, there are traces going from the header to the button but they could as well go to the microcontroller on the other side of the board. Do you have a tester? Set it in continuity mode and check if the BUTTON0 header is connected to either side of the physical button.

If they were actually different GPIOs you will have to decide what each button does, for instance:

// Buttons
    #define BUTTON1_PIN         0
    #define BUTTON2_PIN         9
    #define BUTTON3_PIN         10
    #define BUTTON1_RELAY       1
    #define BUTTON2_RELAY       2
    #define BUTTON3_RELAY       1
    #define BUTTON1_MODE        BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH
    #define BUTTON2_MODE        BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH
    #define BUTTON3_MODE        BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH

In this configuration button3 is the physical button (GPIO10) but trigger the first relay, just as the BUTTON0 header does.

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Thanks for jumping in to help Xose:)

My multimeter (annoyingly) doesn't have a continuity setting, so need to rely on resistance and it jumps around a little, so difficult to say for sure. I'll try for a bit of trial and error to see if the header pins and physical button can be used to control the relays - at least to figure out that I've got the right pins.

I don't know what anyone would normally want to use the buttons for as I'm just tucking the units away and controlling them via mqtt (or Alexa).

@xoseperez
Copy link
Owner Author

Original comment by decoddeki (Bitbucket: decoddeki, GitHub: Unknown):

I will check when I get home from work, if I find my multimeter :)

I would use buttton0 and button1 to attach physical switch to work in parallel with HA.

@xoseperez
Copy link
Owner Author

Looks like this last one id the correct configuration. The physical button is indeed connected to GPIO10, not GPIO0. I have added the configuration for Dual R2 in the dev branch. Will be released with 1.10.1

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Thanks Xose! I'll kill off my fork and not bother with the PR.

It did look to work (my relays switched on once), but I think I might have just fried the GPIO on the headers on this board... This isn't a problem for me as I'm not planning on using them anyway. Should we be using resistors - I thought the gpio pins on these modules could handle pulling the pins high internally and grounding them to 'switch' without resistors.

It might be useful to have button 3 toggle on/off both relays, or toggle them in 2 bits 00, 01, 10, 11, but that would probably require a change to the DUMMY RELAY code and probably more trouble than it's worth. It looks as though you can't have a dummy relay along with real ones.

@xoseperez
Copy link
Owner Author

Released with 1.10.1
@ColinShorts Interesting proposal but not possible at the moment since that kind of behavior is tied to the relays, not the buttons.

@xoseperez
Copy link
Owner Author

Original comment by Colin Shorts (Bitbucket: ColinShorts, GitHub: ColinShorts):

Please remember to add an entry in arduino.h too 😀

@xoseperez
Copy link
Owner Author

Removing milestone: 1.10.1 (automated comment)

@xoseperez xoseperez added minor General enhancement New feature or request labels Jan 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request minor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xoseperez