Did you enter the parameter names (or part of the names) in the search field?
Yes, i.e. enter DECALCIFICATION_TIME nothing found
OK, that must be a bug in the AdminUI with Max-devices. With my Homematic devices i can find all these parameters.
Maybe 
, anyway i can find exposed some of those parameters in the underlying Home Assistant:
[climate.oeq0943015] auto hvac_modes: auto,heat,off min_temp: 4.5 max_temp: 30.5 target_temp_step: 0.5 preset_modes: boost current_temperature: 20.1 temperature: 18 preset_mode: null battery: High valve: 0 mode: Auto id: OEQ0943015 interface: wireless friendly_name: Radiatore Cucina supported_features: 17
that magically (!) manages to read…
Hi all,
I checked the code and found a bug, but not related to missing parameters 
Unfortunately I don’t have a BC-RT-TRX-CyG-2 but the BC-RT-TRX-CyG-3. And there are no settings for paramsetType “MASTER” on any channel other than 0. The settings you are searching for are on channel 1 with paramsetType of “VALUE”. These settings can be set within Node-BLUE (see screenshot).
– Micha
PS: direkt linking is noch possible with the admin-ui at the moment
Hi Micha,
ok, I hope the bug will be fixed sooner or later! I will try with node-blue!
Thank you!
Hi @arkimede,
the bug has nothing to do with this problem The AdminUI will only set “MASTER” settings of a channel …
– Micha
Ah, OK! …and what would be the bug (just to know 
)?
Hi @arkimede
the UI is showing channel 2, but this channel does not exist
[CHANNELS] (Array length=4)
[
(Integer64) 0
(Integer64) 1
(Integer64) 3
(Integer64) 4
]
– Micha
ah yes… sure…
sorry Micha, in what file is that fragment?
Hi @arkimede,
that’s not the content of a file, thats the output of the getDeviceDescription rpc-call:
homegear -e rc ‘print_v($hg->getDeviceDescription(36,-1));’
(Struct length=19)
{
[ADDRESS] (String) KEQ0717167
[CHANNELS] (Array length=4)
[
(Integer64) 0
(Integer64) 1
(Integer64) 3
(Integer64) 4
]
[CHILDREN] (Array length=4)
[
(String) KEQ0717167:0
(String) KEQ0717167:1
(String) KEQ0717167:3
(String) KEQ0717167:4
]
[FAMILY] (Integer64) 4
[FIRMWARE] (String) 1.0
[FLAGS] (Integer64) 1
[ID] (Integer64) 36
[INTERFACE] (String) VBC7665170
[NAME] (String) Heizung Besprechung rechts
[PAIRING_METHOD] (String)
[PARAMSETS] (Array length=1)
[
(String) MASTER
]
[PARENT] (String)
[PHYSICAL_ADDRESS] (Integer64) 820082
[RF_ADDRESS] (Integer64) 820082
[ROAMING] (Integer64) 0
[RX_MODE] (Integer64) 2
[TYPE] (String) BC-RT-TRX-CyG-3
[TYPE_ID] (Integer64) 416
[VERSION] (Integer64) 1
}
– Micha
ok, thank you!
Michele
Hi @arkimede,
the problem why the parameters are not settable through the UI is indeed that they are variables and not configuration parameters. I’m not sure anymore, why it is implemented that way, but there was a reason. So the easiest way is to set them through Node-BLUE. As an alternative you can use the command line, using: https://ref.homegear.eu/rpc.html#setValue (but putParamset() works as well).
Cheers,
Sathya
ok Santhya, i’ll try this way…
Thank you
Michele
direct linking is not possible with the admin-ui at the moment, is what he meant to write.
I understand, it’s a real shame! I was hoping for it!
Hi @Micha,
I saw that in the administration dashboard now it is possible to modify the variables, but only of channel 0 while those that interest me are on channel 1; unfortunately there is still the bug that channel 1 is not displayed while channel 2 that does not exist is displayed; is there any chance that this thing will be fixed? If not, can you tell me where is the code that manages that functionality? I could try to fix it myself
Thank you
Michele…