On my c5 I was trying to create devices shared by hubmesh on my c7. As soon as I click create I get an internal server error 500. Not sure what's up. On latest update. No other problems with the hub...
Open a live logging page and see what's there when pressing create. Or look back at the past log.
I've seen the error too. For me it seems to show up if I an creating devices that use a complex device handler (i.e. ecobee Suite).
I looked through the logs - did it happen for the Schlage lock?
If yes... I don't have exactly the same device, but can try with another zwave lock.
It happened with any device. But I deleted an old rule that wasn't in use by any devices anymore (as I had moved that hardware to the c7) and that seemed to fix it...
I started having this same issue last night (trying to share 4 virtual devices between two hubs... hubs are currently already meshed and sharing devices between one another). When I go to add any of these 4 devices, I get the 500 error.
Was there a specific way you identified the problem rules in question? I was deleting several virtual devices, and associated automation rules, right before I attempted to add these meshed devices to said hub, and I'm wondering if I've stumbled upon this same issue or something different entirely. Tagging @gopher.ny as well.
Post the log errors
Which hub produces the 500 error? Hub name works...
No log errors I could find being generated, other than the 500 that is shown to the user.
The hub generating the error was 52, devices were on 54.
I rebooted all the hubs yesterday (while also upgrading to latest release) and the error stopped. Prior to rebooting, I did confirm I could successfully share and delete devices shared from 52 to 54.
Found some errors in the back end logs. The fix is going to be in 2.2.9 since the issue is rare and reboot fixes it.
1 Like
Victor - This appears like it still is an issue - I was getting the 500 error trying to create a device on the hub being shared to. On 2.3.0.113 on both C7s that are meshed. Can you look at my logs and tell me what's up?
Rebooting the hub the devices are being shared to did fix it.
