-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENTITY_GENERIC_ERROR when updating an existing device #205
Comments
Similar to #204 , try to change your code for the provisioning:
Besides, I also recommend:
Please let me know if it solves your problem. |
Branch 205-ENTITY_GENERIC_ERROR-when-updating-an-existing-device created! |
I edited the code as you mentioned, so now it looks like that:
But I still get the same error. The problem here is, I cannot update the motion sensor device before I published the first MQTT message. When I set an attribute via MQTT for the first time, an entity of the motion sensor will be created and the |
Okay, I just find these changes from telefonicaid/iotagent-node-lib#1413. The error is not caused by FiLiP but the IoTagent. I think the solution is not to rely on the initial creation of IoTagent anymore but to create the corresponding entity in context broker actively. That will surely increase the stability of your IoT service and the compatibility for the long term. |
After I created a service group and provisioned a motion sensor device I get an error when I update the device by using a PUT-request with the IoT-Agent endpoint:
The program exits with an
When I looked at the response content of the PUT-request of the IoTAClient, I get the error
I fixed this problem for me by including the attribute "entity_name" in the PUT-request of the "update_device" method:
I again used the FIWARE setup from the Git-Repo https://github.com/FIWARE/tutorials.IoT-over-MQTT.git
The text was updated successfully, but these errors were encountered: