Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:IoT
-
HD-Enabler:IDAS
Description
Created question in FIWARE Q/A platform on 14-03-2016 at 16:03
Please, ANSWER this question AT http://stackoverflow.com/questions/35992228/fiware-idas-timeinstant-attribute
Question:
Fiware - IDAS: TimeInstant attribute
Description:
I’m using the MQTT Ultralight agent. I have seen that when the agent registers into the context broker an entity related to a device, the agent adds to that entity the “TimeInstant” attribute. This attribute seems to be on UTC+0.
I would like to work with UTC +1. I tried modifying the device’s “TimeZone” when registering it, but seems that this doesn’t work, because the time continues to be on UTC+0. Here an example:
curl -X POST 172.21.0.23:8090/iot/devices \
-i \
-H "Content-Type: application/json" \
-H "Fiware-Service: red_entrada_4" \
-H "Fiware-ServicePath: /Prueba" \
-d '
'
Is there any way of modifying the default value of the “TimeInstant” attribute, in order to work with a specific UTC?
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Assignee | Carlos Ralli Ucendo [ ralli ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
HD-Enabler | IDAS [ 10884 ] | |
Description |
Created question in FIWARE Q/A platform on 14-03-2016 at 16:03 {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/35992228/fiware-idas-timeinstant-attribute +Question:+ Fiware - IDAS: TimeInstant attribute +Description:+ I’m using the MQTT Ultralight agent. I have seen that when the agent registers into the context broker an entity related to a device, the agent adds to that entity the “TimeInstant” attribute. This attribute seems to be on UTC+0. I would like to work with UTC +1. I tried modifying the device’s “TimeZone” when registering it, but seems that this doesn’t work, because the time continues to be on UTC+0. Here an example: curl -X POST 172.21.0.23:8090/iot/devices \ -i \ -H "Content-Type: application/json" \ -H "Fiware-Service: red_entrada_4" \ -H "Fiware-ServicePath: /Prueba" \ -d '{ "devices":[ { "device_id": "AC_2", "entity_name":"disp_entrada:AC_2", "protocol":"PDI-IoTA-MQTT-UltraLight", "entity_type": "disp_entrada", "timezone": "Europe/Madrid" } ]}' Is there any way of modifying the default value of the “TimeInstant” attribute, in order to work with a specific UTC? |
Created question in FIWARE Q/A platform on 14-03-2016 at 16:03 {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/35992228/fiware-idas-timeinstant-attribute +Question:+ Fiware - IDAS: TimeInstant attribute +Description:+ I’m using the MQTT Ultralight agent. I have seen that when the agent registers into the context broker an entity related to a device, the agent adds to that entity the “TimeInstant” attribute. This attribute seems to be on UTC+0. I would like to work with UTC +1. I tried modifying the device’s “TimeZone” when registering it, but seems that this doesn’t work, because the time continues to be on UTC+0. Here an example: curl -X POST 172.21.0.23:8090/iot/devices \ -i \ -H "Content-Type: application/json" \ -H "Fiware-Service: red_entrada_4" \ -H "Fiware-ServicePath: /Prueba" \ -d '{ "devices":[ { "device_id": "AC_2", "entity_name":"disp_entrada:AC_2", "protocol":"PDI-IoTA-MQTT-UltraLight", "entity_type": "disp_entrada", "timezone": "Europe/Madrid" } ]}' Is there any way of modifying the default value of the “TimeInstant” attribute, in order to work with a specific UTC? |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
HD-Chapter | IoT [ 10839 ] |
Summary | [fiware-stackoverflow] Fiware - IDAS: TimeInstant attribute | FIWARE.Question.Tech.IoT.IDAS.Fiware - IDAS: TimeInstant attribute |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
3d 4h 5m | 1 | Carlos Ralli Ucendo | 17/Mar/16 10:07 PM | |||||
|
25d 11h | 1 | Carlos Ralli Ucendo | 12/Apr/16 10:08 AM | |||||
|
16s | 1 | Carlos Ralli Ucendo | 12/Apr/16 10:08 AM |
2016-03-14 18:05|CREATED monitor | # answers= 0, accepted answer= False