I have been playing with PyIndiClient and not having much luck.

Is it supported currently? I see last checkin was three weeks ago

It seems to not compile under Python2.7 - ok
After compiling under 3.7
Trying to run the example:
Starting here:
github.com/indilib/pyindi-client/blob/ma...es/testindiclient.py

I get (end of log output):
List of Device Properties
-- Telescope Simulator
Traceback (most recent call last):
  File "./tme1.py", line 82, in <module>
    for p in lp:
TypeError: 'SwigPyObject' object is not iterable

And trying  to run the example here:
github.com/indilib/pyindi-client

Fails on any and all 'decode's
    self.logger.info("new Text "+ tvp.name.decode() + " for device "+ tvp.device.decode())
AttributeError: 'str' object has no attribute 'decode'

Just a 'bad' libindiclient (using 1.9.3 and also a real old one I have around)

Thanks for your time!

Gene



Gene
 

The example code is written for Python 2 and is out of date.

Try this:

The example code is written for Python 2 and is out of date.

Try this:

<code>
self.logger.info("new Text "+ tvp.getName() + " for device "+ tvp.getDeviceName())
</code>

The example code is written for Python 2 and is out of date.

Try this:

self.logger.info("new Text "+ tvp.getName() + " for device "+ tvp.getDeviceName())
 

The example code is written for Python 2 and is out of date.

Try this:

self.logger.info("new Text "+ tvp.getName() + " for device "+ tvp.getDeviceName())
 

The example code is written for Python 2 and is out of date.

Try this:

self.logger.info("new Text "+ tvp.getName() + " for device "+ tvp.getDeviceName())
 

The example code is written for Python 2 and is out of date.

 

Sorry, the forum was returning an error when I was replying. I did not know it was actually posting my messages.

Thanks Aaron,

Classic issue with opensource, things are abandoned or only partially followed through as time moves forward.

I missed the first error you posted about "TypeError: 'SwigPyObject' object is not iterable."

There is actually an issue open right now on this problem. It seems to be one of the last outstanding bugs for full INDI 1.9 compatibility.
github.com/indilib/pyindi-client/issues/4

Otherwise, pyindi is fully functional. I use it extensively in my allsky camera software: github.com/aaronwmorris/indi-allsky