Skip to content

"device already exists" ajax async errors perhaps? #1693

Open
@pb66

Description

See https://community.openenergymonitor.org/t/device-already-exists-ajax-async-errors-perhaps/17807?u=pb66

Should we be trying to use data that might not yet be available?

Should these ajax calls be async: false instead?

return $.ajax({ url: path+"input/list.json", dataType: 'json', async: true, success: function(data, textStatus, xhr) {

$.ajax({ url: path+"device/list.json", dataType: 'json', async: true, success: function(result) {

relates to previous issues #1485 & #1618

[edit - just noticed the device call IS async: false already but I have no idea if emoncms.org is running latest emoncms. If it is, then it must be the input call change that is fixing things for me.] Ignore that! I had linked L895 (device/create.json) in error, it should have been L835 (device/list.json) which I've now corrected above and is inline with my original findings.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions