Skip to content

SPI and reading issues #202

@mikelawrence

Description

@mikelawrence

With your recent updates to the ESPHome ATM90E32 component I though it was to time to update to the latest yaml. But I started having serious problems. I started receiving SPI warnings like this one:

[16:55:23][W][atm90e32:863]: [get_phase_current_()] SPI read mismatch: expected 0x0002, got 0x2413

But the real problem was with the data.

Image

Image

What fixed my problem was removing interface: software from 6chan_common.yaml line 55.. This defaults to any and I believe it will choose a hardware SPI on the NodeMCU.

spi:
  interface: software
  clk_pin: 18
  miso_pin: 19
  mosi_pin: 23

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions