[bug report] MethodSelectionException (setLevel) with "GE Enbrighten Z-Wave Smart Dimmer" built-in driver via Hub Mesh

🧰 Built-In Apps and Drivers
1

All hubs on 2.3.9.184.

One C8 hub, freshly set up, has a dimmer device aptly configured to use the built-in "GE Enbrighten Z-Wave Smart Dimmer". Locally, e.g. using the UI, calling "setLevel" works fine. This device is exposed via Hub Mesh to another hub, where trying to invoke setLevel via the UI (or programmatically), e.g. with (90, 0) doesn't achieve anything except it produces the following log message --- on the hub where the device lives:

org.codehaus.groovy.runtime.metaclass.MethodSelectionException: Could not find which method setLevel() to invoke from this list:
public java.util.List embrightenDimmer#setLevel(java.lang.Object)
public java.util.List embrightenDimmer#setLevel(java.lang.String)
public java.util.List embrightenDimmer#setLevel(java.lang.Object, java.lang.Object)
public java.util.List embrightenDimmer#setLevel(java.lang.String, java.lang.String) (method setLevel)

I tried a few variations (linking the device on other hubs, swapping out the device driver), always same or similar results. When using the "Generic Z-Wave Plus Dimmer", I get the following:

org.codehaus.groovy.runtime.metaclass.MethodSelectionException: Could not find which method setLevel() to invoke from this list:
public void genericZWavePlusDimmer#setLevel(java.lang.Number)
public void genericZWavePlusDimmer#setLevel(java.lang.String)
public void genericZWavePlusDimmer#setLevel(java.lang.Number, java.lang.Number)
public void genericZWavePlusDimmer#setLevel(java.lang.String, java.lang.String) (method setLevel)

The difference between Object and Number seems a bit bizarre but doesn't get me further either.

What confuses me greatly is that I have a bunch of hubs, connected via Hub Mesh, also using the same "GE Enbrighten Z-Wave Smart Dimmer" driver, and everything is working fine. Why not this one?

Please help. Let me know what other information you might need.

2

The issue persists, it's real, and only involves stock Hubitat features. How can I get support from the Hubitat team?

1 Like
3

What platform version are you running on both affected hubs?

FWIW, I don't see anything weird in either set of driver code (supported by the fact that it also works for you in some cases?), so it might be a Hub Mesh oddity...

4

As I said, all hubs on 2.3.9.184.

I am also suspecting some Hub Mesh magic going wrong, but as an end-user, I have no insights into that. Something very basic is going wrong.

6

Tagging @gopher.ny in case he wants to dig into anything with Hub Mesh here since I can't see any reason it would be the driver.

There is a platform update (still for 2.3.9) in beta that will likely make it to public release at some point, though I can't think of any particular fixes that would help with this particular issue. But I suppose the other option is to wait for that just in case...

7

Can you PM me the hub id? I'll check the engineering logs.