Fibaro universal binary sensor - very confused

Until you’ve had a chance to get to this, I reckon I should be able to workaround the problem by using tail/awk to monitor the logfiles and trip an openhab switch when the device sends the BASIC_SET command. Will post that on this thread when I’ve got it working, on the offchance anyone else has the same problem.

Ok, thanks. Are you using the development version, or the snapshot?

development - 25 October version

Ok, thanks. Can you try deleting the XML for this device, reinitialise, and send me the log of the init? I think that by setting the multi-channel lifeline association it should enable multi-channel messages - I’d like to see if that is being set or not…

sure - log is here

Sadly looking at the logs I don’t think I can do anything clever with an awk script, because the logs look exactly the same when I trigger input 1 as when I trigger input 2.

If you have the opportunity, give this version a try. Delete the XML for the node so it reinitialises…

Thank you!

Doesn’t seem to make a difference. I attach the log with the reinitiatisation and a couple of test transactions, and also the XML

Thanks - I’ll take a look at this later.

The log doesn’t show any initialisation. The device is showing as failed by the controller, so it hasn’t yet initialised it (hence there’s no change in function). Probably waking up the device will sort this and allow it to initialise (I plan to change this logic in the near future).

oh, I assumed that if a new XML was created there must have been initialisation. I’l have another go!

Yes - that is a valid assumption, but the log doesn’t have the info. Maybe it completed after the log was sent ?!?

You are of course right - it came a bit later… I think it’s in here

There is some in here, but not the full log.

Anyway - hold off for a bit as I’m hopefully homing in on some more changes to these settings that I think will impact this…

Thanks - will do. I’ve been trying to avoid dumping vast logs on you, but looks like I’m no good at that…

Vast logs (well, reasonably vast) are fine - up to 10 to 15MB I can handle in the log viewer and really once they are in there it’s pretty manageable…

staying in the queue for FBS001 fix :slight_smile: Happy to help with testing/logs as needed

So here’s my temporary solution:

add the following into crontab:

@reboot tail -F /var/log/openhab2/zwave.log | awk '/NODE 56: Incoming command class COMMAND_CLASS_BASIC/ { system("wget http://localhost:8080/classicui/CMD?MySwitch=ON -P /tmp") }'

then (making sure the expire binding is installed) the following item:

Switch MySwitch  "New switch" { expire="2s,command=OFF" }

A rule can then simply detect the switch changing from OFF to ON

Obvious disadvantage is you can’t use two inputs - my dumb solution for the moment was to buy another fibaro device.

I got it to work (sort-of) fiddling with the Associations in HABmin.
1: Input 1 -> openhabController
2: Input 2-> openhabController

Had to set them multiple times, one at a time and restarted binding/openhab several times.
Strange thing is that after a restart, coming back to openHAB; both entries are empty, but inputs still work:

2018-02-04 23:15:51.109 [INFO ] [.model.script.UniversalBinarySensor2] - Update: UniversalBinarySensor2=ON
2018-02-04 23:15:51.383 [INFO ] [.model.script.UniversalBinarySensor2] - Update: UniversalBinarySensor2=OFF
2018-02-04 23:15:54.735 [INFO ] [.model.script.UniversalBinarySensor1] - Update: UniversalBinarySensor1=ON
2018-02-04 23:15:54.795 [INFO ] [.model.script.UniversalBinarySensor1] - Update: UniversalBinarySensor1=OFF

3: Controller updates; which is the one I really want for reporting scenes, is not possible to set, ever. HABmin only mark it as Pending… after I hit save trying to associate it to openhabController.

Oh, almost forgot: I’m on snapshot #1198 and Z-Wave development binding:

@chris, any chance you could have a look at getting the scene channel working.
Could be quite useful:

thanks… perfect. i am using your shared workaround with the Associations in Habmin. Without that, my Fibaro sender does not provide the alarms.
it would be great if that can get fixed. … i am happy to help with testing/logs when needed.

how weird - I set the associations in the same way, but never get anything from my items.

They’re defined as:

Switch Lift_Test1 { channel="zwave:device:zstick:node56:sensor_binary1" }
Switch Lift_Test2 { channel="zwave:device:zstick:node56:sensor_binary2" }

and when openHAB starts I see entries in the event log:

2018-03-12 22:23:38.145 [vent.ItemStateChangedEvent] - Lift_Test1 changed from NULL to OFF
2018-03-12 22:23:38.186 [vent.ItemStateChangedEvent] - Lift_Test2 changed from NULL to OFF

but no event ever fires when the inputs are triggered. I know they’re working, because I can capture the results with an awk script monitoring the zwave.log file (extremely hacky, even by my low standards)

Using the latest experimental binding but a slightly old snapshot - #1149