I am trying to get ESPNow working and I've run into some weird error message I cannot get past, yet. The ESPHome editor red-underlines the whole packet_trasport section saying "No sensors or binary sensors to encrypt" on the consumer device yaml (which, correctly, does not have any sensors to provide).
I've implemented my stuff close to the Simple Example listed here.
Provider device (this one works):
sensor:
- platform: adc
pin: GPIO35
name: "Battery Voltage"
id: battery_voltage
accuracy_decimals: 3
binary_sensor:
- platform: gpio
pin:
number: GPIO32
mode: INPUT_PULLUP
name: "Door"
id: door
device_class: door
filters:
- delayed_on: 20ms
espnow:
id: espnow_component
peers:
- 00:00:00:00:00:FF # consumer's MAC removed for posting in forum
packet_transport:
- platform: espnow
id: transport_unicast
espnow_id: espnow_component
peer_address: 00:00:00:00:00:FF # consumer's MAC removed for posting in forum
encryption:
key: "my key goes here"
binary_sensors:
- door
sensors:
- battery_voltage
Consumer device (this one shows the error):
espnow:
peers:
- FF:00:00:00:00:00 # provider's MAC removed for posting in forum
packet_transport:
- platform: espnow
encryption: "my key goes here"
providers:
- name: mailbox
binary_sensor:
- platform: packet_transport
provider: mailbox
remote_id: door
internal: true
name: "Mailbox Door"
device_class: door
sensor:
- platform: packet_transport
provider: mailbox
remote_id: battery_voltage
name: "Mailbox Battery Voltage"
internal: true
When I run "validate" on the device, it also complains about the same issue. In the example, the consumer does not have any sensors to encrypt... what am I missing here?

