Skip to content

Conversation

@KoenBreeman
Copy link
Contributor

@KoenBreeman KoenBreeman commented Aug 9, 2024

Description:

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable): esphome/esphome#7233

Checklist:

  • I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
    or

  • I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

  • Link added in /index.rst when creating new documents for new components or cookbook.

@KoenBreeman
Copy link
Contributor Author

Create new pull request for documentation, since the old version was clothered with errors. #2840

@netlify
Copy link

netlify bot commented Aug 9, 2024

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 7f41986
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/69049e31990d1f0008a8e985
😎 Deploy Preview https://deploy-preview-4122--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@KoenBreeman
Copy link
Contributor Author

Created new documentation, since the old one was incorrect, so it should be ok now.

@github-actions
Copy link

github-actions bot commented Oct 9, 2024

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@KoenBreeman
Copy link
Contributor Author

Can it be reviewed??

@github-actions github-actions bot removed the stale label Oct 10, 2024
@github-actions
Copy link

github-actions bot commented Dec 9, 2024

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 9, 2024
@KoenBreeman
Copy link
Contributor Author

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

Can it be reviewed

@github-actions github-actions bot removed the stale label Dec 10, 2024
@github-actions
Copy link

github-actions bot commented Feb 9, 2025

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@KoenBreeman
Copy link
Contributor Author

Review required

@github-actions github-actions bot removed the stale label Feb 10, 2025
@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@KoenBreeman
Copy link
Contributor Author

When is this review expected

@github-actions github-actions bot removed the stale label Apr 12, 2025
@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jun 11, 2025
@KoenBreeman
Copy link
Contributor Author

Any updates?

@github-actions github-actions bot removed the stale label Jun 12, 2025
@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Aug 11, 2025
@KoenBreeman
Copy link
Contributor Author

Any updates?

@strawpants
Copy link

FYI: your code (this branch) saved my day.

I've tested it successfully yesterday on a xiao ESP32C3 together with a grove xiao shield and an AHT10 i2c temp & humidity i2c sensor for a terrarium project.

Note: that since the module is supposed to work with 5v but the xiao works with 3v3, I did splice the input usb power cable to bypass 5v to the relay module instead of the 3v3 from the Grove xiao shield. I suspect the i2c logic still works with 3v3, as the Xiao acts as the master and should be providing the voltage to the i2c data cables (in contrast to the VCC), but I'll report back in case I've fried up my board or sensors.
It may also work fine without the splicing (use 3v3 to power the relay toggling) but I didn't test that, and I'm not sure if this may harm the relay's working.

@KoenBreeman
Copy link
Contributor Author

FYI: your code (this branch) saved my day.

I've tested it successfully yesterday on a xiao ESP32C3 together with a grove xiao shield and an AHT10 i2c temp & humidity i2c sensor for a terrarium project.

Note: that since the module is supposed to work with 5v but the xiao works with 3v3, I did splice the input usb power cable to bypass 5v to the relay module instead of the 3v3 from the Grove xiao shield. I suspect the i2c logic still works with 3v3, as the Xiao acts as the master and should be providing the voltage to the i2c data cables (in contrast to the VCC), but I'll report back in case I've fried up my board or sensors. It may also work fine without the splicing (use 3v3 to power the relay toggling) but I didn't test that, and I'm not sure if this may harm the relay's working.

I’m it worked. Hopefully it will be included in the core of esphome.

@swoboda1337
Copy link
Member

The docs for this PR are also out of date and need to be looked at. Thanks

@KoenBreeman
Copy link
Contributor Author

The docs for this PR are also out of date and need to be looked at. Thanks

I made this integration more thsn 2-3 years ago. Including documentation. But I will update it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants