Bug #1929
TVadapters network error when implementing unicable switch
100%
Description
HI
i noticed there is a bug with how the configuration file was made when the unicable switch type was implemented,
the problem now is that its impossible to select normal switch (Generic) it wil defafult to unicable.
i have identified the problem to how the configuration file in home directory is created
by the way after this change i noticed it creates new configuration folder for the config files
old directory - ~/devices
new directory - ~/adapters
Correct Config:
{
"network": "f19457f8adcbe5cc670636304d86c59a",
"lnb_type": "Universal",
"switch_type": "Generic",
"enabled": true,
"priority": 0,
"displayname": "1w",
"uuid": "93ff1659958162095af43094ceac1f69",
"lnb_conf": {
},
"switch_conf": {
"committed": 0,
"uncommitted": 0,
"toneburst": 0
}
},
Default config created after unicable implementation:
{
"network": "6a15a8b549c99c5e75c8bc668e9ee352",
"lnb_type": "Universal",
"en50494_type": "en50494",
"enabled": true,
"priority": 0,
"displayname": "5e",
"uuid": "3e29a711ef15a757f1a814e382b254ff",
"lnb_conf": {
},
"en50494_conf": {
"position": 0,
"frequency": 0,
"id": 0,
"pin": 256
}
},
Subtasks
History
Updated by Adam Sutton almost 11 years ago
- Status changed from New to Accepted
Yes, for some reason its forcing Unicable enabled (although it also enabled standard switch). But I think the Unicable stuff will then completely mess with the standard stuff.
Adam
Updated by Adam Sutton almost 11 years ago
- Status changed from Accepted to Fixed
- % Done changed from 0 to 100
Applied in changeset tvheadend|commit:effdde2b2f081e41f271be1a27a3ddb59809098e.