Google AI eror.

[storchalberto]

I am interested in using udp. i have done the google interrogation: "esp8266 tasmota releases udp send" and i see the AI response at the beginniong of the page:"Tasmota, when configured, can send data over UDP using rules and the UDPSend command. This allows you to send data to a specific IP address and port, enabling communication with other devices or services on your network" ad next as code for rule: "Rule1 ON button1#state DO UDPSend 192.168.1.100,1234,Hello from Tasmota; ENDON". i think it is an error. where the AI as read this notice?

[barbudor]

There is actually a udp class in Berry but not in rules

[storchalberto]

yes i know, it is only to signal an errata indication on google. In any case, in a next release, i think my be useful to have the UDPSend command

[sfromis]

Get used to it. Using an AI means that you have to expect hallucinations. They are especially likely to just make up plausibly-sounding stuff when lacking an answer.

[s-hadinger]

New features are not created in response to hallucinations 😄
Only on valid use cases and available time from developers

[storchalberto]

This is my case: I have a lot of devices Tasmota based. To access all the devices i am using static IP. To migrate to DHCP on all the devices i have developed a server (based on berry code and with static IP) that receive from the other devices an UDP message and present a page with a drop down list of the devices indicating the name of the devices that allow the browser to redirect on each. All the devices must send an UDP message (for the ESP32 using berry code) to this server, This is not possible for ESP8266 devices. For me the UDPsend can solve the problem.

[barbudor]

I have something similar on my node-red where I present a list of devices with a link to the web page of the device.
I'm using MQTT (processing the INFO message sent by every tasmota at device's boot time including 8266)
No need for UDPsend
You can also use Tasmota Discovery messages

[sfromis]

Saying "I have developed" does not even try to explain why you actively made the choice of creating the "problem" of not using a technique already possible with Tasmota on ESP8266 devices.