YAML Configuration variables and/or post-setup of should_broadcast_/should_listen_ for UDP component

[juanboro]

Component name

udp

Link to component documentation on our website

https://esphome.io/components/udp/

Describe the enhancement

Currently, the UDP component will configure itself during setup() as a broadcast socket only if a udp.write action is created. Similarly it will only configure as a listen socket if a on-receive trigger is created.

The requested enhancement would to be to add optional specific ability to configure the UDP config instance as broadcaster and/or listener, ie:

udp:
  is_broadcast: true  

It also would be good if public methods like send_packet would either just return/error if broadcast isn't set or perhaps - just have it do the socket setup. Right now ... it core dumps kind of like this...

[16:29:28.254]Core  1 register dump:
[16:29:28.262]PC      : 0x400ee722  PS      : 0x00060c30  A0      : 0x800df723  A1      : 0x3ffb6620
WARNING Decoded 0x400ee722: esphome::udp::UDPComponent::send_packet(unsigned char const*, unsigned int) at /COMPONENT_LWIP_DIR/include/lwip/sockets.h:68
 (inlined by) esphome::socket::BSDSocketImpl::sendto(void const*, unsigned int, int, sockaddr const*, unsigned long) at /COMPONENT_SRC_DIR/esphome/components/socket/bsd_sockets_impl.h:135

In my case where I need to use send_packet in a lambda, I have to currently work around this like this:

esphome:
  on_shutdown:
    then:
      # necessary to make esphome codegen tell udp component instance it is a broadcaster before setup()...
      - udp.write:
          id: udpbc
          data: []

Use cases

This allows using the send_packet method in lambdas - for example piping remote_receiver data out to UDP.

Anything else?

An example of use in remote_receiver - here: esp32-cc1101-udp-example.yaml

[github-actions[bot]]

🏷️ I've automatically added the component: udp label to help categorize this feature request.