Can't get TV buttons to show up in HomeKit #714
Comments
|
From my limited understanding, you won't see it in HomeKit but you should see it in Remotes |
|
Hello, the device does not appear automatically, you have to:
1. Add a device in the home app
2. Select "device not found"
3. The TV accessory will appear
4. You select it and read the HomeBridge QR code.
From here you will turn on the TV and choose the source from the home application, but you will control the volume from the cell phone remote control
Gastón
… El 4 jul 2024, a las 01:37, NikoV5 ***@***.***> escribió:
I dont think this is a bug but rather my ignorance considering I just started using home bridge but I can't for the life of me figure out how to get the tv power on/off and the remote to show up. I have a broad link rm4 mini and it seems to have no problem connecting with HomeKit as the learn and scan frequency buttons work but when I map the remote buttons and add everything to the json config file and then reboot and then go into the home app, the accessory doesn't show up. I dont think anything is wrong with my config file but I can send it if need be.
I was also thinking that maybe this is happening because the rm4 mini device was already setup in the broad link app and it has to be a fresh install? But then again HomeKit is connected to this device so I dont think that is the issue either.
—
Reply to this email directly, view it on GitHub <#714>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APBDDDEALASK2BR6F7DKYVTZKTGQTAVCNFSM6AAAAABKKYFDOCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DSOJRHE3DOMY>.
You are receiving this because you are subscribed to this thread.
|
When I click the remote it still doesn't appear |
Hello. After doing this it still doesn't appear. Is there something I'm supposed to do to link the plugin to my actual tv? All I did was map hex codes that I got from my BroadLink rm4 mini but is there something else I'm supposed to do? |
|
I have the HOSTS configuration on BROADLINK platform like this (I have 5 rm4 mini):
"hosts": [
{
"address": "10.0.0.20",
"mac": "MAC_ADDRESS",
"isRFSupported": false,
"isRM4": true
},
{
"address": "10.0.0.21",
"mac": "MAC_ADDRESS",
"isRFSupported": false,
"isRM4": true
},
{
"address": "10.0.0.22",
"mac": "MAC_ADDRESS",
"isRFSupported": false,
"isRM4": true
},
{
"address": "10.0.0.23",
"mac": "MAC_ADDRESS",
"isRFSupported": false,
"isRM4": true
},
{
"address": "10.0.0.24",
"mac": "MAC_ADDRESS",
"isRFSupported": false,
"isRM4": true
}
I have the ACCESORY configuration like this (host MUST be the rm4 mini accord to hosts configuration):
{
"name": "TV Comedor",
"type": "tv",
"host": "10.0.0.21",
"data": {
"on": "HEX_CODE",
"off": "HEX_CODE",
"remote": {
"select": "HEX_CODE",
"back": "HEX_CODE",
"exit": "HEX_CODE",
"info": "HEX_CODE",
"arrowUp": "HEX_CODE",
"arrowDown": "HEX_CODE",
"arrowLeft": "HEX_CODE",
"arrowRight": "HEX_CODE",
"playPause": "HEX_CODE"
},
"volume": {
"up": "HEX_CODE",
"down": "HEX_CODE"
},
"inputs": [
{
"name": "Apple TV",
"type": "hdmi",
"data": "HEX_CODE"
}
]
}
}
Gastón
… El 8 jul 2024, a las 14:01, NikoV5 ***@***.***> escribió:
Hello, the device does not appear automatically, you have to:
Add a device in the home app
Select "device not found"
The TV accessory will appear
You select it and read the HomeBridge QR code.
From here you will turn on the TV and choose the source from the home application, but you will control the volume from the cell phone remote control
Gastón
El 4 jul 2024, a las 01:37, NikoV5 @.***> escribió:
I dont think this is a bug but rather my ignorance considering I just started using home bridge but I can't for the life of me figure out how to get the tv power on/off and the remote to show up. I have a broad link rm4 mini and it seems to have no problem connecting with HomeKit as the learn and scan frequency buttons work but when I map the remote buttons and add everything to the json config file and then reboot and then go into the home app, the accessory doesn't show up. I dont think anything is wrong with my config file but I can send it if need be.
I was also thinking that maybe this is happening because the rm4 mini device was already setup in the broad link app and it has to be a fresh install? But then again HomeKit is connected to this device so I dont think that is the issue either.
—
Reply to this email directly, view it on GitHub #714 <#714>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBDDDEALASK2BR6F7DKYVTZKTGQTAVCNFSM6AAAAABKKYFDOCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DSOJRHE3DOMY.
You are receiving this because you are subscribed to this thread.
Hello. After doing this it still doesn't appear. Is there something I'm supposed to do to link the plugin to my actual tv? All I did was map hex codes that I got from my BroadLink rm4 mini but is there something else I'm supposed to do?
—
Reply to this email directly, view it on GitHub <#714 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APBDDDH57MOMVLAQXJU6LLLZLLAVHAVCNFSM6AAAAABKKYFDOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUG4YDSNJXGM>.
You are receiving this because you commented.
|
Okay and just to clarify the MAC address and up address you get from the rm4 mini correct? That's what I was doing I just wanted to make sure. But I think my issue is that for the tv I didn't put "host" with the 4 mini ip address. When I get off work I'm gonna try that later |
I dont think this is a bug but rather my ignorance considering I just started using home bridge but I can't for the life of me figure out how to get the tv power on/off and the remote to show up. I have a broad link rm4 mini and it seems to have no problem connecting with HomeKit as the learn and scan frequency buttons work but when I map the remote buttons and add everything to the json config file and then reboot and then go into the home app, the accessory doesn't show up. I dont think anything is wrong with my config file but I can send it if need be.
I was also thinking that maybe this is happening because the rm4 mini device was already setup in the broad link app and it has to be a fresh install? But then again HomeKit is connected to this device so I dont think that is the issue either.
The text was updated successfully, but these errors were encountered: