-
"should be" is not an option :-) Did you try it specifically on ESP?
I do not see a difference from captiveportal vs test_dgram...., both use bind and server.on...
Well I will give a try anyway....I will need to implement send-udp on my PC than.
-
Hey, I got progress and ALMOST DONE....
PLEEEEESEEE HELP!!!! We'r very close to get Alexa integration
The CaptivePortal script is working on my ESP. Looks good.
When I rewrote test_dgram with server side UDP from CaptivePortal it was not working anyway... seams the script has client's part problem. Never mind.But my Alexa script WORKS to receive UDP requests now!!!! YUHUUUU!!!
Small info how Alexa works:
- Alexa sends UDP multicast request to discover devices
- device answer UDP package identifyng itself as Belkin IoT and answer has a http link to on/off page
In arduino I used folowing Alexa UDP broadcast params
(it works, I use it myself long time now):
IPAddress ipMulti(239, 255, 255, 250); // 239.x.x.x is for Belkin discoverable devices
const unsigned int port = 1900;Now... I did implement Alexa protocol already, playing and search Espruino git around. I managed to get UDP incomings with addon param dgram.createSocket(...multicastGroup:
I attach my script. Please put you SSID and PWD.
Still Alexa is not recognizing response and answers "no new devices found".
I need help!!! How to send correct UDP response? I saw CaptivePortal and it is pretty awkward. I am sure that the text msg I prepare is correct - need just reformat it in binary I guess.
Thanks.
- Alexa sends UDP multicast request to discover devices
You are reading a single comment by @opichals and its replies.
Click here to read the full conversation.
Vasily
@opichals
The CaptivePortal example should be functional.
The connect call is asynchronous, so you would need to put the test code into the connect() callback function (right below the console.log()).