New fault requiring reboot to resolve


C7 Hub on Platform 2.4.4.135
I have had to reboot the hub 3 times recently after kitchen lights switching by "Simple Automation Rules" on Zigbee, at 06:40am, were not implemented.
On checking "Logs", 2 of the 3 seem to be associated with a an error at 06:37 stating:

jjava.lang.NullPointerException: Cannot invoke method getDataValue() on null object on line 2269 (method parseBridgeInfoResponse)

On clicking on this I am referred to an entirely different area, i.e. some Hue lights in the living room.
I have been using Hubitat for many years and have not had many problems, but this is well beyond my level of fault finding.
I would appreciate any help understanding what this fault is and where to look to resolve it.


It may help if you can provide a screenshot of the logs in and around this error having appeared in the list of logs.

It may also help if you provide some screenshots of the setup involved in what you believe to be the App/Devices involved. Feel free to wait until a few more details are worked through...

When you say "On clicking on this..." where exactly are you clicking? If you click on the coloured Info/Debug/Warn/Error then you will be taken to the Device detail or App page that produced the log (something I embarrassingly took a long time to realise / be made aware of :slight_smile: ).

If I had to guess... from your error message referencing parseBridgeInfoResponse, I am expecting you are using Hue lights paired to a Hue bridge. Similar to my earlier comments, I would suggest explaining your current setup, e.g. are you using a Hue bridge with lights paired to it then connected to HE using and Integration app of some kind (built-in or Community-developed)? Etc...

Nice to hear someone who has had such as smooth run up until this likely simple issue to resolve....

Thank you for your response.
Here is a screenshot of logs around that time:


Hovering over the red "error" I get "Show details for app Hue Bridge Integration etc"
As you suggest, I am using a Hue lights paired to a Hue Bridge, but can't answer method of integration as this was done many years ago. However, clicking on the red "error" it opens a menu to "Add Hue Bridge Devices" which rather indicates that it is not integrated.
Tried to include a further screenshot but it would not upload so will do further entry,

This is what I get on "Add Hue Bridge Devices"
Screen Shot 2026-03-02 at 10.57.10

Is that the built-in Integration, Coco-Hue or the Advanced Integration?

I do apologise for my ignorance but I don't recall and I don't know where to look to answer your question.
Under "Apps" I get this:
Screen Shot 2026-03-02 at 11.13.04

That's it... and it would show up in the URL when you clicked on the error in the logs...

Looks like you are using the built-in Hue Integration... I'm guessing the original... Ultimately one for the HE dev's to comment on...

The null object part of the error is one I have seen if devices were deleted but the automations were still intact. If you are using the hue bridge, have you tried checking to see that the devices are still integrated in Hue? Have you made any changes to your Hue setup?

Just thinking outloud....

I don't see the the connection between the Hue Bridge error and your problems with Simple Automation Rules, nor -- considering that, based on your description, no such lights are involved with that rule -- any reason why there should be one. (While errors in general can be a concern, a single error in the same general time as an unrelated automation doesn't mean that this error is necessarily the cause of a different problem.) Is your description accurate, that your lights are "Zigbee" (as in, directly paired to the hub via Zigbee) and not Hue Bridge lights?

While looking at Logs is good in general, I'd enable all logging for your rule (if it isn't already) and look at those logs first. You're more likely to find (or rule out) the source of the problem that way. For this and other things that will help you narrow down the problem, start with tips like these at: How to Troubleshoot Apps or Devices | Hubitat Documentation.

1 Like

Likewise, I don't see any logical connection between the Hue hub and associated lights and the Simple Automation Rules devices other than the fact that the error occurred at the same time as an SAR switching action.
I suppose it must be coincidence but I have never had this problem in 10 years and it followed installing 4 new Sonoff ZB Mini
Apart from the Hue lights, all my Zigbee devices are paired with the C7 hub

I have not intentionally made any changes to Hue devices and they are all still responding on the Hue app

If you were using Hubitat in 2016, you should have done your troubleshooting with the founders, with whom you would have been closely working for pre-alpha testing. :wink:

This is why I'm trying to be extra clear about whether these are Zigbee devices or Hue devices (from the perspective of the hub; both are Zigbee in some sense).

Regardless of the device type or length of time, there is no substitute for the specific troushooting techniques I referred to above. Please try some and let us know what clues you find.

3 Likes

Sorry, please excuse my ignorance as I am not getting past 1st base on your suggested procedure
For instance, does the app that appears to be linked to my Hue hub (Hue Bridge Integration [Philips hue 96544BF0]) have the facility to select "Enable logging"?
I only have a very simple operation on the Hue lights switching on at dusk and off at 23:30 and "Enable Logging" is selected on this

You want to enable logging in your rule, the app you are actually having problems with (but yes, both have logging options). Hue is just a distraction until proven otherwise at this point.

3 Likes

Now I am really confused because I thought it had been established that the Hue app is the problem, because when I click on the error in question, it takes me to the Hue app.
I thought it was agreed that the distraction was the SAR switch which just happened to occur at near the same time as the error and as such was just a coincidence.

1 Like

This means the Hue integration app is the origin of that specific log entry. However, from the information provided so far, there is no reason to assume it is related to your actual problem, which is apparently that some devices you are trying to control with Simple Automation Rules are not responding as expected. According to your previous posts, these are Zigbee devices and not Hue integration devices. So aside from the timing, as you note, there is really no reason to believe these two are related.

Isn't this "distraction" your actual problem? :slight_smile: (Simple Automation Rules failing to achieve your desired outcome, turning some Zigbee switch on or off?)

You will need to start with app logs or any of the suggestions above to narrow the possible causes down.

OK, Thanks. All the SAR's have "Enable Logging" on, so we will see if the same fault occurs tomorrow morning

1 Like

I think once you have the outcome of your additional logging it may also pay to post a screenshot showing the rule you are having issues with and drilling into the exact setup of the devices that are not responding as you expect. I say this because I seem to have got a different interpretation of what your setup is and the problem compared to @bertabcd1234 , i.e. all the Hue lights are paired to the Hue Bridge and brought in via the integration App and some of them are not being adjusted correctly by the SAR automation, seemingly with an error being thrown by the hud integration app. The extra logging will help to clear some of this up I expect.

1 Like

I was trying to figure that out but was neither answered nor corrected. :slight_smile:

But this is why I think they are Zigbee:

Knowing what is actually going on and what devices are involved would indeed be good. I'd suggest sharing the actual rule and not just logs if the problem recurs -- but, again, the logs that would be most helpful to start with are those from the rule app if that's what seems to not be working to start.

(But have I mentioned how you can try other troubleshooting tips from the doc in the meantime without needing to wait for the scheduled job? :slight_smile: Knowing if you can control the device yourself would be a good place to start, too, for example.)

EDIT - I see now I probably aided some of the distraction by getting hung up on the Hue error log entry. You were right to get more info about the rule rather than focusing on the logs first.

Yes, @david.storer 's response to my original post is what I was basing my comments on just now:

Plus, in response to your original questions:

Either way, I agree it would be helpful to know for sure how the devices involved are configured.