Alexa Integration

aa6vh's Avatar Topic Author
User User
  • Posts: 111
  • Thanks: 7

Alexa Integration

1 year 5 months ago
#4210
I have been trying to send commands to MyServer (version 6.8.236.34236), as described in the blueprint for sending commands to Allonis using the IFTTT service (as described in allonis.com/support/documentation?view=category&id=219 ). Unfortunately port 6246 returns "connection refused". I am trying this from inside my LAN, so this should not be a firewall problem, nor port forwarding problem.

Questions: Has the capability been removed? Has port 6246 been changed to another port? Is there a setting or option that needs changing?

I also tried requesting the "ServerStatus" (as described in "myServer Command Syntax", and which also uses port 6246), and still get that "connection refused" error. Sending to port 9001 ("Live Event Log") does work like it should.

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Alexa Integration

1 year 5 months ago - 1 year 5 months ago
#4211
That's some old documentation from back in the MLServer days (pre-myServer 6). From distant memory, that port 6246 was the webserver port. Now, default is a more standard port 80. Within myServer 6 you can change that port to what you want in the configuration tab. But recommended is to keep it default.

Try that...see if that works.

The NMAP Linux command can ping a networked device to see what ports are currently open.  FYI
Last edit: 1 year 5 months ago by David Li.

Please Log in or Create an account to join the conversation.

aa6vh's Avatar Topic Author
User User
  • Posts: 111
  • Thanks: 7

Re: Alexa Integration

1 year 5 months ago - 1 year 5 months ago
#4213
Thank you for your response.

Well, as expected, port 80 is open. Was the capability of sending an Allonis command via the old port 6246 removed/omitted in myServer6, instead of moving that capability to port 80?

Sending the url "http://<ip>:80/command?..." as described in that old documentation returns a 404 error, page not found.
Last edit: 1 year 5 months ago by aa6vh.

Please Log in or Create an account to join the conversation.

bowlingbeeg's Avatar
User User
  • Posts: 248
  • Thanks: 33

Re: Alexa Integration

1 year 5 months ago
#4214
If you want to send a command to myServer you use the api
http://<ip>/api/docommand?command=<command>
The following user(s) said Thank You: aa6vh

Please Log in or Create an account to join the conversation.

aa6vh's Avatar Topic Author
User User
  • Posts: 111
  • Thanks: 7

Re: Alexa Integration

1 year 5 months ago
#4215
bowlingbeeg,

That exactly what I have been searching for! Alexa control, here I come (and without using IFTTT also),

Many thanks

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Alexa Integration

1 year 5 months ago
#4216
re: Alexa - that's neat. Please post on how you are implementing.
Note that the SmartRemote Voice button does a voice to text to a myServer var....put that into the mix :)

Please Log in or Create an account to join the conversation.

Time to create page: 0.324 seconds