[2.3.0.123 C7] Error 500 on Device Page

I installed 2.3.0.123.

I started to create a new group (clicked create and started filling the page in--when I realized I was creating a group and not a scene, so I clicked "Remove" before saving).

Then, I created a new scene (with a scene capture device) and a transition.

I then went to view the device list--and all I see is an Error 500 now.

I'm also unable to "capture" the scene. There seem to be no errors logged for the device page error. But, attempting to capture the scene logs the following:

By finding log references and manually creating the URL for the 3 new devices:

Not sure what tripped it up.

Removing the transition and the capture device didn't help--but removing the scene I just created seemed to solve the problem (something was clearly messed up with that scene, as it never would actually "capture" either).

1 Like

First time user here. I just started (Updated to the same update) and I get the same error on the device page also. I am not much help but it could be a thing right now.

Rolling back to 2.3.0.121 -- now, I can actually capture the scene.

Browse to: http://<your hub's IP address:8081/

Select "Restore Previous Version"

2 Likes

I, too, am experiencing this error code whenever I attempt to access the Devices tab. This has only started to occur since a hub update to the most current version today.

I performed a hub reboot and it seems to have solve this.

having the Same ERROR on my C-5 hub , Reboot hasn't helped, Rolled back to 2.3.0.113 and still have the problem along with others

Me too. Updated to .123 and error started.
Will downgrade to 121.

Had this with my C4, but a reboot seems to have solved it.

I rolled my C4, C5 & C7 to .123 and it only happened on the C4.

S

For me, it seems like if I edit any device settings, the Error 500 results after I hit the save/done.

S

Same for me. I've just reboot the hub and now works well

It happened again sometime after rebooting. Unfortunately, rebooting will not fix it. All this is due to the last software upgrade.

@bobbyD @gopher.ny I’m seeing this too (error 500 after doing anything on device page, then going back to devices listing).

Seems to happen on any device (Lutron integration Caseta lights, Z-Wave devices, etc).
C-7 with 2.3.0.123. Very vanilla system. But it ran fine for hours, with automations working, until I manually touched something on a device page to test this reported bug. Reverted back to 2.3.0.121, problem fixed.

Have never seen this before in all the updates ever since I got my C-7 over a year ago.

Yeah, it's a new one. A reboot fixes it. Expect a bug fix release today.

4 Likes

Looks like @gopher.ny is on it

Edit: He’s bloody quick on the keyboard too.

5 Likes

Well, that page is private, not viewable by us mere mortals.

1 Like

Bunch of trouble makers over there, always peering under the covers and trying to rewire things…:rofl:

Please revert to 2.3.0.121. I've pulled 123 in the meantime.

6 Likes

This is the inevitable support curse that results when a release is made on Friday afternoon of a holiday weekend. Staff is working too hard. Take the weekend off, give yourselves a much-needed rest, spend time with your family.

13 Likes

Thanks - downgrade to .121 sorted it. Agree with comments on releasing over the holidays, not ideal bar an urgent security patch.

I just ran into this as well and am rolling back now.

All was working well, what seemed to trigger it was I changed the device label on a device, then got the 500 error when going back to the devices.

Thank you guys for your hard work on this platform!