LB60Z pairs, but no control

[mr23]

Trying out a linearlinc LB60Z, sensor page says supported, as dimmer.
Started with R070, paired, then upgraded to R072.
Neither the LCD nor the luci sensor page nor Almond+ app can control it. None of On/Off/Dimmer settings will affect it.

When pairing, LCD asked if should be a Multilevel, RollerShutter or other. Chose MultiLevel.


DeviceList.xml entry is as follows; no last known value, and dimmer/level setting only, no on/off.

Code: [Select]

        <Device ID="11">
                <Name>test lb60z</Name>
                <Location>test fixture 1</Location>
                <OZWNode>3</OZWNode>
                <ZigBeeShortID>NaN</ZigBeeShortID>
                <ZigBeeEUI64>NaN</ZigBeeEUI64>
                <DeviceTechnology>ZWaveTechnology</DeviceTechnology>
                <AssociationTimeStamp>1428726038</AssociationTimeStamp>
                <DeviceType>MultilevelSwitch</DeviceType>
                <FriendlyDeviceType>MultilevelSwitch</FriendlyDeviceType>
                <AllowNotification>1</AllowNotification>
                <ValueVariables Count="1">
                        <LastKnownValue Index="1" CommandClassID="38" CommandIndex="0" Name="SWITCH MULTILEVEL" Type="Byte"/>
                </ValueVariables>
        </Device>

zwave_server.log says repeatedly

Code: [Select]

[2015-4-10 23:32:21.146908140]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:32:23.151257393]   {PRINT}         Driver:Removing Msg from Node 3 attempts:3
[2015-4-10 23:32:23.171682419]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:32:25.339782680]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:32:27.354388112]   {PRINT}         Driver:Removing Msg from Node 3 attempts:3
[2015-4-10 23:32:27.374802859]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:34:49.236856593]   {PRINT}         Received Operation Code:Code_SetValueOperation
[2015-4-10 23:34:49.237039626]   {PRINT}         home id :0xc48813d6 cmd cls:0x26,genre:1,index:0,instance:1,type:1
[2015-4-10 23:34:49.237162446]   {PRINT}         Setting value:Node:3,cmdcls:SWITCH MULTILEVEL(0x26),valueType:byte,Inde
x:0,Value:76
[2015-4-10 23:34:51.307348786]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:34:53.311661746]   {PRINT}         Driver:Removing Msg from Node 3 attempts:3
[2015-4-10 23:34:53.332086446]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:34:53.650304546]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:34:55.480640539]   {PRINT}         Driver:Removing Msg from Node 3 attempts:2
[2015-4-10 23:34:55.501056886]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:34:55.511289726]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:37:15.714696513]   {PRINT}         Received Operation Code:Code_SetValueOperation
[2015-4-10 23:37:15.714903640]   {PRINT}         home id :0xc48813d6 cmd cls:0x26,genre:1,index:0,instance:1,type:1
[2015-4-10 23:37:15.715029053]   {PRINT}         Setting value:Node:3,cmdcls:SWITCH MULTILEVEL(0x26),valueType:byte,Inde
x:0,Value:23
[2015-4-10 23:37:17.785480253]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:37:19.789973140]   {PRINT}         Driver:Removing Msg from Node 3 attempts:3
[2015-4-10 23:37:19.810398740]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:37:21.968136159]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:37:24.008117239]   {PRINT}         Driver:Removing Msg from Node 3 attempts:3
[2015-4-10 23:37:24.028549586]   {PRINT}         Not Sending Node 3 Type_Notification(26) notification to haserver
[2015-4-10 23:41:33.993180560]   {PRINT}         Received Operation Code:Code_SetValueOperation
[2015-4-10 23:41:33.993388860]   {PRINT}         home id :0xc48813d6 cmd cls:0x26,genre:1,index:0,instance:1,type:1
[2015-4-10 23:41:33.993514340]   {PRINT}         Setting value:Node:3,cmdcls:SWITCH MULTILEVEL(0x26),valueType:byte,Inde
x:0,Value:65


[LGNilsson]

Wow, that's interesting. When I pair it, it shows up as a dimmer.
It looks like they have two different firmwares where it shows up as different things. 

[mr23]

Wow, that's interesting. When I pair it, it shows up as a dimmer.
It looks like they have two different firmwares where it shows up as different things. 

What was the last FW rev of Almond+ that you tried to pair it?
What version did you pair it under to test?
When I get time, I might go back to an older rev and see what happens here.

[mr23]

Wow, that's interesting. When I pair it, it shows up as a dimmer.
It looks like they have two different firmwares where it shows up as different things. 

2nd question in the next message, but here's another.

> When pairing, LCD asked if should be a Multilevel, RollerShutter or other. Chose MultiLevel.
Should  I have chosen "Other"? to get Dimmer ?

[LGNilsson]

Multilevel switch is the correct option.
My bulb is working just fine, on/off and dimming.

No idea what might've changed 
It's possible you got a dud, as everything looks the same in the device list.

I've tried the bulb with R070 and R072, no problems.

[Deleted]

I have had a hit/miss experience with Linear z-wave devices.  I have one dimmer working great and have had to send two others back.  One of them paired just fine but would not respond.  The other would not pair or respond....

[mr23]

Thanks, I guess I'll return it and can't recommend them.