for connecting the Pi to ThingWorx, there needs to be an actual connection in any sort. This could be through a (W)LAN or with some GSM connection - some way of allowing to connect the device to the ThingWorx server.
In case you're not allowed to connect the Pi directly to the Internet (I assume ThingWorx is somewhere on the net not on your local network), is it possible to use a (corproate) proxy server?
There's a nice example at
So what's the usual way of connecting from inside your network to the internet?
Is this allowed at all? If not, maybe some kind of mobile connection could be a solution, where a phone is acting as a WIFI hotspot for the Pi to connect to.
yeah - as long as you can ping from the Pi to the ThingWorx server and the other way around, you should also be able to connect directly through a EMS / EdgeSDK / REST-API etc.
Once machines (or the Pi) is moving outside of the local network it probably requires a tunnel to be able to connect to the ThingWorx server.
If it's not working in a local network, I'd check for network related issues or any firewall / port related issue - this could block some of the connections.
I hope this helps.
I'm trying to set a connection with the RasPi and Thingworx according to the Raspberry Pi Quickstart Guide (http://developer.thingworx.com/guides/thingworx-raspberry-pi-quickstart?page=1) and I'm having a problem at step 10. Whenever I execute the code sudo ./luaScriptResource I get the the following error: Attempting to GetPropertySubscriptions from server failed. code: 500, result:
What do you suggest me to do? I can see my RasPi on Monitoring as an unbound device but I can't manage binding with the RasPi and the Thing in Thingworx.
I just found the solution for my problem. Looks like someone had the same problem like me ([RaspberryPi Tutorial] Unable to connect LSR to EMS). I added an identifier in my config.lua, identifier = "PiThing", within my PiTemplate section and it solved the connection error.