Hub Variables Issue

Hi!

I am trying to create a hub variable to set a wake-up alarm.

When I enter the name of the variable (tried many names like "Alarm Time" and even "testing" without the quotes of course) and after setting the initial value, I save it and then nothing appears.

This seems an easy procedure but I am completely lost.

I was running 2.3.2.126 but Button Controller was not responding to a button's event (strange I know) but RM was running fine I then reverted back to 2.3.1.142.

Can anyone help?

Have you set up other hub variables successfully or is this your first attempt? Which page are you looking at when you notice nothing has appeared? The hub variables page or somewhere else you are trying to access it from?

If you're new to hub variables it might be worth just testing with a different data type of variable such as boolean... cos you say you've reverted to an earlier build and there were some builds that had glitches with the date-time variables

1 Like

Hi!

I am looking at the Hub Variables menu option in the settings page. I've tried number also. When I type for example 10 as the initial value and then hit TAB the field for initial value disappears and no save button appears.

This is very strange.

Kind regards,
Miguel

I don't usually use Tab to move around in Hubitat screens. I have just tried it and it works up to a point but I notice with the date time variable it only enables cancel and if you then hit tab or do so too fast to notice you're tabbing onto cancel, it cancels the whole thing and results in what you're seeing. Try instead to click outside the entry boxes when you fill each one in and avoid tabbing unless you're careful what you're tabbing onto.

As to your other problem, having to revert isn't great - would be good to explore what's going wrong with your button controller

Just tried clicking with datetime and with number... Same outcome.

This is very odd. If you also tried this in the latest build and had the same result (or was it ok in 2.126?), then I guess you have to be doing something unexpected - cos it's working for others. But I can't think what

I'm upgrading from 2.3.1.142 to 2.3.2.126 and check if the problem persists.

If Button Controller does not work properly I'll have to request assistance from Hubitat staff.

It works on 2.3.2.126.

I'll check the Button Controller App when I get home and push the button :slight_smile:

Thanks!

Well at least one of your two problems is sorted :smiley: I suspect the button one will be more straightforward

@bobbyD

Can you give @miguelgoncalves permission to post screenshots of their app setup? It will make troubleshooting much easier.

2 Likes

Done!

2 Likes

Can you post screenshots of what you are describing?

I think that particular problem (variable) was solved by updating to latest - some earlier builds did have bugs with date-time variables. It's the button thing they've still got to solve - ie the reason they reverted to an earlier firmware.

1 Like

Hi!

I am happy to report that the button now works…

When I moved to the recent build and the button stopped triggering actions, even though the event was received by Hubitat, I recreated the scenario in RM.

When I downgraded I created the scenario using Button Controllers. Perhaps what was needed was to recreate the scenario using BC?

I confess that I am an IT guy and I messed around with a lot of stuff in various apps before settling with RM for complex stuff, Button Controllers and Motion and Mode Lighting Apps. I also use Mode Manager of course.

Many thanks for those who helped and to the developers of Hubitat. What a great platform! I live in an small apartment buy I sprayed it with ZigBee and Z-Wave repeaters to have a strong mesh for both technologies :slight_smile: OCD, OCD

2 Likes