Domoticz

Hello,

add "1/" in parameter(s)

Having the same issue, strangely tho was that the scripts did work. If i call them directly in terminal the script (sending a snapshot to my telegram) works flawlessly but when i true to call the script through domoticz nothing happens. I did try changing the url, adding "1/" in the parameters even the space after the script text area. After adding the space or changing the url i get no error msgs but i don't get the script to run

I am running the latest (beta)version 3.9052 but come to think of it i did have it before that build (not sure which one).

Laulo7 wrote: ↑Sunday 18 March 2018 14:46 Hello,

add "1/" in parameter(s)

Why ? where are you referring to ? To remove # ?

If you run the whole path the backspace isn't needed mine is in /home/pi/domoticz/scripts/bash/ and specify it like that and i have no #.

Strange problem with my problem is that the script seems to work partially, since the snapshot is uploaded to the directory which is specified in the script, i how ever don't get a msg via telegram (it does so when i locally call the script)

Did you ever get this resolved? I have the same issue. Adding "1/" as a parameter does not help for me.

I'm in the same situation:

Spoiler: show

2018-08-27 12:54:56.672 Status: Executing script: /usr/local/domoticz/var/scripts/tv_alert.sh#
2018-08-27 12:54:56.682 Error: Error executing script command (/usr/local/domoticz/var/scripts/tv_alert.sh#). returned: 32512

The script runs perfectly from CLI.

For workaround, i add a blankspace and ampersand to send the job to background and it seems to work.
Status: Executing script: /usr/local/domoticz/var/scripts/tv_alert.sh &#

Any advances?

Hi guys,

i know this topic is very old but i was also struggeling with this issue and found no solution in the forums.

But I could now figuere out when this problem happen:
It happens ONLY if there are more then the "start script" action in the doing.

Example:

If a Blockly Script looks like this (only the Start Script action is selected, it will work:
If there are other actions in the "Do" section, Domoticz will tail the # after the script:

My Workaround: - "SOLUTION"
I Create a Dummy-Item (Push On Button) and added my script to the "action at on" field.
In the Blockly Script i will just set this dummy button to ON - then the Script will be executed.

I hope this can help other people with the same Issue.

Thanks to all of you bringing up this problem!
And of course I realize that this is an old topic but anyway I would like to contribute to this problem and possible solutions.

I ran into the same problem (the logfile says: " Error: Error executing script command (/home/pi/domoticz/scripts/buzzer.py#). returned: 32512").
In addition to the solution of @dakarli I found out that just adding a space right after the name of the script (in my case /home/pi/domoticz/scripts/buzzer.py solves my problem.
[Edit] It looks to me like a parsing problem.
Even if you are running more than one script, just add a space after the name of the script and it works as expected. There is no need for an ampersand (&).
I'll hope anyone will benefit of this.

Thanks to the update to V2022.1 the parsing problem is gone!
So if you encounter the problem as described I suggest update Domoticz to V2022.1.

Thank you Gizmocus!

I have this problem V2022.2 still.

Weirdly I have two scripts and one works fine and the other gets the # added on the end and fails.

The only difference in the text is one ends in off.sh and works fine and the other ends in on.sh and gets the # added. I've tried removing and re-adding the broken one but it didn't help. Adding a space as a workaround works but the # is still appended so it doesn't seem to be related to the length of the text as with the space added they would be the same length.