-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
bin file with pcf8574 support #11
Comments
Thanks for informing me. I will check on the weekend. arendst changed a lot during the last weeks on relays. Not very easy to keep the rest working. I had fo change a major portion of the code already. You will get feedback asap |
I found the bug and fixed it. Tested today only with ONE board, but hopefully also working with more than one. BIN files updated |
Thanks for fixing it. Yes all 10 Relays are switchable now by remote commands. Thanks |
I checked with two relays on the WEMOS and 8 relays on the pcf. For me this worked perfectly though mqtt and webinterface . I have no eletrodragon to verify. |
Relay switching does also work for me by web and mqtt. On the electrodragon board there are two mini switches which can also switch the two relays on the board with the standard arendst software. with yours variant they don't. But it is ok for me. I wanted only mention it. Never mind. Thanks for fixeing the main bug. |
ok, now I understand. I assume 2 GPIO are assigned as SWITCH1 and SWITCH2. They should switch RELAY1 and RELAY2. let me see. should be fixable. |
Details of the electrodragon board you find here. The switches are on gpio0 and gpio2 |
Could you be so nice and update the bin files to version 5.10.0? Thanks in advance. |
Yes, done. |
I commented this already in the closed issue. But perhaps it might be better to open a new issue.
I use your last bin file with the electrodragon 2 Relay board and a chinese pcf8574 and an 8 relay board.
The relays connected to the pcf8574 are working, the relays onboard don't switch anymore but they show up in the weggui.
Any Idea?
The text was updated successfully, but these errors were encountered: