Domoticz

lonebaggie wrote: ↑Saturday 09 September 2017 11:24 puts some print commands to debug before you test values

val = devicechanged['Humidifier']
print ("Humidifier Value is " .. val)

check logs

Suspect you may need to test on level values

2017-09-09 12:29:58.876 dzVents: Humidifier Value is Medium
2017-09-09 12:29:58.878 (Humidifier) Light/Switch (Humidifier)
2017-09-09 12:30:00.611 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)
2017-09-09 12:30:00.616 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:4: attempt to index global 'devicechanged' (a nil value)
2017-09-09 12:30:03.147 User: Admin initiated a switch command (30/Humidifier/Set Level)
2017-09-09 12:30:03.383 dzVents: Humidifier Value is High
2017-09-09 12:30:03.385 (Humidifier) Light/Switch (Humidifier)
2017-09-09 12:30:13.954 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)
2017-09-09 12:30:14.077 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)
2017-09-09 12:30:27.925 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)
2017-09-09 12:30:28.047 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)
2017-09-09 12:30:30.535 Error: EventSystem: in Humidifier: [string "commandArray = {}..."]:5: attempt to concatenate global 'val' (a nil value)

jvdz wrote: ↑Saturday 09 September 2017 12:02 How did you implement this LUA script? When you used the internal editor, did you change the Event dropdown from All to Devices?
... else what did you name the script and where is it located?

Jos

jvandenbroek wrote: ↑Saturday 09 September 2017 12:44 It seems that dzVents log line is printed instead of Lua, which sometimes seem to occur for yet unknown reason (it's harmless). So the example/test script is working, it just tries to match on all device changes, which results in those nil value messages.

Try to add the full path to screen in os.execute, eg. /usr/bin/screen

Edit: But that wouldn't explain that it didn't return commandArray, sorry, that seems to be wrong. But if you don't get that message without the os.execute line, it seems that the script exits / disappears before completing, possible caused by screen. Could you try those lines just without using screen?

commandArray = {}

-- Humidifier

if devicechanged['Humidifier'] == 'Off' then
    os.execute ('bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 off')
end

if devicechanged['Humidifier'] == 'Silent' then
    os.execute ('bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on silent')
end

if devicechanged['Humidifier'] == 'Medium' then
    os.execute ('bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on medium')
end

if devicechanged['Humidifier'] == 'High' then
    os.execute ('bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on high')
end

return commandArray

jvandenbroek wrote: ↑Saturday 09 September 2017 13:58 What about /bin/bash? And the cannot open dzVents.lua error is suspicious, something seems wrong with your installation. Could try disabling dzVents under settings -> other, restart domoticz and see if at least that error message is gone?

jvandenbroek wrote: ↑Saturday 09 September 2017 14:29 You could try using those actions instead, but that doesn't explain why it's not working with Lua..

When using script:// you should set it like this: script:///bin/bash etc (triple / and full path to bash). It might work for you, because it calls the scripts without Lua involved.

If in doubt, I would move the current domoticz installation folder and conpletely re-install, because you shouldn't get that dzVents.lua not found message (the other error doesn't seem relevant in this matter). Just copy over domoticz.db afterwards to get your data back.

bigmak wrote:

jvandenbroek wrote: ↑Saturday 09 September 2017 14:29 You could try using those actions instead, but that doesn't explain why it's not working with Lua..

When using script:// you should set it like this: script:///bin/bash etc (triple / and full path to bash). It might work for you, because it calls the scripts without Lua involved.

If in doubt, I would move the current domoticz installation folder and conpletely re-install, because you shouldn't get that dzVents.lua not found message (the other error doesn't seem relevant in this matter). Just copy over domoticz.db afterwards to get your data back.

If dzVents - not a main problem - i will fix it after solving the problem with script.

Can you tell me - for Domoticz is it equal (1-3):
1. LUA script in folder ~/domoticz/scripts/lua...
2. Script in internal editor
3. Link in Scripts Action "script:///...'

?
Can I choose just one way (1-3)?

jvandenbroek wrote: ↑Saturday 09 September 2017 14:49
If in doubt, I would move the current domoticz installation folder and conpletely re-install, because you shouldn't get that dzVents.lua not found message (the other error doesn't seem relevant in this matter). Just copy over domoticz.db afterwards to get your data back.

2017-09-10 11:50:18.369 User: Admin initiated a switch command (30/Humidifier/Set Level)
2017-09-10 11:50:18.596 Executing script: /home/pi/domoticz/scripts/test_script.sh

jvandenbroek wrote: ↑Sunday 10 September 2017 16:38 You could try something simple like this, it should print the current date in /tmp/test.log:

Code: Select all

#!/bin/bash
echo $(date) > /tmp/test.log

jvandenbroek wrote: ↑Sunday 10 September 2017 16:38 If you update to the latest beta, the mix-up of dzVents / Lua lines showing up in the log should be solved (but that has nothing to do with your issue, just to make things less confusing)

bigmak wrote: ↑Monday 11 September 2017 9:18 I didn't catch the idea about "showing up in the log should be solved".
I updated to the v 3.8390 and what? Please, write a little bit more about it?

Thank you!

jvandenbroek wrote: ↑Monday 11 September 2017 11:31
Not sure why nothing happens, while executed manually it works fine.. Maybe you could try "script:///bin/bash -x /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on silent" and start Domoticz in a seperate terminal (just with ./domoticz instead of start-up script) to get a trace of what's executed, this might give you an idea where is goes wrong.

#!/bin/sh

# Humidifier
# Set Power off
sudo /home/pi/.nvm/versions/node/v6.0.0/bin/node /home/pi/Xiaomi/humidifier.js 192.168.1.40 power off /dev/null

exit 0

jvandenbroek wrote: ↑Monday 11 September 2017 12:04 Ah interesting, thanks for letting us know! I think the full paths to both node and js file would be sufficient? Or is it really necessary to use sh?

commandArray = {}

-- Humidifier

if devicechanged['Humidifier'] == 'Silent' then
    os.execute ('sudo screen -S humidifiertemp -d -m /bin/bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on silent')
end

if devicechanged['Humidifier'] == 'Medium' then
    os.execute ('sudo screen -S humidifiertemp -d -m /bin/bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on medium')
end

if devicechanged['Humidifier'] == 'High' then
    os.execute ('sudo screen -S humidifiertemp -d -m /bin/bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 on high')
end

if devicechanged['Humidifier'] == 'Off' then
    os.execute ('sudo screen -S humidifiertemp -d -m /bin/bash /home/pi/domoticz/scripts/humidifiercontrol.sh 192.168.1.40 off /dev/null')
end

return commandArray