Skip to main content
16-Pearl
August 20, 2025
Solved

Unable to push CSDK properties to ThingWorx 10.0.0

  • August 20, 2025
  • 1 reply
  • 3252 views

Hi,

 

I just installed ThingWorx 10.0.0 and created a service that will create

  • User
  • ApplicationKey for this User
  • Organization with a Top Organizational Unit with the User as a Member

After this, the service create a new RemoteThing and sets visibility to the Organization and adds Runtime Permissions (property read/write, service invoke, event invoke/subscribe) and Design Time Permissions (Read).

 

With the ApplicationKey and thing name I can now connect a CSDK application.

The application has three properties and on changing the status of the "isConnected" property, the Platform will run a service that will create these remote properties on the RemoteThing.

 

However, when running the CSDK I can see that the properties are connected but they fail to synchronise with the following error in the CSDK:

 

[ERROR] 2025-08-20 10:58:30,206: twSubscribedPropsMgr_PushPropertyInfoList: Error pushing properties for ON1111-2. Error: 1111.
[ERROR] 2025-08-20 10:58:30,206: twSubscribedPropsMgr_PushProperties: error pushing or persisting property list, code: 1111

 

This continues throughout any restart of the CSDK (where properties are no longer touched on the RemoteThing). Only when restarting ThingWorx, the properties will synchronise.

 

Why would this be blocked, but starts working after a ThingWorx restart?

 

There seems to be some kind of permission issue, because everything works just fine with an Administrator-ApplicationKey.

 

Thanks for your help,

Michael

Best answer by Constantine
If you change the owner, then you should be able to remove all other permissions. You might want to check services like SetPropertyValues instead.

Beware — Allowing a remote device own some entities has pretty deep security implications. If I remember correctly, it also grants design time ones, meaning you can impersonate System.

/ Constantine

1 reply

mneumann16-PearlAuthor
16-Pearl
August 20, 2025

- deleted due to a temporary hiccup that made it work.

The issue still continues.

18-Opal
August 20, 2025
If you change the owner, then you should be able to remove all other permissions. You might want to check services like SetPropertyValues instead.

Beware — Allowing a remote device own some entities has pretty deep security implications. If I remember correctly, it also grants design time ones, meaning you can impersonate System.

/ Constantine
mneumann16-PearlAuthor
16-Pearl
August 21, 2025

Thanks Constantine!

I somehow managed to make the original issue work.

 

You have a good point about ownership here.

For now I created a generic user (without password nor any other permissions) that owns all remote devices, and I kept the assigned permissions for the Things themselves. Before that, we had the owner set to whoever created the device, but that put unnecessary ownership questions to the original creators.