Add Nous A6T#1664
Conversation
Adopted from Nous A1T, with - GPIOs from manual / validated against tasmota docs - Change to ESP32 platform - Adding [partition update option](https://esphome.io/components/ota/esphome/#updating-the-partition-table-on-esp32) Updated by using the ota.bin format.
Removed extensive configuration details for the Nous A6T device and added a reference to a separate config.yaml file.
… config.yaml into its own file
✅ Deploy Preview for esphome-devices ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![esphome[bot]](https://avatars.githubusercontent.com/in/247347?s=60&v=4){kind=small}
There was a problem hiding this comment.
❌ Device configuration checks failed
The automated checks for the device pages in this pull request found 1 issue. Please address the items below and push an update — this review refreshes automatically and will be dismissed once the checks pass.
src/docs/devices/Nous-A6T/config.yaml
- config.yaml must be hardware-only —
platform: templateatswitch.0is a user-derived value, not hardware
Need help? See the Adding Devices guide.
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Device configuration checks now pass — dismissing.
There was a problem hiding this comment.
❌ Device configuration checks failed
The automated checks for the device pages in this pull request found 1 issue. Please address the items below and push an update — this review refreshes automatically and will be dismissed once the checks pass.
src/docs/devices/Nous-A6T/index.md
- line 27 — added or modified device pages must use
file=- orurl=-based yaml fences — inline yaml is no longer accepted; move the config into a sibling yaml file and reference it. See https://devices.esphome.io/devices/adding-devices#configuration-yaml-files
Need help? See the Adding Devices guide.
Device configuration checks now pass — dismissing.
|
Power measurements are currently not working correctly: 
So this will be a WIP until I figured that out. |
1 participant
Brief description of the changes
Add Nous A6T smart plug. This is similar to the A8T, but for outside use.
Type of changes
Checklist:
The rules below are enforced in CI by
npm run validate-devicesandnpm run validate-yaml. The full reference is at Configuration YAML files..yamlfile alongsideindex.mdand is pulled into the page with a fenced block of the form```yaml file=<name>.yaml— no inline yaml on added or modified pages.file=fence on the page referencesconfig.yaml.config.yamlis hardware-only: no top-levelapi:,ota:,mqtt:,web_server:,web_server_idf:,improv_serial:,captive_portal:,bluetooth_proxy:, ordashboard_import:, and noplatform: homeassistant,platform: mqtt, orplatform: templateanywhere in the tree.config.yamlhas awifi:block, it contains only radio tunables (country,power_save_mode,output_power, …) — nossid,password,networks,manual_ip,eap, oruse_address. An emptyap:block is allowed.!secret) onpassword:,*_password:, orpsk:keys, and no!secretreferences anywhere in any example yaml.made-for-esphome: truein frontmatter: at least one```yaml url=…fence points at a.yamlfile in the manufacturer's GitHub repo (github.com/<owner>/<repo>/(blob|raw)/<ref>/<path>.yamlor theraw.githubusercontent.comequivalent) so the rendered page shows the upstream config live.