Open davidjbradshaw opened 1 year ago
I seem to have made some progress by directly editing /var/lib/hoobs/optomaprojectortelnetbridge/config.json
I had to do this using vi
, when I try and do it in Hoobs it just hangs on the save.
Edited Version
{
"bridge": {
"name": "Optoma Projector Telnet Bridge",
"pin": "xxx-xx-xxx",
"username": "C7:91:9F:39:84:5C",
"advertiser": "bonjour-hap"
},
"accessories":[
{
"accessory": "OptomaProjectorTelnet",
"name": "Projector",
"address": "192.168.0.139",
"model": "UHZ65",
"projectorId": 1
}
]
}
Original Version
{
"bridge": {
"name": "Optoma Projector Telnet Bridge",
"pin": "xxx-xx-xxx",
"username": "C7:91:9F:39:84:5C",
"advertiser": "bonjour-hap"
},
"accessories": [],
"platforms": [
{
"platform": "homebridge-optoma-projector-telnet",
"accessories": [
{
"accessory": "OptomaProjectorTelnet",
"name": "Projector",
"address": "192.168.0.139",
"model": "UHZ65",
"projectorId": 1
}
]
}
]
}
It would be really good to understand why the above change to the config makes a difference, I noticed your Pi-Hole template also moves accessories
up a level and removes platforms
. But the web interface seems to get upset when I try and do this directly in Hoobs.
Description This plugin connects to Optoma Projectors and allows HomeKit to turn them on and off
Expected behavoir Connect to projector and create device in HomeKit
Plugin name homebridge-optoma-projector-telnet
Please report the issue to the plugin developer https://github.com/simonrauch/homebridge-optoma-projector-telnet/issues/6
Version 1.0.7
Did you upgrade Please let us know if you upgraded from a previous version.
Pervious version None
Did you orginally upgrade to HOOBS 3 from HOOBS 2.1.1? Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
What device are you using? Please let us know the device you are running HOOBS on.
If this is a custom install, what's your operating system? Raspberry PI OS-lite (64 bit) Bullseye
Post your config
Post your log You can get the log from the intercafe. This is in the Log section.
Additional context I added extra logging to this plugin, but as far as I can tell it never calls the constructor.