I get this error when trying to install the Preference Manager app. How can I get the app loaded properly?
@bobbyD Still getting this error with trying to load Preference Manager. Same error message and log message. The log message actually point to the line of code with the error.
This line number is within a portion of hub code, in order so see exactly where I'll need to review the engineering logs on this hub. Please DM me your hub id, thanks!
1 Like
The line number in the logs is referring to a line number in the actual driver.
Engineering logs note that the method isLongRange() in the driver is being called with a reference to line 1136.
This method wouldn't be called from preference manager since its a method, not a preference, anyway I think this is a red hearing.
Preference manager is actually blowing up due to the dynamic nature of these preferences as its unable to actually read the metadata of the preference, though the database itself says a preference exists.
I'll spend a little time seeing if I can reproduce the issue locally without having this specific device on hand to test with.
Can you send me a screen capture of the State Variables section for this device?
I vaguely remember issues with jtp10181's drivers having dynamic preferences. If Preference Manager excludes other drivers that have dynamic preferences, this driver should also be excluded.
Some of our internal drivers use dynamic preferences, just not with embedded html
ok then.
If it can't be easily resolved, then just eliminate the devices using those drivers from consideration in the Preference Manager app.
Just have a list of devices that aren't included.
If I'm able to resolve this the effect would be that non conforming preferences would not be available (ie not shown) in preference manager. There isn't a feasible way I can think of off hand to display these devices within preference manager.
Went back to this issue today. Did a ZWave exclusion on a Zooz ZEN37 wall remote as it uses dynamic prefernces with HTML. App loads fine now.
It has worked on other drivers of mine with the html in the pref names last time I checked it a long tme ago.
But also, it did not work very good on my switch/dimmer driver for example where you might have multiple different models all with different preferences available. It would only load one set of preferences and then assume they were the same on all devices using that driver. Not sure if they ever fixed that issue.
