esphome-devices
esphome-devices copied to clipboard
esphome
Update index.md
Brief description of the changes
Fixed GPIO numbers to P numbers for the wb3s board which comes native in device
Type of changes
- [ ] New device
- [x ] Update existing device
- [ ] Removing a device
- [ ] General cleanup
- [ ] Other
Checklist:
- [x] There are no passwords or secrets references in any examples.
The only exceptions are
!secret wifi_ssidand!secret wifi_password. - [x] The
wifiorethernetblock has no static / manual ip address specified. - [x] The first configuration provided should be hardware definitions only. A more involved example can be provided in a separate configuration block.
Deploy Preview for esphome-devices ready!
| Name | Link |
|---|---|
| Latest commit | b49fff1b164e2c1d64252a7ae5ca897d1191fe0b |
| Latest deploy log | https://app.netlify.com/sites/esphome-devices/deploys/678172cd9b2ce600084871ab |
| Deploy Preview | https://deploy-preview-981--esphome-devices.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
1 paths audited Performance: 97 (🟢 up 2 from production) Accessibility: 86 (no change from production) Best Practices: 100 (no change from production) SEO: 89 (no change from production) PWA: 70 (no change from production) View the detailed breakdown and full score reports |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks :+1:
Learn more about our pull request process.
![esphome[bot] avatar](https://avatars.githubusercontent.com/in/247347?v=4 "Published by a pub.dev verified publisher"){kind=small}
You should not wipe out the previous esp8266 based configuration. If there are new revisions of the device with different chip/configuration, you should make that clear and put the configuration below the existing with its own header.
Hey Jesse,
I wiped it out since I don't believe this device was ever shipped with a ESP8266 but rather it was suggested, before the tuya-cloudcutter latest method, to remove the chip and replace it with a ESP. In that case the information provide was correct but is not correct with the device as its manufactured.
Whats the best way to include that in the pull? I'm not super familiar with workflow process in git hub.