ha_hisense_tv: Update Mosquitto Addon to 6.2.0 breakes proper working ha_hisense_tv

In fact after update it is only impossible to switch on tv, so I don’t know why Mosquito update break WoL.

After manual TV on (local button ora IR remote), all works OK.

(bad) Mosquitto addon 6.2.0 uses Mosquitto 2.0.15 (working) Mosquitto addon 6.1.3 uses Mosquitto 2.0.11 https://mosquitto.org/ChangeLog.txt so maybe you can find dependecies with non-working WoL…

When TV is off it generates errors (something like this was also existing in old Mosquitto, I’ll downgrade addon to show later)

2023-03-28 15:44:18: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:44:30: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:44:33: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:44:58: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:45:01: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:45:32: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:45:35: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:46:06: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:46:09: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:46:40: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:46:43: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:46:54: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:46:57: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:47:06: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:47:09: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:47:26: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:47:29: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:48:00: Connecting bridge Hisense (192.168.20.60:36669)
2023-03-28 15:48:03: Client local.HomeAssistant disconnected: Protocol error.
2023-03-28 15:48:34: Connecting bridge Hisense (192.168.20.60:36669)

mqtt bridge configuration (file ‘hisense.conf’ located in ‘/share/’, certificates located in /ssl/hisense/)

connection Hisense
address 192.168.20.60:36669
remote_username hisenseservice
remote_password multimqttservice
cleansession false
clientid HomeAssistant
bridge_tls_version tlsv1.2
bridge_cafile /ssl/hisense/hisense_ca.pem
bridge_certfile /ssl/hisense/rcm_certchain_pem.cer
bridge_keyfile /ssl/hisense/rcm_pem_privkey.pkcs8
bridge_insecure true
start_type automatic
try_private true
topic /remoteapp/# both 0 hisense

Edit: After addon downgrade nothing changed, so problem lies elsewhere, but recent day there was many updates, so I’m downgrading HA now.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 40 (3 by maintainers)

Most upvoted comments

I also had problems with mosquitto add-on new version, I decided to replace it with EMQX, got some troubles setting up the bridge, but now everything is working

can you share your config? Have Ingress (receiving data) working with EMQX but can’t seem to get Egress working.

Ingress remoteapp/# >> hisense/remoteapp/# Egress hisense1/remoteapp/# >> remoteapp/# using topic rewrite

Screenshot from 2023-06-29 08-03-00 Screenshot from 2023-06-29 08-02-09 Screenshot from 2023-07-08 09-17-24

OK so I am back with some feedback. I have built an mqtt server and got it working with HA and HiSense TV integration. I can now reboot HA and have the integration running fine. However, if I reboot the mqtt server the integration will stop working.

Need to restart mqtt to get it going again.

No sure where the issue is - is it Home Assistant or it is an mqtt issues? not sure. In the new server I am using the official mqtt docker for this not the HA one.

Can anyone confirm if the bride is still working with Mosquitto 2.0.15 and the MQTT messages are still available there?

Answering myself: Can confirm the bridge is still working under 2.0.11, but not under 2.0.15. I’ll try to narrow it down, but can’t give you any ETA. If anyone want to help, please increase the Mosquitto loglevel and look for something SSL/certificate related.