-
Notifications
You must be signed in to change notification settings - Fork 1
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
TLS Error in Homebridge #3
Comments
Hey @ryanshand I was confused when I saw the E-zone config for a second and worried I uploaded the wrong config to this! Awesome to see you trying to use both of my repos :) I am away from home until tomorrow night, but hopefully we can get something going for you. First off what model of Hisense TV is it and do you know which version of VIDAA it uses? A TLS issue sounds like an encryption issue, the use of insecure mode and the cert in my commands should get us around this… Can I get you to try the following command from your terminal?
Just replace |
the Aircon plugin is wicked, total life-saver. So I did bit of research into the mosquitto_ commands and found this has the same issue that @Mraus so for my TV, the 70S5, software version V0000.01.00T.L0305 you need to pass in some certificates - I have attached them here put them somewhere on your box, and then the command changes to below - this works! I have attached my fully working solution
|
I am glad to hear you love the air con shell script :)
I am pretty sure you should be able to use the ‘no temp sensor’ version and set the state or temps without a temp sensor; please let me know there is an issue there that I need to look into! Or is this an issue with how the MyAir app displays it on the actual app? To be honest I didn’t have the temp sensors at first and then shelled out for the lot; they do deals on them at certain points of the year so keep an eye out for that.
Interesting, so for your model you actually have a slightly different command? By requiring this cert chain and private key. Good on you for finding this out, not a lot of people do their own googling! I can’t open your zip file on my phone but will take a look when I get home tomorrow.
This is I believe a limitation of Apple. From the Home app you can not change channels. It won’t let me connect to this away from home, but if you check the ‘remote’ in your control centre (add it from settings if you don’t); then you can control more of the TV from here. I still don’t think it gives you a number keypad but I think you can you the up and down key to change the channel (not ideal I know, but once again Apple limitations). |
Ah ok gotcha. just something i'm messing with.
|
I like what you are experimenting with! You could also create Switch accessories to act as your channels (would have to make a heap of them); just take a look at how my Personally all I ever use my TV accessory for is the on/off function through Siri but hated not seeing a TV in my home; then this became about making the fully functioning TV accessory for everyone else. Sometimes I change the input through the Home app when the remote is out of reach as my phone is always on me lol hopefully Apple up their game with a lot of their accessory services across the board in the coming years. |
Ah that’s a cool idea, I don’t mind the idea of using switches. I gave up my developer license because I’m a cheapskate so I don’t have access to the HomeKit SDK. Might have to bite the bullet and sign up again |
There would be a trick to it with that approach as you would need to use the |
Also what is HomeKit SDK? I’m still pretty new to all this stuff! |
I ended up just reading a bunch of the doco on Homebridge and its limitations regarding RemoteKey. It's kind of a pain in the arse, it doesnt support volume control, channel control or other functions that RemoteNOW does. That's not your fault or anything I just mean to say it's a limitation. I've got my setup pretty much exactly the way I want it now, so I'm going to sit on it for a while. For what it's worth, I'll share my set up with you. After some dicking around using MQTT Explorer monitoring API calls, while using RemoteNOW on my phone, I found that RemoteNOW can set the TV to a specific TV Station - regardless of what Input is currently shown, OR if the TV is off. Use case: TV is powered off (standby) - you can go into the "favourites" part of RemoteNOW app, press channel 10, and the TV will power on, and show channel 10 - even if it was on HDMI1 when it was on standby. It does this using the changechannel call. /remoteapp/tv/ui_service/$normal/actions/changechannel and passing in channel_param you get the list of available channels from the TV directly using MQTT - I have attached mine, not sure if they're specific to each TV or static - but a sample is below
so an example API call to change to channel 10 for my TV is
Now, because RemoteKey is limited - I decided I didn't need all of the TV inputs you pull in (e.g. I don't need AccuWeather, TV browser, Foxtel etc - so I hijacked those and just replaced the commands with ones to do the following: Change to Channel 7 In Home app on my phone, it presents as below. Using the Shortcuts app, I then create shortcuts to do the actions. The shortcut is:
I then Google Image searched the logos for each station, and added the shortcut to my home screen of my phone. So now I have pretty much full control via voice or device. I don't typically watch any other stations like ABC, SBS etc so I didn't bother doing the others, but hopefully this gives you some ideas if you want to do something to cover all bases. I'm getting a bit of pressure from the missus to get off the computer, so need to park this. I've attached my shell script, my Homebridge config file, the certificates and the channel list. Cheers Ryan |
Yeah like I said it is limited thanks to Apple and hopefully they will improve it in the future.
That is pretty much how I created all of this; it’s really annoying messing around with it all to be honest and probably had a bit to do with why I put off making the full published version I put online for a few months; versus the simpler implementation I use myself (my inputs are just TV and HDMI1) and the remote through the control centre (as limited as it is). I really like what you have put together and how you have implanted it; nice job!
I also get a bit of this and completely understand. My wife has probably been more patient than she has had to be through the whole e-zone and hisense work lol I have been pretty flat out lately, but mean to have a good look over your work and can add it up here on the repo to help anyone else who has the same model as you (I will make sure to credit you of course). I’ll close this out for now seen as everything is working. And if you have any ideas or troubles here or with your ezone; just reach out and I’ll be happy to help or brain storm. Been a pleasure chatting with you Ryan! |
I'm having some trouble setting an input and getting the channel buttons when I set up my homebridge.
The HisenseTV is added to HOME app and I can see the inputs TV, Netflix, HDMI1, HDMI2 etc.
however when i change the inputs on the HOME app on my phone, the TV does not respond.
Describe Your Problem:
I have added the accessory to Homebridge CMD4 per the instructions.
I have successfully got the TV to appear in my iOS Home app - so the MAC and IP setings are correct.
I can connect to the TV using MQTT explorer.
However it appears that not all functions are working - specifically there appears to be a TLS error when running the ActiveIdentifier function - I am not familiar with mosquitto_sub command to know why there is a TLS error, but I can confirm the certs are correct as I can connect manually to the television via MQTT explorer using the certs.
the error seems to relate to this, but I don't know what in the shell script it refers to
getValue: accTypeEnumIndex:( 4 )-"ActiveIdentifier"
Link to Logs:
Paste of Logs:
Cmd4 Config:
Screenshots:
![image](https://user-images.githubusercontent.com/83274883/116975535-60bd1680-acf2-11eb-882b-942e08bd2a0c.png)
Environment:
hisense.txt
HisenseTV.txt
The text was updated successfully, but these errors were encountered: