How to put a date variable in config file?

[eMindFfM]

Hi all,
I'm using the MPI 5K and IOBroker to monitor it. So I'm looking for an option to put the date variable into the config in order to get kW per day displayed in the monitoring. So far I tried the following in the mppsolar.conf file:
#command=ED20221006
command=ED%(date +"%Y%m%d")

But It does not work. Any hints?
Best Regards

[jblance]

there isnt a way at the moment.
others are using a shell script for this - bit of a cludge, but I need to change the internal workings to make this work properly (its in my todo)

[Saentist]

On my inverter command is:
DAT221208212837
aka
2022-12-08 21:28:59

[Saentist]

Bash script

adapt for your needs

#bash
getdate=DAT$(date '+%Y%m%d%H%M%S')
echo "$getdate"
echo executing 
echo mpp-solar -p /dev/hidraw2 -o screen -c "$getdate"
mpp-solar -p /dev/hidraw2 -o screen -c "$getdate"

[jblance]

Sneak preview...
powermon is new (very alpha) command in mpp-solar package
it uses a yaml config file like

device:
  name: Test_Inverter
  id: 123456789
  model: 8048MAX
  manufacturer: MPP-Solar
  port:
    baud: 2400
    path: /dev/ttyUSB0
    type: test
    protocol: PI30MAX
  commands:
  - command: QED
    # f_command: f'QED{(date.today()-timedelta(days=1)).strftime("%Y%m%d")}'
    f_command: f'QED{(date.today()).strftime("%Y%m%d")}'
    outputs:
    - name: screen
      tag: Test_Inverter
      filter: ^pv

and this yaml supports a formatting command as shown
powermon service also listens to commands and runs them

still a few key design pieces to sort out so I dont recommend using it yet (yaml format is changing and only supports serial connections atm) however I am using on my install for production monitoring

[RoySalisbury]

I saw this mentioned in another discussion so figured I would check it out (yes, I am aware its not ready for prime time).

Anyway, I ran it using the sample yaml file and can understand the direction your going. Is the hassd_mqtt output provider working yet? I can get screen, but none of the others (module not found).

[jblance]

It was in at least one version. Currently broken again as I'm working on which approach to take for outputs. Ie hassd_mqtt is just sending via mqtt but has a different message format, so I'm working on splitting the format of the message and the sending mechanism. Sounds easy but there's still a lot of overlap and last attempt I tied myself in knots

…

On Tue, 28 Feb 2023, 3:25 pm Roy Salisbury, ***@***.***> wrote: I saw this mentioned in another discussion so figured I would check it out (yes, I am aware its not ready for prime time). Anyway, I ran it using the sample yaml file and can understand the direction your going. Is the hassd_mqtt output provider working yet? I can get screen, but none of the others (module not found). — Reply to this email directly, view it on GitHub <#264 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVKNQOCSPD6KJRI7WSE5LWZVOZTANCNFSM6AAAAAAQ7BDULU> . You are receiving this because you commented.Message ID: ***@***.***>

[RoySalisbury]

ok.. I'll keep an eye out for updates.

Thanks