closed by mistake(have no idea how that happened) big Fibaro home center 2 listing as devices panels and other “ Remotes” as I realized which are not supposed to be listed as such. Please continue kindly to handle the issue and see my proposal ahead

[candybars2001]

          I have done a first analysis and added the info available from fibaro API of one panel in the attached file for your reference.

onepanel.txt

Unfortunately there is no special identifier which can help in identifying the panel. It just contains type and baseType attributes as used in many other devices. So a change just for this special panel device is not possible. What changes per sub entity is the endpointId, but this is as well the case for some climate and RGB devices. So I think this is also not an option.

So I'm a bit lost how we should improve that...

@MartinHjelmare Do you have some best practice from zwave_js implementation how to group z-wave entities in devices? Currently the fibaro integration creates one device per hardware device which is not optimal for complex devices (e.g. a double switch) where you can for example use one switch for bathroom and second for the kitchen so logically showing the hardware device makes no sense and an end-user expects two devices to see.

Originally posted by @rappenze in https://github.com/home-assistant/core/issues/94137#issuecomment-1591998052

[candybars2001]

There are other messages that may be interesting in the original thread but this was my proposed solution. I don’t know how this mistakenly was marked by me as a closing of the case rather than a comment I apologize. I think when I hit comment I don’t realize that the default is for the second comment to close the issue. Sorry about that again. Here’s the last message I posted

OK so I think I may have realized where the problem lies by daring to look inside the json file. While both physical devices that are meaningful such as binary light switches, multilevel switch (dimmer) and panel, are “actors” (and appear in the configuration user interface under devices), the panels are device type “ remote controller”, of which I have hundreds in the user interface, and I believe that anything that activates a meaningful device or scene, is called a remote. Since you can activate a real device or scene by pressing a button or in other ways to just voice commands, those remotes are not real entities and are or ignored in the various integration. For example, Kitchen Island Lights is device type com.fibaro.binarySwitch:

from the json file:

{"id":476,"name":"Island Light","roomID":220,"type":"com.fibaro.binarySwitch","baseType":"com.fibaro.actor","enabled":true,"visible":true,"isPlugin":false,"parentId":472,"remoteGatewayId":0,"viewXml":false,"configXml":false,"interfaces":….

and study Uplight is device type com.fibaro.multilevelSwitch:

{"id":513,"name":"Study Uplight","roomID":221,"type":"com.fibaro.multilevelSwitch","baseType":"com.fibaro.binarySwitch","enabled":true,"visible":true,"isPlugin":false,"parentId":508,"remoteGatewayId":0,"viewXml":false,"configXml":false,"interfaces":…

panel C is Device type com.fibaro.remoteController:

{"id":474,"name":"Panel C","roomID":220,"type":"com.fibaro.remoteController","baseType":"com.fibaro.actor","enabled":true,"visible":true,"isPlugin":false,"parentId":472,"remoteGatewayId":0,"viewXml":false,"configXml":false,"interfaces"….

and then the configuration user interface, as stated, there are many of these remotes that are rightfully ignored, as can be seen in screenshots of “ devices” UI configuration page, and here are a couple of screenshots from that section:

Also, I don’t know how to delve into the Fibaro integration page on Holbridge, but here’s a screenshot of the devices there, no Remotes:

hope this can help thanks again

[MartinHjelmare]

Don't open a new issue. Just reopen the closed issue. Also please don't tag people at random.

I'd also recommend to try and describe the problem in less words.

[candybars2001]

I apologies I don't know what it means to tag and that I did this. Also as i me mentioned, I don't know how to reopen an issue. Could you kindly explain (I'll try to be convince but if you could in detail?" Since it appears you closes this issue for me and did not reopen the other, I'm kind of stuck again. Thanks.

Don't open a new issue. Just reopen the closed issue. Also please don't tag people at random.

I'd also recommend to try and describe the problem in less words.

[MartinHjelmare]

Just press the "reopen issue" button at the bottom of the issue.

[candybars2001]

I spent an hour looking for this button before I referenced in a new issue. Could you kindly re-open the original issue or this one for me because I don’t see this option? I think this issue can be resolved if the guy who is looking into this, and spent a lot of time on this. I would appreciate if you could kindly help me re-opening the original issue or this one.

Just press the "reopen isssue" button at the bottom of the issue.

[candybars2001]

Just press the "reopen issue" button at the bottom of the issue.

I just tried to edit my last response and make it shorter and it closed the issue again. Any comment I post or edit that I make ends up closing the issue. Can you tell me what I'm doing wrong and reopen please? Without deleting my the suggestion that I came up with it won't reopen the subject. Thanks