Home Forum Software Automated Dynamic ID allocation

This topic contains 10 replies, has 4 voices, and was last updated by  Radu Motisan 2 years, 9 months ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #658

    Radu Motisan
    Keymaster

    To allow DIY / Kit units, a mechanism to allocate device IDs automatically, without requiring a firmware update is required.

    My ideea is to start the device with a default Device ID (and a default MAC address), then the very first time the unit connects to the server, it would receive a unique, new ID, will save it to its EEPROM and reboot.

    On startup, the Device ID from the EEPROM will be used.

    The only drawback is the user will not know what is the device of his station. Solutions?

    • This topic was modified 4 years, 5 months ago by  Radu Motisan.
    #664

    Lars
    Participant

    I can only think of two possibillities here, both depending on if the hardware can do it.

    1: Blink the ID using the ethernet port lights at boot time. Depends on the hardware having that kind of access to controlling those lights directly.

    2: Run a webserver on the unit, serving only the ID. Depends on the unit having resources to run a webserver.

    None of those are very user friendly though.

    #667

    Jeff Cooper
    Moderator

    How about a portal on the website that compares visitor ips with the ips of units. That way you can find your units id as long as you are connecting to the urad site from the same public ip.

    #703

    Lars
    Participant

    @jeff: Yes, I vote for that one!

    That should also give access to correcting which location the unit is at.

    #704

    Radu Motisan
    Keymaster

    Hmm…this is an excellent idea! I can’t find a scenario to invalidate it yet. But let’s think it through.

    #727

    vinz
    Member

    Just a thought,
    schools and companies often have all the same public IP.

    The device has to be programmed anyways. So maybe there is a way to automatically set the ID / MAC (besides a shared secret for a hash/crc check (for data, urls, ..)).

    The device has to be tested and calibrated anyways, so maybe there it can be set online and given its ID / MAC (besides a shared secret for a hash/crc check (for data, urls, ..)).

    Both cases the ID is known (?) at delivery.

    DIY sensors may ask for an ID on uradmonitor.com later on.

    #728

    vinz
    Member

    Scenario (just a thought):

    1) the device is soldered an programmed (all the same)
    2) the device is set online while testing/calibrating at urad-laboratories
    2a) it atomatically pulls its new ID and secret from a database.
    3) it appears in an (online or local) website as beeing new (devices without eMail)
    4) one has to enter customers eMail
    5) device-id, login-data, and all wellcome-info are sent to customer automatically

    (when user logs into his device on uradmonitor.com he may also need to see its local IP and a link, but that is some kinde of private information… )

    • This reply was modified 4 years, 5 months ago by  vinz.
    #3281

    Radu Motisan
    Keymaster

    A new firmware revision will drop hardcoded device IDs, instead, when a unit is first connected to the internet, it will receive its ID from the server and store it in its EEPROM. When the station owner opens the webportal, the server will match his IP with the new station, and present a registration dialog. This window will appear until the station is fully configured (user details, email, station ID, a Boolean for configuration done, all stored in a DB table). The user will then see his new station (and any other he has) in the station admin panel where more options are available

    #3283

    Radu Motisan
    Keymaster

    In progress. Will have this in place for the new devices to be shipped out.

    #3284

    Radu Motisan
    Keymaster

    This will use great suggestions posted by @jeff and @vinz in https://www.uradmonitor.com/topic/automated-device-ids/

    #3323

    Radu Motisan
    Keymaster

    I’m happy to report this functionality is already implemented, both in firmware and in server backend, and it is now entering testing phase.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.