I have identified an issue when using local variables that have names longer than 19 characters in Rule 5.0. I created the following local variables:
The name of the last two variables are 20 characters whereas the first two have names of 19 characters or below. Other than their name, they are identical as you can see in the screenshot.
The issue I'm running in to is that I cannot use "Set Variable" with the 20 character variables.
It doesn't matter what I select in the "Select operation" drop down menu. Nothing happens when I click it and it doesn't even "close" the drop down menu when I click on something in it.
What browser are you using? I am not seeing this problem with Chrome -- it works fine.
Could spaces be the issue?
Not in the OPs example but, are there any limitations of names? i.e.
- Must they start with a letter?
- Are !@# $%^&*()_+":?>< acceptable?
- is / or \ acceptable?
Spaces are not a problem. As it says in the app, these characters may not be used in variable names:
DO NOT use these characters: ' " ~ [ ] < > in Hub Variable Names
Iām using Edge Chromium. Iāll try Chrome as well when I get home from work.
@bravenel - Iāve done some further testing. I didnāt have a computer available to me tonight but I tested it on my phone instead with both Chrome and Safari and both exhibit the same issue as Edge on my computer. The 19 character variable works fine, but the 20 character one does not.
I installed Rule 5.0 from scratch on another of my hubs (all my hubs are on 2.2.8.152) and set up a new rule with the same variable names. Same issue there, the shorter variables work fine, the longer ones donāt. 
Edit: Just did some more testing with different variable names. I tried a variable name consisting only of numbers and that works for both 19 and 20 character lengths. I then extended my āhumidityā variable to 21 characters, just to find that just like the 20 character āhumidityā variable, this one didnāt work either.
I can confirm this issue as well in a test case using Chrome. 20 characters or less work just fine. Anything over 20 does not allow the completion of the action. @mattias I think I got it to work as a workaround by doing the following:
Select the long variable name. Choose the Operation such as Number. Click outside of the dropdown and then click the Refresh button. Once I did that, it allowed me to set a number. I didn't test to see if the rule actually worked using that method, so you may try it.
I also created a few different variables to see if it mattered for number or decimal, etc. It didn't.
This is very odd. A very long variable name works just fine, and 'Humidity 24 hours ago' causes the UI to choke. We will look into it.
@bravenel, it is almost like it is thinking before giving you the option to set its value LOL. But if you click outside of the dropdown and click Refresh, it then allows an entry (if that helps you track it down).
Release 2.2.8.153 is out and it fixes this problem.
3 Likes
