Dear all,
I read through several posts but am still unsure if there is a remaining issue to send the Park/Unpark command in Indi (indi_setprop). I am aware there are several posts having issues with iOptron - but I can confirm my CEM60 behaves perfect to Park/Unpark using Ekos Indi Control Center when connecting to the remote telescope or using the hand controller....

-> When executing “Park” in the telescope HC the telescope slews to the horizontal park position (west)
-> When executing “Park” in Ekos the telescope slews to the horizontal park position as expected
-> When sending “indi_setprop -h 192.168.178.106 iEQ.TELESCOPE_PARK.PARK=On” it does park somewhere 45 deg east in RA from home position...

My initial intent is to write a script (Python, NodeJS, bash...) executing the park command behaving as if executed by Ekos or the HC. Of course a better understanding by learning what I do/understand wrong for future projects are highly welcome!

Thank’s for your feedback,
Frank

Hello, I've done a similar test on my CEM25p, I can connect to the mount, unpark it, send it to the home position and park it again without any issues.
My mount park position is weight bar horizontal.indi_setprop iEQ.CONNECTION.CONNECT=On
indi_setprop iEQ.TELESCOPE_PARK.UNPARK=On
indi_setprop iEQ.HOME.IEQ_GOTO_HOME=On
indi_setprop iEQ.TELESCOPE_PARK.PARK=On
indi_setprop iEQ.CONNECTION.DISCONNECT=On

Ok, Just in case I will try an see if ti makes any difference if I do "connect=ON" before... but I think this is not required as the telescope will already be connected in ASIAIR. Just have to wait until it stops raining to open the roof.

In the meantime I did extract the TCP stream sent from Ekos INDI Control Panel to INDI Server when parking the mount as I would like to do using indi_setprop!

The first "PARK" command is in #215 (see attachement)
<newSwitchVector name='TELESCOPE_PARK'>
  <oneSwitch
    name='PARK'>
      On
  </oneSwitch>
</newSwitchVector>

And the confirmation in #258
<message device="iEQ" timestamp="2021-04-09T12:37:59" message="[DEBUG] Parking to Az ( 0:00:00) Alt (49:01:00)..."/>

My plan would be to do the same traffic capture when issuing "PARK=On" when using indi_setprop to hopefully understand better what makes the difference in the scenario... 

Connection:
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep -i ".connect="
iEQ.CONNECTION.CONNECT=Off
iEQ.CONNECTION.DISCONNECT=On
root@heidenrod-obs:~# indi_setprop iEQ.CONNECTION.CONNECT=On
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep -i ".connect="
iEQ.CONNECTION.CONNECT=On
iEQ.CONNECTION.DISCONNECT=Off
root@heidenrod-obs:~# 


Check current park position:
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep PARK_POSITION.PARK
iEQ.TELESCOPE_PARK_POSITION.PARK_AZ=339.04244699999998147
iEQ.TELESCOPE_PARK_POSITION.PARK_ALT=9.4718499999999998806
root@heidenrod-obs:~# 


Un-parking and set to home position (weight down):
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "PARK="
iEQ.TELESCOPE_PARK.PARK=On
iEQ.TELESCOPE_PARK.UNPARK=Off
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "EOD_COORD."
iEQ.EQUATORIAL_EOD_COORD.RA=0.16243888888888888267
iEQ.EQUATORIAL_EOD_COORD.DEC=45.794580555555555179
root@heidenrod-obs:~# indi_setprop iEQ.TELESCOPE_PARK.UNPARK=On
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "PARK="
iEQ.TELESCOPE_PARK.PARK=Off
iEQ.TELESCOPE_PARK.UNPARK=On
root@heidenrod-obs:~# indi_setprop iEQ.HOME.IEQ_GOTO_HOME=On
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "EOD_COORD."
iEQ.EQUATORIAL_EOD_COORD.RA=18.652088888888890494
iEQ.EQUATORIAL_EOD_COORD.DEC=90
root@heidenrod-obs:~#


Park and check coord:
root@heidenrod-obs:~# indi_setprop iEQ.TELESCOPE_PARK.PARK=On
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "PARK="
iEQ.TELESCOPE_PARK.PARK=On
iEQ.TELESCOPE_PARK.UNPARK=Off
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "EOD_COORD."
iEQ.EQUATORIAL_EOD_COORD.RA=0.24518333333333333646
iEQ.EQUATORIAL_EOD_COORD.DEC=45.794580555555555179


Ran the test another time:
You get a slighlty different RA value but nothing to be concerned off
root@heidenrod-obs:~# indi_setprop iEQ.TELESCOPE_PARK.UNPARK=On
root@heidenrod-obs:~# indi_setprop iEQ.HOME.IEQ_GOTO_HOME=On
root@heidenrod-obs:~# indi_setprop iEQ.TELESCOPE_PARK.PARK=On
root@heidenrod-obs:~# indi_getprop | grep iEQ | grep "EOD_COORD."
iEQ.EQUATORIAL_EOD_COORD.RA=0.27026944444444445104
iEQ.EQUATORIAL_EOD_COORD.DEC=45.794580555555555179

forgot the park position after testing:

root@heidenrod-obs:~# indi_getprop | grep iEQ | grep PARK_POSITION.PARK
iEQ.TELESCOPE_PARK_POSITION.PARK_AZ=339.04244699999998147
iEQ.TELESCOPE_PARK_POSITION.PARK_ALT=9.4718499999999998806
root@heidenrod-obs:~#

Yes, we are connected...
pi@raspberrypi:~ $ indi_getprop -h 192.168.178.106 | grep iEQ | grep -i ".connect="
iEQ.CONNECTION.CONNECT=On
iEQ.CONNECTION.DISCONNECT=Off

The park position defined in the HC...
pi@raspberrypi:~ $ indi_getprop -h 192.168.178.106 | grep iEQ | grep PARK_POSITION.PARK
iEQ.TELESCOPE_PARK_POSITION.PARK_AZ=0
iEQ.TELESCOPE_PARK_POSITION.PARK_ALT=49.016700000000000159

We are currently not parked...
pi@raspberrypi:~ $ indi_getprop -h 192.168.178.106 | grep iEQ | grep "PARK="
iEQ.TELESCOPE_PARK.PARK=Off
iEQ.TELESCOPE_PARK.UNPARK=On

Park NOW...
pi@raspberrypi:~ $ indi_setprop -h 192.168.178.106 iEQ.TELESCOPE_PARK.PARK=On

Park position reached...
pi@raspberrypi:~ $ indi_getprop -h 192.168.178.106 | grep iEQ | grep "EOD_COORD."
iEQ.EQUATORIAL_EOD_COORD.RA=17.261250000000000426
iEQ.EQUATORIAL_EOD_COORD.DEC=41.424172222222225059

I think it get's a little bit weird since the telescope will first slew EAST before going to it's defined park position (HORIZON WEST).
Not sure if the device acting as INDI Server is causing issues - I can only see Ekos/KStars plays more nicely with the device than my current INDI Lib.

I will need to evaluate what solution might be the best for me to ensure 100% the telescope is in the expected position...

Only once I saw my CEM25p park in the opposite direction. Apart from that, it's been rock solid. From command line or from Ekos.