Windows python agent

What product/components do you use and which version/fix level are you on? 10.13

Is your question related to the free trial, or to a production (customer) instance?

Customer instance

What are you trying to achieve? Please describe it in detail.

Connect Windows device via downloadable Python client

Do you get any error messages? Please provide a full error message screenshot and log file.

The client is not currently connected

Have you installed all the latest fixes for the products and systems you are using?

Yes

I’ve downloaded the installed the Windows Python agent from cumulocity-client · GitHub Topics · GitHub . I’ve got Python installed but when I try to do a c8ydm.start, the client starts but doesn’t bootstrap the device I entered in the platform. I’m thinking I dont’ have the agent.ini file configured correctly - does anyone have any experience doing that?

Thanks!

Hi,
can you be more specific with regards to the client? The link you included leads to an overview page of many clients.
Cheers!

What do you have in the agent.ini?

I guess he means that because he refers to agent.ini.

Could you post your agent.ini?

I did the pip install c8ydm on the Windows device.

[secret]
c8y.bootstrap.tenant = management
c8y.bootstrap.user = devicebootstrap
c8y.bootstrap.password = ******* [edited]

[mqtt]
url = ic-sandbox.iotnonprod.bsci.com
port = 8883
tls = true
cert_auth = false
client_cert = /root/.cumulocity/certs/chain-cert.pem
client_key = /root/.cumulocity/certs/device-cert-private-key.pem
cacert = /etc/ssl/certs/ca-certificates.crt
ping.interval.seconds = 60

[agent]
name = DP-CUMUTest
type = c8y_dm_example_device
main.loop.interval.seconds = 10
requiredinterval = 10
loglevel = DEBUG
#device.id = DP-CUMUTest

Why did you dis comment the device.id? I’m not sure what’s happening then on windows. On unix the agent uses the hostname which does not exist on windows (@Stefan_Witschel ).

Could you also print the log in level debug?

I don’t recall doing that, but I uncommented the Device.id and that fixed the problem. The device is communicating now. Duh…

Thanks to everyone for their help! Sorry it was such as small issue.

No worry, that’s what this forum is all about :wink: