[RELEASE] Hub Information Driver v3

I did a migration from a C7 to a C8 Pro and updated my Hub Info Driver to V3.

It still showed the hub info as my old C7 hub with all old IP address and info.

So I created another virtual multi sensor and also had it “replace” the old virtual senor so the settings would copy over and point to my dashboards where it is used. Then I go into Prefs and set that all up again, then to commands and clicked configure, initialize, refresh and things looked to all populate correctly except the cloud attribute says invalid endpoint.

In the logs it shows…

**dev:6838**2026-06-16 8:41:29.013 am

warn

Status 408 while fetching Public IP

**dev:6838**2026-06-16 8:40:56.471 am

info

Hub Information v3.1.27 initialized

What did I miss getting this working on my new C8 Pro?

Sounds like you should be almost completely functional. Cloud endpoint is looking for the URL to a classic dashboard (cloud version) or MakerAPI.

The 408 is a timeout error and normally will correct itself on the next iteration.

I think the Hub Info driver breaks in the 2.5.2 release. Just upgraded and my Hub Info screen never loads. If I open it in a new tab, the green dots just circle and circle. The devices overview page also shows stale information, prior to the reboot/upgrade. The only thing I see in my logs are the update checks.

Hmmm I'm running 2.5.2.128 on 4 different hub models and not seeing an issue. Might want to try a reboot with database rebuild to see if that corrects you're issue.

A reboot was the trick. I did not do a DB rebuild since the last time I did that the hub went both sideways and South. And I'm still scared to do that again.

But... the reboot did it. Honestly didn't think that would be needed since it literally just rebooted from the upgrade.

Hi, new to this driver, very nice driver​:grinning_face:. I have a question: I would assume that if you set "Check for Firmware" to 1, the hubUpdateVersion field would update every hour. In my case, however, the hubUpdateVersion field remains at 2.5.2.127, even though an update to 2.5.2.129 is already available via notifications. Am I missing something? Do I need to adjust anything else on the device to get that field to update?

The numbers there refer to the polling queues.

So setting that to 1 tells it to refresh when polling queue #1 runs. If you haven't set those up yet the only time anything will be refreshed is at startup.

Very helpfull, sorry for the stupid question :face_with_peeking_eye:

Never a stupid question, setup is a wee bit involved and it's easy to miss that step.

Hah! I started programming on a Vax 11780! I loved it... though most of the students simply used the dumb terminals for "phone"! (remember that?)

I do now that you mention it :smiley:

Been out of pocket for a while, so maybe this has been addressed at some point, but I'm getting this error:

org.quartz.JobPersistenceException: Couldn't store trigger 'dev1251Once.poll1' for 'dev1251Once.poll1' job:Unique index or primary key violation: "PUBLIC.PRIMARY_KEY_42 ON PUBLIC.QRTZ_SIMPLE_TRIGGERS(SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP) VALUES ( /* key:1186407 */ 'QuartzScheduler', 'poll1', 'dev1251Once')"; SQL statement:
INSERT INTO QRTZ_SIMPLE_TRIGGERS (SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP, REPEAT_COUNT, REPEAT_INTERVAL, TIMES_TRIGGERED) VALUES('QuartzScheduler', ?, ?, ?, ?, ?) [23505-224] on line 258 (method initialize)

Running v3.0.26. Any ideas?

That actually sounds like a hub scheduler issue - most likely database related. Might try a hub reboot with a database rebuild.

within the last 2 Hubitat updates, I am getting

**dev:4554**2026-10-10 6:53:56.490 am

error

Time zone format error: sun.util.calendar.ZoneInfo[id="US/Eastern",offset=-18000000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=US/Eastern,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]
java.lang.SecurityException: Unrestricted script compilation is not allowed from app or driver code when rebooting.

Error appears twice early in logs. I am on the Hub Information latest version and also tried repair with no change. A configure and initialize also. Doesn't seem to effect the sunrise or sunset. AI said Hubitat tightened down security for whatever that's worth. thanks v3.1.32 2.5.2.134

Interesting. That's a new one. Checking to see if it happens on every reboot or if it's just the first boot after the upgrade

mine are all reboots have error now.

Yep, mine too. Good news is that it looks like it only affects the reformat of the time zone string to JSON. On the surface not anything that I haven't done a 1000 times before, so it may be an interesting dig.

All your stuff is excellent. I check logs every reboot this is very recent. Hubitat changed something per AI. thanks

They did, and I see a few other apps/drivers are having similar issues, but if it is something simple maybe I can provide some input to the others and save them some time.

The strange thing, at least in this case, is that it is a simple set of string manipulations.

quick side question, do you foresee a way to include the cloud count numbers in hubinfo. be nice to monitor them from LOCAL dash :slight_smile: