Fibaro Universal Sensor only one input works?

General Discussion
1

Hi guys

I’ve connected a PIR sensor to fibaro universal sensor but I can only get one of the inputs working.

In the logs I always get this for input 1 which is ok

'zw device: 06, command: 2001, payload: FF ' parsed to [descriptionText:Z-Wave Device Multichannel: BasicSet(value: 255), 
'zw device: 06, command: 2001, payload: 00 ' parsed to [descriptionText:Z-Wave Device Multichannel: BasicSet(value: 0), isStateChange:true, displayed:true, linkText:Z-Wave Device Multichannel]

I’ve connected input 1 to the PIR sensor and any movement returns the above or if I move input 1 to tamper on the PIR sensor same, the tamper switch works fine. So result input 1 works fine.

I don’t seem to be getting any commands being sent from input 2, do I need to do some extra work to get input 2 working? I’ve excluded it from ST/reset it as it says on the docs and then included again with both inputs connected but still no luck.

Excuse the wires used;

Thanks

edit: its cool, I got it working :smile:

2

To get it input 2 working I had to assoicate with group 2.

Now just trying to figure out how to tell which input is sending the data, both have the same signature as the post above.

Theres a group 3 that gives that shows separate inputs but does not get parsed.

'zw device: 09, command: 600D, payload: 01 01 20 01 00 ' to []
warn Exception 'java.lang.NullPointerException: Cannot invoke method parse() on null object' encountered parsing 'cmd: 600D, payload: 01 01 20 01 00'
'zw device: 09, command: 600D, payload: 01 01 20 01 FF ' to []
warn Exception 'java.lang.NullPointerException: Cannot invoke method parse() on null object' encountered parsing 'cmd: 600D, payload: 01 01 20 01 FF'
'zw device: 09, command: 600D, payload: 02 02 20 01 FF ' to []
warn Exception 'java.lang.NullPointerException: Cannot invoke method parse() on null object' encountered parsing 'cmd: 600D, payload: 02 02 20 01 FF'
'zw device: 09, command: 600D, payload: 02 02 20 01 00 ' to []
warn Exception 'java.lang.NullPointerException: Cannot invoke method parse() on null object' encountered parsing 'cmd: 600D, payload: 02 02 20 01 00'

Commands Supported

// Multi Channel (version 2)
// Basic (version 1)
// Binary Switch (version 1)
// Version (version 1)
// Multi Channel Association (version 2)
// Binary Sensor (version 1)
// Multilevel Sensor (version 1)
// Manufacturer Specific (version 1)
// Association (version 2)
3

ok so parsed the description without saying which classes and it came out as Multi Channel 3. Now I can tell if its input 1 or 2 :smile:

4

@Sniper, where did you purchase this from?, and did you get the US zwave frequency?

5

This has been on my wish list for some time. It is so insanely small which opens a lot of possibilities to give smarts to dumb devices.

Seems Fibaro has pushed out a US release.

6

well poop…, I was going to use this with the Kiddie smoke and co modules…
I had two on back order for 6 months when they first came out.

7

Hi guys, I got it from amazon uk, well thats because I am from the UK :smile:

Surprised they don’t have it out in the US yet.

8

Hi @Sniper

would you mind sharing your code on how you got this to work?

Thanks

Paul

9

Hi

I’ve not worked on it for a while now, I got the basics working. Was able to identify each input by using association group 2 if I recall correctly. Think it would need a smart app creating to make use of both inputs.

My alarm is under warranty for another 10 or so months, so probably won’t work on it until after then.

test code not really useable but might be helpful

10

Hi @Sniper

Thanks for the code, works great for the first input, but getting the 2nd input to work/show is a little beyond me. I changed capability “Sensor” to capability “Contact Sensor” so I could use it with the smartlighting app.

Thanks
Paul

11

Hi @pukka

Sorry for the late reply, you will have to change the code a little bit.

If i remember correctly by default it associates with group 1 which only returns the state of input one, you need to associate with group 2 by running zwave.associationV2.associationSet(groupingIdentifier:2, nodeId:[zwaveHubNodeId]).format() its part of the device code above just commented out.

I think once you do that it sends slightly different data for each input. You’d need to create a smart app to make use of both inputs from what I’ve read in various threads.

12

Hey i’ve just received universal sensor and was planning giving it a go this weekend, @Sniper am i right in thinking the revision on your github has both inputs working?
Dave

13

hi @daveo2k

Have a look at this thread: