-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get it to work properly #2
Comments
Can you make sure you are using the latest version of Mosquitto? Put the CA file in another folder, such as your home directory, since you are not using the Home Assistant Mosquitto addon. Further debug the issue, through this: https://github.com/tiagofreire-pt/Home_Assistant_Hisense_TV#further-debugging-or-exploring-the-mqtt-broker-inside-the-tv (the bottom) |
Damn, I really thought I had it. Moving the CA file to another folder worked at first, but as soon as the TV is switched off, the Mosquitto broker is stuck in a restart loop again. Here's the message:
This only happens when the TV is off. When it is on again, the restart loop stops. |
It works now! You may include this in your instructions, because I have the feeling I will not be the only one who
|
Thanks for posting your solution! |
Hi there,
there seems to be something wrong with how the config of the MQTT Bridge is done. Everything works for me for approx. 2 minutes and I can control the TV during that time, but after that it doesn't work anymore and when I look into the log of my MQTT broker, it shows constant restarts (which are only there if I have the MQTT bridge to the Hisense TV defined):
A closer look into
/var/log/mosquitto
shows the following:Apparently there is something wrong with my hisense.crt file. However, I created it according to your instructions and the file looks like this:
Here is my hisense.conf file:
Hmmmmm... I tried to manually verify the hisense.crt file and the output is ok:
openssl s_client -host 192.168.1.203 -port 36669 -CAfile ../ca_certificates/hisense.crt
The text was updated successfully, but these errors were encountered: