Upgrade 2.3.9.177 -> 2.4.2.160 = Visual/Web (?) Errors

🛎️ Get Help
1

I have a mature system that is very stable, and I have rarely made a change in the last several years! I typically just apply some updates.

Yesterday I upgraded from 2.3.9.177 to 2.4.2.160.
The hub continues to work fine. The apps, rules & devices continue to work fine. BUT!

Every single device I issue a command to via the web interface produces this error (?):

image
image1439×328 29.1 KB

In the above example, I switched the switch on. The switch status changed to ON, the log files (even for devices that allow enhanced debug logging) show no errors, the device physically functions as it should.

A similar error is displayed when changing the device Type; again it appears to be happening with every device:

image
image1429×288 22.1 KB

The device Type is however changed successfully - I only have to refresh the page to see it.

Any ideas?

2

Two ideas (or really one and one question):

  1. Try clearing cache for at least Hubitat IPs in your browser, or do a full/cacheless reload (Shift+F5 or whatever that may be in your particular browser).

  2. Are you using any unusual network setups, like accessing your hub UI through a cloud tunnel or reverse proxy?

2 Likes
3

I think you hit the jackpot!

I use pfSense with HAproxy which allows me to use my own local [internal] "domain". Again, been using it like this for Hub access for years with no "visual" issues! Must be due to the new UI design.

When changing to the Hub IP, everything works 100% as it should - no "display" errors.

Thanks for the outta the box though!