Letavia

I tried with random strings it didt work. And if I looked at the gk-deploy script, user key is not mandatory. Can you shed a light here? Edited: I used...

I also struggled with the same condition, what version of idm and pep-proxy are you using? Mine is both with 7.0.2. When I tried to upgrade to 7.5.0 for both...

Did you use docker or manual installation? I used docker, first with version 7.0.2 and came across the same issue as yours then with 7.5.0 which gave me the error...

I know exactly what you mean and am doing the same. The thing is there's a new parameter introduced in 7.5.0 called PEP_TOKEN_SECRET if you look at config.js file and...

Hi, I finally managed to do it with 7.5.0. With 7.0.2 apparently there is an error in the config.js that you have to fix after you install it. With 7.5.0...

Any update on this issue? I tried with the latest docker image on fiware/lightweightm2m-iotagent repo, using "active" instead of "attributes" in the payload for device provisioning, but when I checked...

Yes, and I will continue in [issue #112](https://github.com/telefonicaid/lightweightm2m-iotagent/issues/112#issuecomment-486260958).

What is the status of this? I tried but still CB does not read the active attributes sent by the client (device).

I followed the instructions for [device provisioning](https://github.com/FIWARE-GEs/iot-agent.LightWeightM2M/blob/1cdf6abc96654aca2f912cad01d5fdfcd21d7ec8/docs/configurationProvisioning.md). Here is my device configuration: ``` fiware-service: factory fiware-servicepath: /robots payload: { "devices": [ { "device_id": "robot1", "entity_type": "Robot", "entity_name": "robot01", "attributes": [...

any advice on this issue?