SmartThings Community

[ABANDONED] Fibaro Wall Plug ZW5

fibaro
dth_pocketsocket

(Ulf Thomas) #7

Thanks for assisting - I am no stranger to such things not working. :blush:

You state that I have a different command class - how can you tell?


(Anders) #8

The error you posted states that it can’t find a method for:

physicalgraph.zwave.commands.meterv1.MeterReport

Because I know the code; I know that the only method with a MeterReport is:

def zwaveEvent(physicalgraph.zwave.commands.meterv3.MeterReport cmd) {

Each one of those methods are signals from the device, containing different information. :slight_smile:

Anders,


(Ulf Thomas) #9

Executed the change on line 181 and but the result is the same - switch does not react. No error though.

But - when hitting the “reset kwh” an almost identical error appears:

b69a798b-6285-4e3b-a608-06c4352c7aad 7:19:24 PM: error groovy.lang.MissingMethodException: No signature of method: script1483899564177156597316.zwaveEvent() is applicable for argument types: (physicalgraph.zwave.commands.meterv3.MeterReport) values: [MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 0], precision: 2, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.00, scaledPreviousMeterValue: 0.00, size: 4)]
Possible solutions: zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicReport), zwaveEvent(physicalgraph.zwave.commands.crc16encapv1.Crc16Encap), zwaveEvent(physicalgraph.zwave.commands.meterv1.MeterReport), zwaveEvent(physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation), zwaveEvent(physicalgraph.zwave.commands.sensormultilevelv2.SensorMultilevelReport), zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinaryReport) @ line 209

Please advise.


(Ulf Thomas) #10

I must also add that when hitting the “reset kwh” the plug blinks green twice - every time - suggesting that the plug is in communication with ST.


(Ulf Thomas) #11

Seems like there is something going after the plug has responded correctly to one “power on or off”.


#12

Two questions:

Exactly which device type handler do you now have assigned to the plug? ( if you can post a screenshot of your devices page that would be helpful, you can crop it down to just that device if you want)

Second, just to be sure, did you paste the DTH into the Device Handler tab, not the smartapp tab? Because that “missing method” or usually means a problem in the code installation, not the DTH itself.

This might help:

My thought on this is that you might not have installed the device type handler at all, and the plug is just trying to use whatever generic DTH it paired with initially. But the device list will tell you what handler it is actually using.


(Ulf Thomas) #13

Good questions. Ill test later and report.


(Ulf Thomas) #14

I believe so yes. It is listed under “My Device handlers”. :slight_smile:


(Ulf Thomas) #15

Just tested again after leaving a plug off for about an hour - and it respons to the first command (being it on or off) but not any consequtive actions. No error messages in the log during these tests.

Then I click “reset kwh” and the debug error I postet about an hour back pops up and the plug responds to one more action.

Wierd.


(Ulf Thomas) #16

Hi there.

I changed a few lines in the debug output section and were able to produce this during my failures:

Could not extract command from Crc16Encap(checksum: 234, command: 2, commandClass: 50, data: [33, 68, 0, 0, 0, 0, 0, 0, 5])

Does this tell you anything at all?


(Ulf Thomas) #17

I think I found the culprit:

Line 142 reads as follows:

def cmd = zwave.parse(description, [0x20: 1, 0x32: 1, 0x72: 2])

This line does some z-wave version-checking (you probably know more about this than I do) and the parameter 0x32 contains the version number for “Meter” and based on this it seems to be telling the code to use V1.

I changed it to 3 and so far I have not gotten any debug errors. (I must add that I am at work and unable to visualy verify that the plug changes state - but the lack of errors is good).

I’ll report status when I return home.

Thomas


(Anders) #18

Awesome Thomas, that seems plausible. It doesn’t explain why it gives different versions for you and me, but it is probably related to that.

I must admit I copied that crc unwrap code without completely understanding what it did. :slight_smile:️ Looking into it now I actually think the second parameter (the map) can be completely removed. I’ll try it later when I get home.

The only reason I can think of why it behaves differently at your location is because we have different versions of the software on our hub. Mine is v2 FW 000.016.00011. What is yours?


(Ulf Thomas) #19

I am on that version myself.

Could there be a difference in the plugs themselves?


#20

Hi @ulfthomas74, @cscheiene and @anderssv ,

i have the complete equal failure like Ulfthomas.

  1. "If I click the “reset kw/h” they will respond to the next on or off action but nothing more. "
  2. “I must also add that when hitting the “reset kwh” the plug blinks green twice - every time - suggesting that the plug is in communication with ST.”

@ulfthomas74: Do you have a solution?

I changed it and tested it:
def cmd = zwave.parse(description, [0x20: 1, 0x32: 3, 0x72: 2])

It´s not possible to change On/Off. In “Recently” i get no updated when I push “on” or “off”.
If i click “reset kwh” and than “on” so it works. In Recently it is shown the correct action

Hub:
Firmware Version 000.016.00009
Hardware Version hub v2, UK customer

Plug:
Raw Description:
zw:Ls type:1001 mfr:010F prod:0602 model:1001 ver:3.02 zwv:4.05 lib:03 cc:5E,22,59,56,7A,32,71,73,98,31 sec:85,70,72,5A,8E,25,86 role:05 ff:8700 ui:8700


(Ulf Thomas) #21

Your problems seems identical to mine aside from the hub version - both @anderssv and myself are on version 000.16.00011.

My suggestion would be to remove (exclude) all plugs and remove the DH. Then re-add the DH with the change on line 142 then re-add the plugs.


#22

I have done every step
But i have also the same problems.


(Ulf Thomas) #23

Clear your log and copy a few lines from when you are switching the plug on or off (and any other commands)


#24

OFF:
2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:14:50: debug zwaveEvent: v3.MeterReport
2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:14:50: debug Command: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0], precision: 1, previousMeterValue: [0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.0, scaledPreviousMeterValue: 0.0, size: 2)
2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:14:50: debug Parse: zw device: 33, command: 3202, payload: 21 32 00 00 00 00

ON:

2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:15:26: debug zwaveEvent: v3.MeterReport
2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:15:26: debug Command: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0], precision: 1, previousMeterValue: [0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.0, scaledPreviousMeterValue: 0.0, size: 2)
2f034564-464c-4dc4-8bb8-816e7d7e9e11 14:15:26: debug Parse: zw device: 33, command: 3202, payload: 21 32 00 00 00 00


(Ulf Thomas) #25

Those are the same messages I get in my log but since I am still at work I have not been able to visually confirm that the state of the plug changes based on the command I send.

I will test and report back later today.


(Ulf Thomas) #26

@anderssv

I just did some additional testing and all though the error messages are gone it does not resolve the problem.

Whenever I click on or off the following is logged and the plug does not respond:

‎14‎:‎48‎:‎48: debug zwaveEvent: v3.MeterReport
14‎:‎48‎:‎48: debug Command: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0], precision: 1, previousMeterValue: [0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.0, scaledPreviousMeterValue: 0.0, size: 2)
14‎:‎48‎:‎48: debug Parse: zw device: 13, command: 3202, payload: 21 32 00 00 00 00

but if I first click “reset kwh” the following lines comes in addition to the ones above and the plug responds:

‎14‎:‎46‎:‎18: debug zwaveEvent: switchbinaryv1.SwitchBinaryReport
‎14‎:‎46‎:‎18: debug zwaveEvent: securityv1.SecurityMessageEncapsulation
‎14‎:‎46‎:‎18: debug Command: SecurityMessageEncapsulation(commandByte: [0], commandClassIdentifier: 37, commandIdentifier: 3, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)

Any insight?