Mismatch of dwelltimeUp/dwelltimeDown in API vs. deviceHQ partial config update

Home › Forums › Conduit: AEP Model › Mismatch of dwelltimeUp/dwelltimeDown in API vs. deviceHQ partial config update

Viewing 1 post (of 1 total)
  • Author
    Posts
  • April 10, 2021 at 10:28 am #31733
    EG
    Participant

    Hi.

    I am working with several MTCDT-246A running 5.2.5. I set dwelltimeUp and dwelltimeDown to 1 in the AEP web interface. It shows as 1 both there and from the api GET loraNetwork command. However, in deviceHQ, the partial config update screen shows the current value for both of these as 0.

    I suspect the problem is with the deviceHQ web interface. It looks to me like that field is missing a “selected” on one of the options, so the correct value is not being displayed.

    Can you please confirm that there isn’t a problem with actually setting this value in the Conduit and that the discrepancy is only a web interface display problem?

    Thanks!

  • Author
    Posts
Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.