[Solved] Hub Variables reporting error

Hi all,

After the last update to version 2.4.0.151 on C7 hub, I'm getting below error when I'm trying to view the hub variables. I tried to revert back to version 2.4.0.148 but issue still persist.
Do anybody experienced the same issue/bug/behavior last days please?
Thanks

This is a database issue. Try to restore a recent backup to see if that will fix it first. If it doesn’t I have something else we could try, but it’s not the preferred method.

4 Likes

I restored my hub with the recent backup but issue still persist.
May I ask you for another hint please?
Thanks in Advance

Two additional thing. I can see the global variables in webCoRE and pistons are properly getting the values that are set up to global (hub) variables.

Below is the error message from the logs:
groovy.lang.MissingMethodException: No signature of method: java.lang.Double.length() is applicable for argument types: () values:
Possible solutions: next(), getAt(java.lang.String), with(groovy.lang.Closure), each(groovy.lang.Closure), wait(), every() on line 255 (method hubVar)

Okay, this will work if you’re not using variable connectors (if you are stop and we’ll ask before going forward). Go to Settings | Hub Variables like before, but change “configure” to “status” in the URL and hit enter - this will give you a “Remove” button. Push it, and then go back to Settings | Hub Variables - this forces a reinstall of the Hub Variable app.

3 Likes

I followed suggested steps but I did not get any REMOVE button.

By the variable connectors, do you mean the "Dashboard variable device" ?

Get rid of the /hubVar

Variable connectors were the old way of allowing variables to be displayed/used on the dashboard and other apps. (They now have direct access methods so many/most people have never used them.)

2 Likes

Without using /hubvar I got the below page.
Do you want me to use the "Remove Hub Variables" please?

That's the one. Sounds scary, but comes right back.

2 Likes

THANK YOU VERY MUCH!
Everything is back and working fine now.

3 Likes