sehaas / ha_hisense_tv Goto Github PK

Hey guys,

I feel like I completed the hardest part of this venture. I successfully configured the MQTT. I have multiple Hisense TV and they all behave the same with WOL.

I recently purchase a VIDAA version and enable the WOL on both lan and wifi. the WOL is simply not constant. Sometime it works, sometime it doesn't.

I created a script to run

@echo OFF
FOR /L %%y IN (0, 1, 30000) DO WolCmd.exe MAC (All lowercase, no space) 192.168.1.0 255.255.255.0
PAUSE

Most of the time, when script is completed, the TV is on but it can take minutes before the TV actually turns on.

Any advise? for all my other Hisense TV, I simply run that command once and it works... not sure where to go from here.

Thansk.

since upgrading to 2022.6 the integration isn't working. There's this in the logs? and mqtt seems to be having issues?

2022-06-02 22:32:41 DEBUG (MainThread) [custom_components.hisense_tv.media_player] message_received_state - skip retained message
2022-06-02 22:32:41 DEBUG (MainThread) [custom_components.hisense_tv.switch] SWITCH message_received_state - skip retained message
2022-06-02 22:32:41 DEBUG (MainThread) [custom_components.hisense_tv.sensor] message_received_turnon
2022-06-02 22:32:41 DEBUG (MainThread) [custom_components.hisense_tv.sensor] message_received_turnon - skip retained message

1654204395: Connecting bridge (step 1) hisensemqtt (10.0.0.45:36669)
1654204395: Connecting bridge (step 2) hisensemqtt (10.0.0.45:36669)
1654204486: Connecting bridge (step 1) hisensemqtt (10.0.0.45:36669)
1654204486: Connecting bridge (step 2) hisensemqtt (10.0.0.45:36669)

2022-06-02 22:35:12 DEBUG (MainThread) [custom_components.hisense_tv.sensor] Skip update
2022-06-02 22:35:42 DEBUG (MainThread) [custom_components.hisense_tv.sensor] Skip update

I've restarted the host and the tv with no change.

There's also this but I'm not sure if it's relelated:

The 'away_mode_state_topic' option is deprecated, please remove it from your configuration
The 'hold_command_topic' option is deprecated, please remove it from your configuration
The 'hold_state_template' option is deprecated, please remove it from your configuration
The 'hold_state_topic' option is deprecated, please remove it from your configuration
The 'hold_modes' option is deprecated, please remove it from your configuration

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.

Hi again!

I am able to use this integration to control on/off via node-red fine, but when I try to change the source, nothing happens. Here is what my node-red command looks like:

When I try the same via the dev tools I get the same result:

When I watch the MQTT via a tool, I do notice that the action published is different from the one that the remote app publishes. It only includes sourceID and not sourcename. The remote app DOES work:

Here is the overall state of the TV:

Anything obvious that I am doing wrong?

Thanks!

infinite plugin loading on homeassistant . impossible to configure. Debian + docker tried other browsers the problem persists.

Hello,

Perhaps I've setup the bridge wrongfully, but I get stuck with:

2023-03-19 13:34:44.128 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - user_input is None
2023-03-19 13:35:04.232 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - set task_mqtt
2023-03-19 13:35:04.237 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish gettvstate
2023-03-19 13:35:04.237 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish sourcelist

How do I check if the bridge is correct?

My /share/mosquitto/hisense.conf:

connection Hisense
address 10.0.0.44:36669
remote_username hisenseservice
remote_password multimqttservice
cleansession false
clientid HomeAssistant
try_private false
topic /remoteapp/# both 0 hisense

I just installed the integration. Now it works like a charm.
But I can't power on the TV via Wake-on-WLAN.
If i switch the TV off, its state switches to "off" immediately followed by "not available" an I get this Error Message:
"Fehler beim Aufrufen des Diensts switch/turn_on. str, bytes or bytearray expected, not NoneType"

Hi

After upgrading HA Core to 2024.0.b0 I've got this error on this integration loading:

Error while setting up hisense_tv platform for media_player
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 368, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 662, in _async_add_entity
    capabilities=entity.capability_attributes,
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 1080, in capability_attributes
    ) and MediaPlayerEntityFeature.SELECT_SOURCE in supported_features:
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable

My hisense doesn't output any picture settings (is a couple years old) so the 5 minute polling of the state doesn't work as the actions/picturesetting is just ignored. Would it be possible to change to actions/gettvstate as that seems to be a standard function on all modals from searching through forums/posts on hisense tv about mqtt (or code it so that if actions/picturesetting doesnt return data so the sensor parameters are mainly blank*, then have actions/gettvstate be a fallback)

*Screenshot of what i get on the sensor - https://user-images.githubusercontent.com/22575856/212385144-102babc1-f0af-4503-a3fe-4c79d66a6fa3.jpg

add PR for basic change from one to the other, may attempt PR for second fallback option but outside of my tinkering comfort level so may take a while

Hi,

I have this integration working fine with HAOS 10.0 + mqtt 6.2.1 add-on.
However there are issues when I apply HAOS 10.1 update - the integration stops working.

I want to try and see what happens when mqtt is running on a different server than HA.
So I have built a new mqtt server and installed and configured mqtt. I have added a power plug that uses mqtt and that works fine without any issues.

I want to add this integration (HiSenseTV) to the new mqtt server but I have no idea how to go abut it and need help.

The power plug is a BK7231T device. All I had to do in the plug configuration is to point it to the new mqtt server. Next there is a button in the plug configuration web interface called "Start Home Assistant Discovery". After pressing that button the device appears in HA and works as it should.

I want to achieve something similar with the HiSenseTV integration (eg. have only one mqtt instance (the one running on a different server and not on the HA server) , but for HA to somehow discover the TV via this separate mqtt server - so I don't want to have a mqtt add-on in HA at al).

I will appreciate if anyone can help me achieve the above.

Cheers.

After installing with HACS, rebooting and adding in the integration, it prompts "Unable to load configuration wizard"

I have an idea that the readme assumes that the user should know a lot of things... however I'm really struggling.

Can it please be updated with relevant information? Or maybe send some resources on how to get started?

It'd be nice to be able to view the list of apps, and launch an app by selecting one from a list.

Enumerate apps:
publish:
/remoteapp/tv/ui_service/HomeAssistant/actions/applist
subscribe:
/remoteapp/mobile/HomeAssistant/ui_service/data/applist

Launch app:
publish:
/remoteapp/tv/ui_service/HomeAssistant/actions/launchapp
send JSON payload including name and url
E.g. launch built-in Youtube app:
{"name": "Youtube", "url": "youtube"}
E.g. launch Plex app installed from market:
{"name": "Plex", "url": "https://app.plex.tv/tv-vidaa"}

@sehaas I'm trying to work out how to add a game mode switch to the integration but unfortunately my knowledge of python is very limited so I'm really struggling. Looking at MQTT explorer I need to send the below for on or off:

{
	"action":	"set_value",
	"menu_id":	122,
	"menu_value_type":	"int",
	"menu_value":	1
}

{
	"action":	"set_value",
	"menu_id":	122,
	"menu_value_type":	"int",
	"menu_value":	0
}

to the topic /remoteapp/tv/platform_service/%s/actions/picturesetting

I can also see the state of game mode is being shown in the sensor as GameModeEnable but I really can't work out how to modify the switch.py to include this switch.

I've been having a go here but I've no idea how I define the state of the switch based on that GameModeEnable value or how I would disable the switch when the projector isn't on (I have a Hisense projector).

Could you assist?

G'day,
Thanks a lot for your work on this, I got a long way by reading and interpreting the instructions.
However, I have hit a roadblock getting the HA Mosquito bridge functioning.
The Mosquito log shows:
1642941765: Bridge local.HomeAssistanttotv doing local SUBSCRIBE on topic <MQTT_PREFIX>/remoteapp/# 1642941765: Connecting bridge hisense (192.168.xxx.xxx:36669) 1642941765: Bridge HomeAssistanttotv sending CONNECT 1642941765: Socket error on client local.HomeAssistanttotv, disconnecting.
Adding "log_type all" increased the log level, but didn't add anything useful.

I can successfully connect with MQTT Explorer using the files that "d3nd3 /Hisense-mqtt-keyfiles" has provided.
For example:
"vidaa_support": "1",
"country": "AUS",
"language": "eng",
"model_name": "55U62GAVT_0002",
"tv_version": "V0000.01.00M.L1110"
So I am confident that the "bridge_certfile rcm_certchain_pem.cer and bridge_keyfile rcm_pem_privkey.pkcs8" are correct (if I omit one or the other in MQTT Explorer it fails to connect.)
Interestingly MQTT Explorer does not even require TLS or a valid username/password to connect (I'm assuming read-only).

So any ideas as to what might be going on?

Update: While writing this post to get all the information correct, I restarted the HiSense TV and it just started to work!
1643842818: Received CONNACK on connection local.HomeAssistanttotv.

So...at this point I think its a bug with HiSense and not HA. But I thought it might be worth reporting as, during my googling, I noticed others with the same errors in their MQTT logs.

Cheers Ben

Tried it, with a bridge to the tv configured in mosquitto, but it did not work.

CIao I don't know why but I no longer see the list of TV channels, sources and media.
how come?

Integration is installed, but switch status is OFF (even with the TV ON) as long as I don't run the app once on my phone.
Then, the switch status is updated in HA and reflects the TV state (ON).
I can then kill the app on my phone and play with the integration (volume, channels and so on...)
If I switch OFF the TV, the switch in HA is updated to OFF.
But then I can no longer switch ON the TV from HA.
I need to use the TV remote to switch it ON.
And the switch in HA stays OFF, until I run the app on my phone again.
It is as if the TV broker needs to be activated by the app to work properly...

hi, I would like to create a scene in HA, which at 07 in the morning the TV turns on and positions itself on channel number 5.

I don't understand how to change the channel, I was able to turn it on, switch to the TV source but not change the channel and set the audio level.

how I can do it?

...

After I install this via HACS, reboot and then install the integration, I am prompted for the MAC address of the TV, which I provide, click "Submit" and then this screen starts spinning. I left it to run for 12 hours or so. I'm guessing it's stuck.

I've done the following:

• Ensured I installed MQTT correctly. I was able to verify it is up and running:
  
• I've tried restarting HA and going through the install process again, but the results are the same.

Is there anything I can enable on my side to provide more debugging info?

Thanks!

Hello,

I ask for help, I can't connect my TV to Home Assistant !

Please

https://postimg.cc/jL8bhy5w

#6 (comment)

Logger: homeassistant.components.switch
Source: helpers/deprecation.py:205
Integration: Schalter (documentation, issues)
First occurred: 08:40:38 (2 occurrences)
Last logged: 08:40:38

DEVICE_CLASS_SWITCH was used from hisense_tv, this is a deprecated constant which will be removed in HA Core 2025.1. Use SwitchDeviceClass.SWITCH instead, please report it to the author of the 'hisense_tv' custom integration

I've noticed that it takes a number of minutes for the integration to detect the off state.

Looking at media player, I can see that it does subscribe to /remoteapp/mobile/broadcast/platform_service/actions/tvsleep
and is processed by _message_received_turnoff at https://github.com/sehaas/ha_hisense_tv/blob/main/custom_components/hisense_tv/media_player.py#L403

Monitoring on the MQTT broker, it seems there is a significant delay in this above message being received. The TV however does seem to post the sleep state in /remoteapp/mobile/broadcast/ui_service/state. This is what I receive when the TV is off:

{
	"statetype":	"fake_sleep_0",
	"name":	"",
	"totaltime":	0,
	"curtime":	0,
	"starttime":	0,
	"playstate":	"",
	"mediatype":	"",
	"resolving":	""
}

This state is visible instantly. I have had a look at the processing of that state, but haven't been able to fully test making a change to the code there at this point.

If I get chance, I will try and test some changes. But open to suggestions!

I have a Hisense VIDAA TV and want to change scenes when streaming media is paused (e.g. bring the lights up sligtly).

Other than detecting when the mobile app sends the "enter" key, is there a way to force a VIDAA TV to report current media state? All I can see from the TV so far is which channel/streaming service is loaded. I haven't been able to detect Pause/Play events.

I can't get this to work on my 100U7KQ Hisense TV form 2023

If I connect to the TV from my MQTT Explorer with the following details it wont connect.
are there any changes on new hisense tv´s mine uses VIDAA as operation system.
I tryed with ectyption on/off and Validate certificate on/off with on luck

Hello, the installation of the integration stops at the stage of issuing a pin code. Pin code is not displayed on the TV. In my TV model MQTT works without SSL, TLS and certificates, I checked the commands through the MQTT service on homeassistant and on mqtt explorer, command works and connection is ok.
I tried in different browsers and on different operating systems.

connection hisense
address 192.168.1.66:36669
username hisenseservice
password multimqttservice
clientid HomeAssistant
bridge_insecure false
try_private false
start_type automatic
topic /remoteapp/# both 0

2022-07-15 08:54:07 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - user_input is None
2022-07-15 08:54:32 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - set task_mqtt
2022-07-15 08:54:32 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish gettvstate
2022-07-15 08:54:32 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish sourcelist

With the latest version, every time I restart Hass the TV's state is set to "on" regardless of it's actual state. This wasn't happening previously.

When I try the first setup and the TV is turned on. The integration requires a PIN code from the TV. The TV shows the PIN, however the integration doesn't provide a way to input the pin. would it need to be put into a config file?
Logs
022-05-01 18:08:53 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user INFO None
2022-05-01 18:10:43 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user NOT task_mqtt
2022-05-01 18:10:43 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _async_pin_needed

Hello.

I am having some issues. I can connect to my TV via MQTT and i have installed this integration via HACS. When i add the integration fill out the TV MAC Address and IP, Also change the prefix i just get the spinning wheel like its trying to add.

What i am not sure, Do i need to fill this out first? If so what file do i add the info to? Sorry that part was not clear to me.

connection hisense
address <TV_IP_ADDRESS>:36669
username <HISENSE_MQTT_USERNAME>
password <HISENSE_MQTT_PASSWORD>
clientid HomeAssistant
bridge_tls_version tlsv1.2
bridge_cafile hisense_ca.pem
bridge_certfile hisense_client.pem
bridge_keyfile hisense_client.key
bridge_insecure true
start_type automatic
try_private true
topic /remoteapp/# both 0 <MQTT_PREFIX> ""

Hi!

I've gone through through the entire installation with MQTT (you helped me several weeks ago), but I am finding that the Hisense TV Sensor is always unavailable. I've tried to uninstall and reinstall the integration and have double checked my IP/Mac Address settings, but nothing seems to change the situation. The log files looks fairly healthy to me, but perhaps you will see something I am not.

Ultimately I am trying to restore this as I want to be able to get and set the current TV source via HA, but when I inspect the state object of the switch, sensor and media player, I don't see an entry for source. I'm guessing it's supposed to be under sensor and it's not showing as the sensor is unavailable.

Here's the log: Home Assistant Log on Startup

Here are some supporting images:

Hi,

Think I am having a similar problem to #31 with a TV of model number: 43A6GTUK, but I cant seem to get the MQTT Bridge to work.

My config is as follows:

hisense.conf:

connection hisense  \
address 10.0.0.208:36669
username hisenseservice
password  multimqttservice
clientid HomeAssistant
bridge_tls_version tlsv1.2
bridge_certfile /ssl/rcm_pem_privkey.pem
bridge_keyfile /ssl/rcm_pem_privkey.pkcs8
bridge_insecure true
start_type automatic
try_private true
topic /remoteapp/# both 0 hisense""

with cm_pem_privkey.pem and rcm_pem_privkey.pkcs8 coming from the Acknowledgement section.

The logs I get are:

2022-10-05 22:32:35: Client local.HomeAssistant closed its connection.
2022-10-05 22:33:03: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:33:03: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:33:03: Client local.HomeAssistant closed its connection.
2022-10-05 22:33:31: New connection from 10.0.0.57:50029 on port 1883.
2022-10-05 22:33:31: New client connected from 10.0.0.57:50029 as mqtt-explorer-4d09194b (p2, c1, k60, u'alex').
2022-10-05 22:33:34: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:33:34: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:33:34: Client local.HomeAssistant closed its connection.
2022-10-05 22:34:05: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:34:05: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:34:05: Client local.HomeAssistant closed its connection.
2022-10-05 22:34:14: New connection from 172.30.32.2:52718 on port 1883.
2022-10-05 22:34:14: Client <unknown> closed its connection.
2022-10-05 22:34:36: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:34:36: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:34:36: Client local.HomeAssistant closed its connection.
2022-10-05 22:35:07: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:35:07: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:35:07: Client local.HomeAssistant closed its connection.
2022-10-05 22:35:38: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:35:38: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:35:38: Client local.HomeAssistant closed its connection.
2022-10-05 22:36:09: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:36:09: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:36:09: Client local.HomeAssistant closed its connection.
2022-10-05 22:36:14: New connection from 172.30.32.2:57756 on port 1883.
2022-10-05 22:36:14: Client <unknown> closed its connection.
2022-10-05 22:36:39: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:36:39: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:36:39: Client local.HomeAssistant closed its connection.
2022-10-05 22:37:10: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:37:10: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:37:10: Client local.HomeAssistant closed its connection.
2022-10-05 22:37:23: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:37:23: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:37:23: Client local.HomeAssistant closed its connection.
2022-10-05 22:37:48: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:37:48: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:37:48: Client local.HomeAssistant closed its connection.
2022-10-05 22:38:04: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:38:04: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:38:04: Client local.HomeAssistant closed its connection.
2022-10-05 22:38:14: New connection from 172.30.32.2:47910 on port 1883.
2022-10-05 22:38:14: Client <unknown> closed its connection.
2022-10-05 22:38:35: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:38:35: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:38:35: Client local.HomeAssistant closed its connection.
2022-10-05 22:39:06: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:39:06: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:39:06: Client local.HomeAssistant closed its connection.
2022-10-05 22:39:18: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:39:18: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:39:18: Client local.HomeAssistant closed its connection.
2022-10-05 22:39:33: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:39:33: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:39:33: Client local.HomeAssistant closed its connection.
2022-10-05 22:40:04: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:40:04: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:40:04: Client local.HomeAssistant closed its connection.
2022-10-05 22:40:14: New connection from 172.30.32.2:37532 on port 1883.
2022-10-05 22:40:14: Client <unknown> closed its connection.
2022-10-05 22:40:35: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:40:35: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:40:35: Client local.HomeAssistant closed its connection.
2022-10-05 22:41:06: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:41:06: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:41:06: Client local.HomeAssistant closed its connection.
2022-10-05 22:41:37: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:41:37: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:41:37: Client local.HomeAssistant closed its connection.
2022-10-05 22:41:46: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:41:46: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:41:46: Client local.HomeAssistant closed its connection.
2022-10-05 22:42:10: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:42:10: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:42:10: Client local.HomeAssistant closed its connection.
2022-10-05 22:42:14: New connection from 172.30.32.2:41430 on port 1883.
2022-10-05 22:42:14: Client <unknown> closed its connection.
2022-10-05 22:42:41: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:42:41: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:42:41: Client local.HomeAssistant closed its connection.
2022-10-05 22:43:12: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:43:12: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:43:12: Client local.HomeAssistant closed its connection.
2022-10-05 22:43:43: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:43:43: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:43:43: Client local.HomeAssistant closed its connection.
2022-10-05 22:44:05: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:44:05: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:44:05: Client local.HomeAssistant closed its connection.
2022-10-05 22:44:14: New connection from 172.30.32.2:50776 on port 1883.
2022-10-05 22:44:14: Client <unknown> closed its connection.
2022-10-05 22:44:23: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:44:23: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:44:23: Client local.HomeAssistant closed its connection.
2022-10-05 22:44:54: Connecting bridge (step 1) hisense (10.0.0.208:36669)
2022-10-05 22:44:54: Connecting bridge (step 2) hisense (10.0.0.208:36669)
2022-10-05 22:44:54: Client local.HomeAssistant closed its connection.

Using these certs in MQTT explorer I can access the MQTT broker on the tv, but don't know what the problem is!

When I try to set up the integration it just spins, and I have tried different browsers and devices but to no avail.

Any help would be appreciated, as I cant work out whats going on!

Thanks,

Alex

When the tv is off the integration show it as on.
When TV is off and i restart HA the TV show as off correct.

When TV is on all display fine and correct (input, channel .....).

But without restart HA is show permanent as on.

Not sure why, but I had to copy the files into custom_components before I could add the integration.
Is that how its supposed to work?

I try with this model, Hisense 50" QLED 4K 2021 50E78GQ, but no work !

I believe I've got everything setup correctly.

here's my config and all the certs are present:

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

here's what I see in the mosquitto logs:

and it appears to be connected:

but all I get in the config in HA is this:

I'm unable to proceed from this point.

i just got a Hisense qled TV.

i gave the integration the TV's ip address and mac. now it's just spinning.. any idea?

Noticed that only the App source appears available on my sources list - looks like you may have identified and are working on this issue - any workarounds in the meanwhile? i have tried the media.sources service but cant pass plain text

Thanks

README says it can be configured using Home Assistant UI. However, neither can it be found on HACS nor the official integration. Manually adding the repo to HACS will not result in successful downloads. Is there any way to manually configure this before the UI becomes available?

Hi Folks, I have a sharp HU43A6107UW running build K0829 on it.
This is a 43" 4K HDR set that is a Hisense series 6 and responds to a series 6 MQTT remoteapp subscriptions and posts.

The thing I am trying to configure out is the option to run without needing authorization and without SSL.

When I was using newAm's build (both based off the same code?) I could use the "--no-ssl " optional argument.
While in here I would assume this is needing to be done in the broker config, but I can't seem to figure it out.
I have removed all the broker config lines in regards to ssl and certificates, but I still get a loop or connect/disconnects.

Has anyone else figured out how to do this through the MQTT broker yet?
Thanks!

Hi, everything appears to be working perfectly other than I'm unable to turn off my device (Hisense Laser TV) it will power on fine but turning off does nothing, toggling the power switch will also just turn straight back on. Powering on works fine.

EDIT: actually I've just done some more testing and I've totally lost the ability to control the TV in any way - volume control, source etc don't work however they do update perfectly I If I use the Phone app or remote. I Have no control from within Home assistant?

Hello, thank you for your work. As I was installing I got this:

Logger: homeassistant.loader
Source: loader.py:786
First occurred: 01:32:49 (1 occurrences)
Last logged: 01:32:49

No 'version' key in the manifest file for custom integration 'hisense_tv'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'hisense_tv'

Currently channel selection is only via media browser if I use it correctly

Channel Up Down buttons that can used within UI would be nice

Hello after insert data from HA:

the circle always turns and does not finish the setup, why?

In HA, in which folder should the certificates be copied?

The config mentions three files:
bridge_cafile hisense_ca.pem
bridge_certfile hisense_client.pem
bridge_keyfile hisense_client.key

Can somebody point me in the direction of how to generate these files?

I've dug through the links provided, but the ones I can find use a hisense.crt file and I'm not smart enough to know if/how it translates.

Hello, I'm trying to add my hisense tv but after adding the requested information, Ha runs in a loop. yet I manage to connect in mqtt via Mqtt explorer.
No information in the logs

My TV needs the publish and subscription topic to be ">BLANK</remoteapp" and not "hisense/remoteapp"

Leaving subscription and publish topic blank during initial setup results in it defaulting to "hisense/remoteapp."
Setting the subscription and publish topic as '/' results in the topic to becoming ">BLANK</>BLANK</remoteapp"

I have been able to get it partially working with NodeRed by bridging topics, but it will be a pain to do this for every topic back and forth. Setup like this was difficult enough.

My TV is up to date. I have seen another user with this issue solve this by updating their TV in the HA Hisense thread, but it did not solve my issue.

Could there be any solution?

Thanks

After rebooting Home Asisstant TV is shown as ON. Does not respond to OFF/ON button. Turning ON tv manually solves the problem.

Hi,

After launching the integration setup, and entering the TV MAC Address:

the TV Shows the 4 digits code, but the integration doesn't move from the following screen:

I tried already to change browser, (I tried Opera, Edge and Chrome) and also the mobile APP.

Any ideas?