@pch : I have Ubuntu 16.04. The RPi hasn't been used for a while. I'll do a release upgrade and try again. Thanks

Hi, I'm running Indi server with Ubuntu 18.04 on a desktop PC. When I run sudo dpkg -i indi-mqtt_1.0.1_all.deb I get the following output ...
ray@indiastro:/shared$ sudo dpkg -i indi-mqtt_1.0.1_all.deb
(Reading database ... 133158 files and directories currently installed.)
Preparing to unpack indi-mqtt_1.0.1_all.deb ...
Removed /etc/systemd/system/multi-user.target.wants/indi-mqtt.service.
Unpacking indi-mqtt (1.0.1) over (1.0.0) ...
Setting up indi-mqtt (1.0.1) ...

Usage:
pip install [options] <requirement specifier> [package-index-options] ...
pip install [options] -r <requirements file> [package-index-options] ...
pip install [options] [-e] <vcs project url> ...
pip install [options] [-e] <local project path> ...
pip install [options] <archive url/path> ...

no such option: --no-warn-script-location
Created symlink /etc/systemd/system/multi-user.target.wants/indi-mqtt.service → /etc/systemd/system/indi-mqtt.service.

When I run indi-mqtt from the command line I get this ...

ray@indiastro:/shared$ sudo /usr/bin/indi-mqtt.py
INDI server localhost/7624 disconnected.
Traceback (most recent call last):
File "/usr/bin/indi-mqtt.py", line 315, in <module>
observatory_json = getJSON(devices)
File "/usr/bin/indi-mqtt.py", line 223, in getJSON
device_type = strDeviceType(device.getDriverInterface())
File "/usr/bin/indi-mqtt.py", line 146, in strDeviceType
if s & 0:
TypeError: unsupported operand type(s) for &: 'SwigPyObject' and 'int'
swig/python detected a memory leak of type 'uint16_t *', no destructor found.

I've also tried installing as per the instructions above provided by Kaczorek but I get the same error when run manually.

Any ideas please?

I have a Raspberry Pi 2B, so hardware may be part of the problem. Yesterday I couldn't even upgrade to ubuntu 18.04. Maybe time to upgrade to at least a 3B+, or even a Rock Pi.

@p1cass0, what version of pyindi-client you are running? you should run at least version 0.2.4

Check it with:
and if it is lower than 0.2.4, run

Can anyone confirm that mqtt-indi publisher is displaying the correct details for

1. Eq eod_cordinates

2. Time_utc

3.geographical _coords

mine isn't when displayed correctly (stuck not being updated) with MQTT-explorer Kstars on Ubuntu 18 and using an RPI 3b+ with Astroberry just running Simulator. Dates/Times are correct on RPI3b+ and Ubuntu 18.

Other details are being updated.

And no Radek I haven't updated MQTT Indi Client lately

restarted indiserver and now it seems all ok !!!!!!!!!!!!!!

I will do some more testing.

The only thing I could see was that the Virtual GPS wasn't running - so started it and reloaded indiserver !!!!!!!!!!!

Spoke too soon - Ground Hog Day - Equat_eod_coord same all the time, Time_UTC never changes.

GPS Panel (virtual GPS) time is being updated and correct. And is same as RPI3b+ time display.

strange ?

Let me guess... You mount is tracking?

Sometimes - but I am testing so I switch off the tracking and switch it back on again to see what happens .

No its the old story - Ekos displays the Coords in one format , MQtt displays it in the RAW format I guess - e.g. EKOS says 18h 03m 00s MQTT says 18.05 Ekos says DEC is 11 02 23 MQTT says 11.0399 - which most likely is the same if someone cares to convert it.


BUT the Time is wrong - never changes on MQTT - so there

And I updated to 2.4.0

OK MQTT displays the time as per Indi control panal "UTC" which isn't the "current time" just a way of starting the clock off manually - Yes ?

Enhancement - Why cant we see the time being used by Indiserver in real time (especially if its remote) subject to the poll delay- more use than a static time from Control Panel IMHO

All data are published to MQTT directly from indiserver with no processing whatsoever. It is not the function of indi-mqtt to process data, change format or do anything else than forwarding them via MQTT.
This is not time from control panel, it's exactly the time as indiserver keeps it (it used to update time every second, it doesn't now. I don't know why). You can easily verify this using indi_getprop - a native tool to read from indi server.

Thank Yo Kaczorek, I was running pyindi-client 0.2.3 after upgrading to 0.2.4 mqtt broadcast installs and runs as expected. Thanks again.