Hisense TV Control

Configuration
328

For me this is still working, but i’m using it with a very old Hisense TV, not sure if it’s still working with newer models.

You have also done the MQTT Brdige configuration?

This is inside my mosquitto.conf file as i’m running MQTT as docker and not as Addon

allow_anonymous false
password_file /mosquitto/config/pwfile
listener 1883

# Hisense TV Wohnzimmer
connection hisense
address 192.168.2.85:36669
username hisenseservice
password multimqttservice
clientid HomeAssistant
start_type automatic
topic /remoteapp/# both 0 hisense ""

Then for sure before trying the HACS integration you could first publish some messages to that topic /remoteapp in order to see if you get results

1 Like
329

I completely left this aside for this last month, when I have a chance I’ll test your config out, thanks for sharing!

330

I need Help, my Mosquitto Broker stopped

[06:02:02] INFO: Starting mosquitto MQTT broker...
1722571322: Loading config file /share/mosquitto/hisense.conf
1722571322: Error: Unknown configuration variable "connection".
1722571322: Error found at /share/mosquitto/hisense.conf:1.
s6-rc: info: service legacy-services successfully started
1722571322: Error found at /etc/mosquitto/mosquitto.conf:43.
[04:02:02] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[04:02:02] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

hinsense.conf

connection hisense
address 192.168.0.62:36669
username hisenseservice
password  multimqttservice
clientid HomeAssistant
bridge_tls_version tlsv1.2
bridge_cafile hisense.crt
bridge_certfile rcm_certchain_pem.cer
bridge_keyfile rcm_pem_privkey.pkcs8
bridge_insecure true
start_type automatic
try_private true
topic /remoteapp/# both 0 hisense ""
331

Hello. Do I need an emulator for this to work? What about connecting to the tv with my physical android device, then sniffing packets from my laptop (all three devices on the same network)

332

solved the problem? I didn’t succeed, replaced the mac addresses, nothing worked, they apparently changed their certificates after the firmware, you need to look for new ones

333

I know this is an old thread, but thought I might add a data point…
I have just this weekend got this working on my (older) Hisense TV…
TV Model: 65R6
SW Version: V0000.01.00a.N0104

Using this integration; GitHub - sehaas/ha_hisense_tv: Hisense TV integration for Home Assistant

My TV did not require the client certificates, but Mosquitto did require the TVs certificate in order to connect… I used the command from here to extract it; GitHub - tiagofreire-pt/Home_Assistant_Hisense_TV: Integration of smart TVs from Hisense on Home Assistant Core

My Mosquitto is a standalone container, and I added this to the config file;

# Hisense TV
connection hisense
address 192.168.xxx.xxx:36669
remote_username hisenseservice
remote_password multimqttservice
clientid HA.TV
bridge_cafile /mosquitto/config/hisense.crt
bridge_insecure true
start_type automatic
topic /remoteapp/# both 0 hisense ""

Once the MQTT bridge was up I added the Integration, typed in the PIN from the TV when requested (although this took a couple of tries before the PIN entry dialog popped up) and voila… TV control in HA!

The integration does raise a few errors in the logs for using deprecated features, but it seems to work so far.

Cheers.

1 Like