Fibaro Smart Implant offers lots of possibilities, but is not easiest one to understand and configure… I have in my setup 6 implants now and spend quite some time playing with them to understand how these works. From Fibaro documentation not everything is clear, so let me share some of my learnings:
- Module has 2 inputs and 2 outpust, that can be configured (but not fully independently)
- IN1/2 are linked to OUT1/2 (though these can be switched by changing appropriate parameters). Clue is that if INs are configured as binary inputs or alarms, change of their status always triggers correcponding OUT. It is not possible to have fully independent binary inputs and outputs.
- In binary input mode module is triggering zwave scenes, that are not handled by hassio yet. There is no entity on implant that would show their status directly… unles you read the status of corresponding OUT. But the trick is that OUT can be changed programatically (it is switch, from hassio perspective), so not always change in OUT status is reflecting change in IN status (e.g. some automation or script might trigger such change).
- Best way of reading inputs is to configure these as burglar alarms. These are visible to hassio as entities and their status can be read or trigger some actions. Buit again, to make things more complex; inactive alarm has 0 value, active alarm has value of 2… but both can change to 254 as module is going to sleep. So this needs to be considered in automations!
- The only way to separate INs from OUTs is to configure INs as input voltage sensors. It is possible to measure input voltage (with or without internal pullup) idependently from setting states of OUTs. Again this is directly measurable in hassio as value of corresponding sensor. So in theory you can configure analog input as input switch by changing its voltage and have it fully separated from OUTs.
- It is not possible to have one IN configured as binary input or or alarm and second as analog input! If one of iputs is configured as analog it iinstantly triggers that second one is also changing to analog.
- As described above type of INs and OUTs can be configured separately, which means that lots of parameters is only applicable when module is properly configured and some can/should be disregarded if configuration is not applicable.
So coming to your question:
- alarm_level, alarm_type, sourcenodeid - I’d disregard, unless you are linking smart implant directly to other zwave devices using scenes (native zwave config)
- burglar can be used to figure out status of inputs
- temperature might be of some use, though since module is constantly powered on it is showing its own temperature, not surrounding…
- input_voltage - voltage on IN1/2 if configured as such (BTW, I’m a bit surprised to see it showing ~20V in your listing. Normally module is capble of measuringh up to 10V (oficially) and it shows ~10.5V if not connected. It can be also used to determine temperature of external sensors (do not know details, not using this functionality)
- switch - status of OUT1/2 can be changed from hassio or reflect changes in IN1/2
And your issues with burglar alarms; not really sure about it, in all of my configs I had to have fully separated INs and OUTs, so can use only one sensor and one output per module. I believe when I tested it it worked independently, so could be faulty module. What I’d do is to remove the module from configuration, do the factory reset and add it again. I’d also recommend using OZWCP add-on rather than build in Z-Wave Control Panel… for some reason it is more reliable for me (even if using the same undrlying libraries). I recall having some issues with fibaro modules configuration that were resolved this way.