Upgrade from 4.2 to 4.6 device computed attributes now just show loading spinner

Hi,

Firstly, thank you for making a great tracking system.

I'm trying to add computed attributes, as we are testing the Teltonika FMC130 to see if we can get the data we need from our vehicles.
Before upgrading, computed attributes were working.

Steps to replicate:

In the Devices section, click on any device.
In the State section, click on the Computed Attributes button.
The Computed Attributes modal opens, but the loading spinner stays.

You can click on the Add button and add a Computed Attribute. This gets added to the attributes table in the database, but it just closed the Computed Attribute modal and the Computed Attributes modal still just displays the loading spinner.

The device_attributes table is not updated, I tried adding records directly, but it made no difference.
I've stopped, then restarted the service.
I've reinstalled (except for the database).

I've tried this in Chrome and Firefox, both behave the same.

Any assistance would be appreciated.

Start troubleshooting by checking developer tools.

In Firefox, I'm getting this in the console:

unreachable code after return statement ext-all.js:22:366125
TypeError: k is null ext-all.js:22:647130

In Chrome, in the console I get this:

ncaught TypeError: Cannot read property 'isModel' of null
    at F.extractData (ext-all.js:22)
    at F.extractData (ext-all.js:22)
    at F.readRecords (ext-all.js:22)
    at F.read (ext-all.js:22)
    at F.processResponse (ext-all.js:22)
    at F.<anonymous> (ext-all.js:22)
    at Object.callback (ext-all.js:22)
    at F.onComplete (ext-all.js:22)
    at F.onStateChange (ext-all.js:22)
    at XMLHttpRequest.t (ext-all.js:22)

I also added a new device, then deleted it, logged out. Then when I logged back in, all the devices have been removed from my login. However, in the user_devices table, there are mutilple records for my user id and the same device id.

Sounds like you have a problem with foreign key constraints in the database. I guess you would need to create those manually.

Foreign keys are in place, engine is InnoDB, I'll look into that some more though. Would that possibly be what is causing the issue with Computed Attributes? If the FK's are not being enforced?

If records in the linking tables are not removed, you usually get behavior like this.