A different implementation has been posted, that is not supposed to have the issues discussed below. Some members have tested it successfully, so I recommend using it instead: [RELEASE] Fibaro Wall Plug ZW5 (Z-Wave+) DTH
Old stuff for reference:
WARNING: There are issues with this new version of the plug (hw or firmware probably) when no load is connected. Read further down in the thread. It might be intended or not, but it limits some use cases.
A new version of the Fibaro Wall Plug has just been released to the market (December 2016) . This handler is for the new version. It supports Z-Wave Plus.
I am really new to the whole Z-Wave / Smartthings eco-system so please give feedback on any improvements. Iâm especially not sure about the fingerprint stuff I did in the handler. Acccording to my understanding of the docs it should be good though.
Working (and tested):
On/Off (of course)
Watt reporting
Kwh reporting
Several parameters implemented (not all of them tested)
Some notes:
Not all parameters has been tested, just updated against the documentation of the new switch. Please let me know if you find something thatâs not working.
This handler is less forgiving than the previous one. If a message arrives that is not recognized by the handler it will result in an error message in the logs. This is by design to weed out anything that is missing in the handler. Please give reports back if you have some.
Please let me know if you use it. Even if it works without any hiccups, so I can upgrade itâs status.
So far all is well, many thanks for this. I have upgraded 4 wall plugs without issues and so far on/off, watt and kwh is working without issues. I have used only your defailt settings and not changed anything.
@anderssv as discussed in another thread I am trying to get these wall plugs to work - without success. I currently have three identical plugs (zw5 - dated october 2016 and v. 3.02 on the box) and none of them responds as expected.
If I click the âreset kw/hâ they will respond to the next on or off action but nothing more.
I have tried removing them and re-adding and tried different DH without success.
The following error i logged:
90cd4afb-02f7-4ef8-946b-f5538df826f3 4:35:19 PM: error groovy.lang.MissingMethodException: No signature of method: script14837256145391703987148.zwaveEvent() is applicable for argument types: (physicalgraph.zwave.commands.meterv1.MeterReport) values: [MeterReport(meterType: 33, meterValue: [0, 0], precision: 1, scale: 2, scaledMeterValue: 0.0, size: 2)]
Possible solutions: zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicReport), zwaveEvent(physicalgraph.zwave.commands.crc16encapv1.Crc16Encap), zwaveEvent(physicalgraph.zwave.commands.meterv3.MeterReport), zwaveEvent(physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation), zwaveEvent(physicalgraph.zwave.commands.sensormultilevelv2.SensorMultilevelReport), zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinaryReport) @ line 146
Still at a loss on how this can happen. Been asking around and there doesnât seem like there is a good reason why you should be getting other versions of the command classes.
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.
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.
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).
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. ď¸ 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?
"If I click the âreset kw/hâ they will respond to the next on or off action but nothing more. "
â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.â
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