Skip to content

Instantly share code, notes, and snippets.

@oxan
Last active October 3, 2021 20:43
Show Gist options
  • Star 14 You must be signed in to star a gist
  • Fork 4 You must be signed in to fork a gist
  • Save oxan/4a1a36e12ebed13d31d7ed136b104959 to your computer and use it in GitHub Desktop.
Save oxan/4a1a36e12ebed13d31d7ed136b104959 to your computer and use it in GitHub Desktop.
Stream server (serial-to-wifi bridge) for ESPHome
@KosieKramer
Copy link

Great component!

I deployed it successfully in 2 applications in my home on ESP32 boards.
I have a question about also having an RSSI sensor defined on a board running your custom component. It seems it does not update, but keep sending the same value it started up with. When I remove the custom component, the RSSI works correctly:

ota:
  password: *****

sensor:
  - platform: wifi_signal
    name: "Paradox Alarm RSSI"
    update_interval: 60s
    
uart:
  id: uart_bus
  tx_pin: GPIO17
  rx_pin: GPIO16
  baud_rate: 57600
  
custom_component:
  - lambda: |-
      auto stream_server = new StreamServerComponent(id(uart_bus));
      return {stream_server};

@oxan
Copy link
Author

oxan commented Apr 21, 2021

@KosieKramer I can't imagine this is actually caused by the custom component, it does nothing even vaguely related to that. I expect it's a side-effect due to the continuous TCP load the serial server generates.

@KosieKramer
Copy link

@oxan, after some more digging, it looks like it has nothing to do with your component. It is a combination of using a hidden SSID, ESP32 device and the fast_connect directive in ESPHome. In this combination, the RSSI does not seem to change. On ESP8266 devices it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment