Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13
  1. #11
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    192
    Quote Originally Posted by ynot1234567890 View Post
    Hi,

    1. Yes the hostname (myserver) in your case. The http:// part is not required. It could even be the ip address if you prefer. The CLI port number which unless you changed something should be 9090. It's a different port than the web interface port 9000. The Command Line Interface Port (CLI) that responds to requests is set to 9090 by default. You can confirm this by choosing settings, advanced and selecting command line interface on the LMS web app. It will show you the CLI port number for your installation.

    2a. For the system to work it needs to be reachable from the internet. Most HASSIO users use a free service called duckdns.org to keep track of their ip and route the internet requests to the hassio service. So first you need to have this service available and installed, I suggest the using the DUCKDNS form the ADD_ON store in your HASSIO config. Once you can access HASSIO from the internet, HA_Link is the name of your server without the domain part. As an example, my server may be reached by typing https://helloworld.duckdns.org my HA_Link value would then be helloworld.

    2b. HA_API_Password is the password you created (or should have created) to access HASSIO. This can usually be found in your configuration.yaml file under the http: heading.

    The key before you go too far is first to ensure HASSIO is working on its own and is accessible from the internet. Until this works, you're dead in the water as far as voice commands, etc due to cloud service requirements. On the Github there is also a troubleshooting document https://github.com/ynot123/LMS_Controls/blob/master/troubleshooting.md to help during your setup.

    I appreciate any feedback on lack of instructions, clarification requirements, etc.. Most users to date already had working versions of HASSIO installed so less setup was required. Also, I may be offline for a few days (fishing) but will get back to any requests / questions upon my return.

    Cheers, Ynot.
    1. I figured you meant hostname/ip but the term "path" confused me. Probably better to use the term "hostname".

    2a. That is sorta what I was expecting you to say. I already have a dynamic dns service I use to make my home server accessible from the internet. Since the home server is getting the standard http and https ports forwarded to it, I guess I'll need to use a non-standard port id for Home Assistant API. So I'll have something like "https://rgdawson.homeserver.com:9443/api/states/sensor.art_ID?api_password=HA_API_Password". And I'll set my router up to forward port 9443 to the Home Assistant R-Pi. I think I need to configure the Home Assistant API to use a different port somewhere.

    R Greg Dawson
    Last edited by rgdawson; 2018-08-07 at 11:40.
    Squeezelite-X

  2. #12
    Quote Originally Posted by rgdawson View Post
    1. I figured you meant hostname/ip but the term "path" confused me. Probably better to use the term "hostname".

    2a. That is sorta what I was expecting you to say. I already have a dynamic dns service I use to make my home server accessible from the internet. Since the home server is getting the standard http and https ports forwarded to it, I guess I'll need to use a non-standard port id for Home Assistant API. So I'll have something like "https://rgdawson.homeserver.com:9443/api/states/sensor.art_ID?api_password=HA_API_Password". And I'll set my router up to forward port 9443 to the Home Assistant R-Pi. I think I need to configure the Home Assistant API to use a different port somewhere.

    R Greg Dawson
    1. I will clean up the documentation to reflect hostname.
    2. Alternate ports should work as well, the shell scripts and configuration.yaml files will need to be updated to reflect this fact.
    3. I find the easiest way is to ensure the HA instance is working properly first over the internet using https: links before tackling the LMS and Dialogflow portions. There is a fair bit of documentation available in securing HA and the use of SSL and alternate ports.


    Ynot

  3. #13

    Upcoming update to Google Home Voice Control of LMS Players

    Hello All,

    A quick FYI with regards to the Voice Control of LMS players from GoogleHome using Home Automation software as the middle man.

    I will be doing a minor update over the next couple of weeks which will include:
    • Cleaning up / stream lining the DF API upgrades from API V1 to V2, refining of entities to reduce configuration requirements and provide more flexible naming conventions, modifications to allow sync of all defined players
    • Update the HA GUI to include up to 10 sync players
    • Update of Spotify shell scripts to improve accuracy of query results


    If you have any thoughts or ides on how to improve this tool, please feel free to email me the ideas for consideration. These can include DF functionality, HA GUI / script additions, or any other features you think might be useful for this application. yland@vianet.ca

    Thanks in advance, Ynot.
    Software - Logitech Media Server Version: 7.9.1, Home Assistant 0.75.3, DialogFlow - V.2 API, LMS Controls App - Voice Control of LMS, OpenMediaVault 4.1.9 - Storage
    Add-ons - Spotty, UPnP / DLNA Bridge, ChromeCast Bridge,
    Players - Sonos, UPNP, PI3 - PI Core Player 3.5.0, Android- SB Player V1.4.0, AirPlay to GoogleHome and Minis
    Hardware - Server - i7-3.4Ghz, 4GB Ram, 6TB storage, Debian - 4.16.5

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •