I can not test uplink messages anymore. Since 5 days. Something wrong with the Dev portal?
Server returned HTTP response code -1
Response info:
Error in sending rest post to developer url http://XXXXXX, for device 0059AC00001802C7, payloadhex 8080. Error details: com.mendix.modules.microflowengine.MicroflowException 301: Moved Permanently at DevLoRa_UpLink.SendLoraMessToDev (CallRest : 'Call REST (POST)') at DeviceMngmt.IVK_SendTestMessage (SubMicroflow : 'SendLoraMessToDev') Advanced stacktrace:
Sorry for my late response Amine. I thought we'd talked in private about this.
We are working on a new "test uplink" button/function. The current button doesn't support SNI (security check).
Therefore we noticed many users got the test uplink working but are experiencing issues when using the application server.
We are working on a new "test uplink" button/function. The current button doesn't support SNI (security check).
Therefore we noticed many users got the test uplink working but are experiencing issues when using the application server.
Hi Tim
It works now but since some days I dont receive SPfactor, Port, time and many more in the json body . anything changed in the dev portal?
{ "LrrSNR": "0", "Lrrid": null, "SpFact": 0, "SubBand": null, "CustomerData": null, "FPort": 1, "Channel": null, "FCntUp": -1, "Time": null, "DevEUI": "0059AC00001802C7", "payload_hex": "808080808080808080808080", "CustomerID": 0, "LrrRSSI": "0", "ADRbit": 0, "ModelCfg": 0, "mic_hex": null, "LrrLON": "0", "LrrLAT": "0", "FCntDn": 0, "Lrcid": null, "DevLrrCnt": 0 }
It works now but since some days I dont receive SPfactor, Port, time and many more in the json body . anything changed in the dev portal?
{ "LrrSNR": "0", "Lrrid": null, "SpFact": 0, "SubBand": null, "CustomerData": null, "FPort": 1, "Channel": null, "FCntUp": -1, "Time": null, "DevEUI": "0059AC00001802C7", "payload_hex": "808080808080808080808080", "CustomerID": 0, "LrrRSSI": "0", "ADRbit": 0, "ModelCfg": 0, "mic_hex": null, "LrrLON": "0", "LrrLAT": "0", "FCntDn": 0, "Lrcid": null, "DevLrrCnt": 0 }
Hi Amine, there has been no changes to the portal. I just got this confirmed.
With my device I do see the SpFact value and others in my output. Something is going wrong indeed at your end. Maybe you can try to switch over on a hookbin to look what output you'll get there?
With my device I do see the SpFact value and others in my output. Something is going wrong indeed at your end. Maybe you can try to switch over on a hookbin to look what output you'll get there?
Hi Tim
I tried on hookbin, same resutl. most of the body is empty
{
"LrrSNR": "0",
"Lrrid": null,
"SpFact": 0,
"SubBand": null,
"CustomerData": null,
"FPort": 1,
"Channel": null,
"FCntUp": -1,
"Time": null,
"DevEUI": "XXXXXXXX",
"payload_hex": "808088",
"CustomerID": 0,
"LrrRSSI": "0",
"ADRbit": 0,
"ModelCfg": 0,
"mic_hex": null,
"LrrLON": "0",
"LrrLAT": "0",
"FCntDn": 0,
"Lrcid": null,
"DevLrrCnt": 0
}
I tried on hookbin, same resutl. most of the body is empty
{
"LrrSNR": "0",
"Lrrid": null,
"SpFact": 0,
"SubBand": null,
"CustomerData": null,
"FPort": 1,
"Channel": null,
"FCntUp": -1,
"Time": null,
"DevEUI": "XXXXXXXX",
"payload_hex": "808088",
"CustomerID": 0,
"LrrRSSI": "0",
"ADRbit": 0,
"ModelCfg": 0,
"mic_hex": null,
"LrrLON": "0",
"LrrLAT": "0",
"FCntDn": 0,
"Lrcid": null,
"DevLrrCnt": 0
}
Hi Amine,
It looks to be a pre-generated empty body. Can it be the case you're using the "Test uplink" button instead of the LoRa device?
The LoRa dev portal does passthrough the messages untouched from ThingPark. When using the "Test uplink" button you'll receive no values in the JSON body as it has been generated by the LoRa dev portal.
It looks to be a pre-generated empty body. Can it be the case you're using the "Test uplink" button instead of the LoRa device?
The LoRa dev portal does passthrough the messages untouched from ThingPark. When using the "Test uplink" button you'll receive no values in the JSON body as it has been generated by the LoRa dev portal.
Hi Tim
Yes you are right.
I have a question about downlink messages via dev portal.
Are the messages delivered to the device from the dev portal?
I am asking because i see the downlink on the dev portal but i dont see the device updated
Are there any downlnk lmitations in the dev portal?
Cheers
Amine
Yes you are right.
I have a question about downlink messages via dev portal.
Are the messages delivered to the device from the dev portal?
I am asking because i see the downlink on the dev portal but i dont see the device updated
Are there any downlnk lmitations in the dev portal?
Cheers
Amine
Hi Amine,
Are the messages delivered to the device from the dev portal? For all details about downlink you can refer this topic about LoRaWAN. The messages are been sent by the LoRa core server. The Dev portal is connected to the server.
Are there any downlnk lmitations in the dev portal? Your device should always obey duty cycle. KPN offers serveral different bundles where the number of uplink and downlink message are given per device. Currently, the largest bundle offers 300 messages per day. Sending more is possible, but you will be charged additional cost per extra message.
Useful information from the FAQ:
When will my downlink message be delivered to my device?
Depends on your device class.
How do I send a downlink message?
Please refer to this topic.
Useful information from the FAQ:
When will my downlink message be delivered to my device?
Depends on your device class.
How do I send a downlink message?
Please refer to this topic.
Thanks Tim
So the downlink messages will be queued until the device sends the next uplink message?
The device i have expects an acknoledgment for one specific uplink message. So the device will not receive this message until next uplink?
Cheers
So the downlink messages will be queued until the device sends the next uplink message?
The device i have expects an acknoledgment for one specific uplink message. So the device will not receive this message until next uplink?
Cheers
Hi Amine,
It depends on your device class, as mentioned in the device class topic. It's explained there.
Class A (Default)
Completely uplink oriented.
Class C (Continuous)
The device is always available for downlink,
It depends on your device class, as mentioned in the device class topic. It's explained there.
Class A (Default)
Completely uplink oriented.
Class C (Continuous)
The device is always available for downlink,
Reageer
Meld je aan
Heb je al een account? Inloggen
Welkom
Nog geen account? Maak een account aan
Inloggen of registreren met sociaal netwerk
Inloggen met Facebook Login with LinkedInof
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.