Remote_receiver and platform max7219digit don't work together

ESPHome
1

Each platform works with tested running code apart from each other.
When put both on one device the remote_receiver stops working and the only indication of this is,

[01:54:32][W][remote_receiver.esp8266:063]: Remote Receiver Signal starts with a HIGH value. Usually this means you have to invert the signal using 'inverted: True' in the pin schema!

again… both pieces of code work until put on the same device. I can take the max7219digit code out and then the remote_receiver starts to show rc_switch data on the logger.

Is this a bug in ESPhome?

esphome:
  name: off-clock

esp8266:
  board: d1_mini

captive_portal:

remote_receiver:
  pin:
    number: D5
  dump: rc_switch
  tolerance: 50
  filter: 4us
  idle: 3ms

binary_sensor:
  - platform: remote_receiver
    name: position
    rc_switch_raw:
      code: '110100100001001000001010'
      protocol: 2
    filters:
      delayed_off: 4s

spi:
  clk_pin: D0
  mosi_pin: D1

time:
  - platform: homeassistant
    id: homeassistant_time

font:
  - file: 'pixelmix.ttf'
    id: digit_font8
    size: 8

display:
  - platform: max7219digit
    id: display_max
    cs_pin: D2
    num_chips: 4
    rotate_chip: 0
    intensity: 0
    scroll_enable: false
    update_interval: 5s
    lambda: |-
        it.strftime(3, 0, id(digit_font8), "%I:%M", id(homeassistant_time).now());
2

And does that work?

3

I don’t get this warning when only the remote_receiver code is used.
It just works. e.g. receives RF and triggers the position sensor.

when I add the display code, remote_receiver stops working.

4

I asked if doing as the error message suggests fixes it.

5

No it does not fix it.

6

esp32_ble_tracker can do something similar.

I would try a board with more resources and see if that helps. A decent ESP32.

7

That is disappointing.

8

I’m not saying it will fix it, but a key learning for me has been that ESP quality can matter.

9

Thnx, but I would bet it’s a ESPhome firmware issue… A log or report of these conflicts would be nice but it happily compiles and uploads just fine. add to wish list though. :crossed_fingers:
Thanks for the suggestion

10

If you have found an error in esphome then post a GitHub issue.

11

I will … It’s just a pain. Was hoping I was doing something stupid.

12

Here’s some standard steps I go through before raising an issue (which takes time before someone else can look at it as well as taking thier time) :

  1. Triple check all connections. Maybe even solder them.
  2. Try different pins
  3. Try a different board (I always have spares)
  4. Try a different sensor (I typically have spares)
  5. Try a different power source (good quality)
  6. Try a different usb cable (if relevant, good quality).

I’m always amazed how often one of these simple things resolves my issue. And then if you raise an issue you also have a solid list of things you’ve tried, and so are more likely to get help.

Recently I was setting up an RF transmitter/receiver and it didn’t work properly on two ESP32s. I switched to a quinled and it started working flawlessly.

1 Like