New UI (2.4.0.144) - Unable to save Preferences for Inovelli devices

@gopher.ny

After updating to 2.4.0.144 I am unable to save preferences on any of my Inovelli devices (and a few other devices using user drivers). The "Preferences saved" popup never shows up and changes are not saved.

The Inovelli devices are using the latest Inovelli user drivers (from HPM). I'm also seeing the same issue with a few other user drivers. Build in drivers and some other user drivers are working correctly.

I've tried the usual debugging steps; Reboot hub; clear browser cache; tested on multiple devices/browsers; reinstalled user drivers.

Forgive me if this is posted elsewhere, but I wasn't able to find any similar issues.

2 Likes

Can you post the links to the community drivers that have this problem?
I can check them, the reason could be the same or similar to this one.

1 Like

Any of the Inovelli drivers seem to be affected. Here is a direct link to the LZW30 driver for example.

1 Like

I'm seeing this problem with my Red dimmers (LZW31-SN driver). No errors in the logs, it just doesn't save.

As a temporary workaround, you can modify lane #165 :

from :

input description: "Use the below options to enable child devices for the specified settings. This will allow you to adjust these settings using Apps such as Rule Machine.", title: "Child Devices", displayDuringSetup: false, type: "paragraph", element: "paragraph"

to:

input "dummyName", "hidden", description: "Use the below options to enable child devices for the specified settings. This will allow you to adjust these settings using Apps such as Rule Machine.", title: "Child Devices", displayDuringSetup: false, type: "paragraph", element: "paragraph"


Same fix, only the line is different: #195

The input method should have a name ("dummyName") and a type ( "hidden"),

Hopefully, there may be a fix for this in the HE system platform update very soon after the New Year holidays, so there will be no need to modify these drivers individually.

2 Likes

Noted.

4 Likes

Thanks @kkossev , this fixed that specific driver and I was able to use that example to fix a couple other custom drivers as well.

Seems to be anywhere a "dummy" parameter is used as a description only text box?

Yes.

Although I didn't see mention of in the release notes, this issue appears to be resolved in 2.4.0.145

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.