I am able to make remote service calls and get returned data, however... I'm getting this polled repeatedly when I get connected with a device on my EMS
[INFO ] 2015-09-16 13:59:28,222 Truck000: Error occured while accessing EMS. Checking isConnected.
[INFO ] 2015-09-16 13:59:28,251 Truck000: EMS is available: true, online: true
[INFO ] 2015-09-16 13:59:28,254 Truck000: Attempting to GetPropertySubscriptions from server failed. code: 500, result:
This is in the monitor under logs:
Unable to dispatch [ uri = /Things/*000/Services/GetPropertySubscriptions/]: Unable to Invoke Service GetPropertySubscriptions on Truck000 : Not authorized for ServiceInvoke on GetPropertySubscriptions in Truck000
The appKey I'm using to authenticate is hooked to "system" as User Name Reference. Is this a permissions issue?
Solved! Go to Solution.
Mike, if you are just testing, can you create an appKey with the Admin user and use that to connect?
Mike, if you are just testing, can you create an appKey with the Admin user and use that to connect?
I've changed the appkey user to Administrator and the error is still there.
Are you able to browse and bind the remote properties from the 'Manage Bindings' section?
Yes I am.
Can you attach both config.json and config.lua files? Also, please do set the log level to TRACE in the config.json, as that would print out detailed logs. Once you get these logs, please do attach that too. Here is how to set TRACE mode in the config.json:
"logger": { | |
"level": "TRACE", | |
"publish_directory": "/_tw_logs/", | |
"publish_level": "TRACE", | |
"max_file_storage": 2000000, | |
"auto_flush": true |
},
Aanjan, I think I had some intermittent connectivity issues that were making it look like it still wasn't working. The thing does seem to bind properly now.