Issue at first test after connexion

[jbperrin88]

Hello,

First of all, thanks for your work.

I was searching for this kind of stuff .

I'm using my own slef hosted pisignage server. I could like to use your plugin to connect to It.
Just after the first configuration , i've a error message:

I've already tested my credential with browser and curl request to the api.

I think it may be an issue this reponse format.

Best regards

[rohanwright]

Hi, Glad to see someone else give it a try, I wasn't sure if anyone would actually use this integration other than me!
I haven't tried it with the self hosted server, Could you turn on debug mode on the integration and give me some of the detailed logs so I can see what data is coming back from your server?

[jbperrin88]

No problem . i just don't kkow how to put debug mode for an integration not set

[jbperrin88]

i've try this

logger: logs: custom_components.pisignage: debug

[jbperrin88]

i've read the code .... and .. i prepare a first french version ;p

{ "config": { "step": { "user": { "title": "sélectionner le type de serveur", "description": "est-ce que vous utiliser le serveur officiel PiSignage.com ou un serveur self hosted?", "data": { "server_type": "Type de serveur", "server_type_hosted": "Officiel (pisignage.com)", "server_type_open_source": "Serveur open source" } }, "server_details": { "title": "Enter Server Details", "title": "Entrer les details de connexion", "description": "Entrer les details de connexion pour votre serveur pisignage", "data": { "host": "IP/Nom du serveur self-hosted ou nom d'utilisateur chez PiSignage.com", "port": "Port du Serveur (default: 3000)", "username": "Nom d'utilisateur / Mail", "password": "Mot de passe", "use_ssl": "utiliser SSL (HTTPS)" } }, "otp": { "title": "Authentification à deux facteur", "description": "Entrer le code OTP depuis votre application de double authentification", "data": { "otp": "Code ATP" } } }, "error": { "cannot_connect": "Erreur de connexion au serveur", "auth_failed": "Erreur d'authentification, verifier vos identifiants", "invalid_user": " Votre nom d'utilisateur / Mail n'est pas enregistré ou actif", "invalid_password": "Mauvais mot de passe", "timeout_connect": "délai d'attente de connexion depassé", "otp_failed": "Code OTP invalide, merci de réessayer", "unknown": "Erreur inattendue" }, "abort": { "already_configured": "Ce serveur PiSignage est deja configuré" } }, "options": { "step": { "init": { "title": "Lecteurs PiSignage ({players_count})", "description": "Configure options for PiSignage below.", "description": "Configuration des options pour PiSignage ci-dessous", "data": { "ignore_cec": "Selectionner les lecteurs ignorant la fonctionnalité CEC" } } }, "error": { }, "abort": { "no_players_found": "Aucun lecteur ¨PiSignage trouvé" } }, "selector": { "server_type": { "options": { "hosted": "Officiel (pisignage.com)", "open_source": "serveur open source" } } }, "services": { "play_playlist": { "name": "Play Playlist", "name": "Lancer liste de lecture", "description": "Demarrer une liste de lecture specifique dans le groupe de lecteur actuellement associé", "fields": { "entity_id": { "name": "Player", "name": "Lecteur", "description": "Le lecteur PiSignage à controller" }, "playlist": { "name": "Playlist", "name": "Liste de lecture", "description": "Nom de la liste de lecture à lire" } } }, "tv_control": { "name": "TV Control", "name": "Controle de la TV (CEC)", "description": "Turn on or off the TV connected to the PiSignage player.", "description": "Allumer / éteindre la TV connecté à votre lecteur", "fields": { "entity_id": { "name": "Player", "name": "Lecteur", "description": "The PiSignage player to control." "description": "Le lecteur PiSignage à controller" }, "status": { "name": "Status", "description": "Set to 'on' or 'off'." "description": "Régler sur « activé » ou « désactivé »." } } } } }

[jbperrin88]

i think it fails at _test_connection function .

It may be the correct behaviour cause from the API documentation , session api path is only accessible for official server and whitelabel servers

[jbperrin88]

With curl :

[rohanwright]

Ok, I've read the documentation 100 times, but I completely missed that the open source uses a different authentication method.
This will take a pretty significant change to my integration. I will have a look at it, but no promises on a timeline, as I’m pretty flat out next few weeks.

[jbperrin88]

if you have some tips ... i may try to find a solution.

I think the open source serveur only use basic auth for acces direct api endpoint ... i'll try to modify localy .

I keep you update .

Best regards

[rohanwright]

Can you please try v1.1.8-alpha, get me the logs if there are issues.

[jbperrin88]

Hey , First of all thanks for you reactivity !

It's working well ! I can connect and see my player in Home Assistant .

Thanks you so much for you work .

By the way , I've seen something strange ..

You call the api /playlistmedia directly on the server to play/pause , forward or backward asset.
But i really don't knwo why , this api endpoint exist but don't work on my self hosted server.
Even if if try with curl , i've a timeout response:

It may be a issue on pisignage , so I push to pisignage github.
colloqi/pisignage-server#226

I've success with direct player api with this query:

Best regard

[rohanwright]

Yeah I noticed none of those commands work. I thought I removed that functionality from my integration. The API docs are not great. It took a ridiculous amount of trial and error to figure out how to make most of the calls actually work.