Cannot create new RM Rule. Error 404 App type with namespace: hubitat and name: Rule-5.1 has parent type that does not match current app

I am setting up a new C-7 from scratch, upgraded to 2.3.6.144 and cannot get Rule Machine 5.1 to work. When I click Create New Rule I get the error:

Error 404
App type with namespace: hubitat and name: Rule-5.1 has parent type that does not match current app

I have no devices installed/connected and just one virtual switch set up. I have tried backup / restore and done the also hit the http://hubitat.local/hub/advanced/reloadAppAndDriverDefinitions endpoint, but it made no difference.

If there is nothing on the hub, can you try doing a soft reset from the Diagnostics Tool at http://hubitat.local:8081 ?

I tried setting up a hub from scratch and was unable to reproduce this. But I also started with 2.3.6.144 and didn't update from an earlier version.

Did soft reset… unfortunately no change. What does a soft reset do? I see all the settings I already had main in the setting section and my one virtual device is still there?

I'm having the same issue. Can one of the devs please chime in on what we can do to fix this? This feature is the main reason I even bought this device.

I had this same 404 error and the soft reset via the Diagnostics tool worked to clear the problem. Soft reset via pushing the button on the bottom of the Hubitat does not fix the 404 error.

Soft reset and restore cleans up a corrupt database. Best way to soft reset is download a new backup (not one of the stored ones) then do the soft reset from port 8081. On reboot restore the file you downloaded.

Backup, soft reset and restore did not work for me. I just loaded about 20 devices today (migrating) then went to RM and got nothing but 404 when i click create rule. Took a backup before that and used it to restore after the soft reset but still getting 404.

I found this solution in another post:

http://hub.ip/hub/advanced/reloadAppAndDriverDefinitions

But that worked for me on only one of my two affected hubs. The other required a full reset and fortunately, that was my dev hub with no zwave devices.