Hi
I have a Shelly Wave Dimmer (800 series, the green one).
It does include in Hubitat and by default uses the Generic Z-Wave DT Multilevel Switch but I'm not really getting it to work. Its not setting on/off state or level.
When including the device in a dashboard as a dimmer it comes up a bit weird too (see screenshot).
Anyone got this one to work and what driver are you using?
That driver should work. Are there any indications that the device isn't working, like range problems or a failed inclusion? You could try an exclude and re-include if nothing else. Seeing if you see anything come into Logs with debug logging enabled and physically manipulating the device (to try to make something come in) might be another good thing to test.
Can you post a screenshot of the "Current States" section of the driver page?
Ok.. That's not normal..
Can you turn on debug logging and then do On/Off and Refresh commands then paste the log here..
Thanks a lot for taking a look at this. Very highly appreciated 
Here is the debug logs;
dev:532026-05-02 00:42:43.332debugskip:hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap@19b6086
dev:532026-05-02 00:42:43.297debugparse:{"cc":38,"cmd":3,"ep":1,"values":[{"ccVersion":4,"newValue":0,"endpoint":1,"metadata":{"readable":true,"min":0,"max":99,"label":"Current value","secret":false,"writeable":false,"type":"number","stateful":true},"propertyName":"currentValue","commandClass":38,"property":"currentValue","commandClassName":"Multilevel Switch","value":0,"prevValue":15,"ts":1777675363272},{"ccVersion":4,"newValue":{"unit":"seconds","value":0},"endpoint":1,"metadata":{"readable":true,"label":"Remaining duration","secret":false,"writeable":false,"type":"duration","stateful":true},"propertyName":"duration","commandClass":38,"property":"duration","commandClassName":"Multilevel Switch","value":{"unit":"seconds","value":0},"prevValue":{"unit":"seconds","value":0},"ts":1777675363275},{"ccVersion":4,"newValue":0,"endpoint":1,"metadata":{"readable":true,"min":0,"max":99,"valueChangeOptions":["transitionDuration"],"label":"Target value","secret":false,"writeable":true,"type":"number","stateful":true},"propertyName":"targetValue","commandClass":38,"property":"targetValue","commandClassName":"Multilevel Switch","value":0,"prevValue":15,"ts":1777675363277}]}
dev:532026-05-02 00:42:42.741debugoff()
dev:532026-05-02 00:42:40.010debugon()
Did you do a refresh in there? Is that was triggered the long parse string (JSON Data)?
Looks like it is sending the dimmer info encapsulated as multichannel for endpoint 1, so it would probably need a multichannel driver to split it out into child devices. Or a special driver that maps EP 1 to the main device.
I am not sure I understand what your mean by a refresh? Do you mean if I pushed the refresh button in the log page on the device or "refresh" button under "actions" in the device list page?
I doubt its range problems. The device are like 2 meters from the Hub and my network are pretty solid in general I have to say.
Including it was a bit "pita" to be honest. The instructions for including it which come with the device is not super clear. So there might be a somewhat failed inclusion here.
The refresh command on the device page. Which would send command to the device to ask for its current state.
Ah. Yes I have tried that. No change in its state at all in doing so.
"ep":1
The problem is here..
The device is sending as endpoint 1 and the driver is not multichannel aware..
@post Please go to Z-Wave details and click on "State" .. Then copy the JSON at the bottom and PM it to me please..
Awesome.
PM sent and thanks a lot for looking into this. Highly appreciated
Download the Hubitat app
