Domoticz

boum

first fix the basic error between execute = function(dz, devices) and local kpmtt = domoticz.devices('Tot_Fornuis') -- Tot_Fornuis is a dummy. But .usage or .actualWatt doesn´t work ! use either domoticz or dz everywhere but not a mix then follow the advice and find the type of the device to ...

boum

the globalData table is the table set as `data` in your lua file. Move your constants table there (with `lastStateUserGPS`)
or put your PUSHOVER table inside helpers and access it with `domoticz.helpers.PUSHOVER.USERS.FAMILIE`

boum

check device name :
- is it unique? (did you rename the old switch with the ozw hardware?)
- check capitalization and trailing spaces too

boum

your skeleton function only initialize the first local variables, all other are nil.

Code: Select all

function ExtractElectrics(dev_switch, dev_volt, dev_watt, dev_kwh)
    local switch, volt, watt, kwh = "a", "b", "c", "d"
    return switch, volt, watt, kwh
end

boum

andrehj wrote: But how can one compare two time objects named for instance "Time1" and "Time2"?

have you just tried:

Code: Select all

    -- compare two times
    print(Time1.compare(Time2).minutes)

boum

add a `customEvents` trigger to your script. On V4 trigger, set a persistent data, user variable or dummy switch to ON. Then call `domoticz.emitEvent(custom_trigger_name).afterSec(0.5)` to reenter your sript later. On custom event, check your dummy/variable, if still on, change level on your bulb ...

boum

you should share both scripts. not much can be done without that (you explained the issue well, but i don't think anybody will look at the issue with just that)

boum

this have been told several time. changes to device states (and probably user variables) are done after the script execution. (that's a good way to avoid infinite loops by the way) during the execution of the script the states are fixed. if you want to track your changes for later use in the same ...

boum

Your use of math.randomseed seems… random. It might overflow integer value and result in a no-op. Or the same value rounded every time so same sequence of generated numbers. Ideally, you should use math.randomseed(os.time()) only once before the whole disco commands. Also lots of redundancy in your c ...

boum

https://www.lua.org/pil/22.2.html

Code: Select all

print(os.getenv("HOME"))

boum

dzVents is a Lua API to domoticz (as explained in the wiki introduction) the wiki is there to explain the API and domoticz specifics, not Lua syntax. if you want to learn Lua, you can find lots of web resources, but first there is https://www.lua.org/pil/contents.html as a good starting point (maybe ...

boum

Maybe newly created devices are not “yet” available in dzVents. It might be a bug. You can try to either restart domoticz or disable/reenable scripts/dzvents in Parameters.

boum

I think Nest API stopped to work a few years ago when it was bought by Google. If there is a new API, nobody did port it to the domoticz plugin.

boum

I'd do something like that: local PIR = { ["Body Sensor Scala"] = {"switch1","switch2"}, ["Body Sensor Camera"] = {"switch3","switch4"}, ["Body Sensor Bagno"] = {"switch5","switch6"}, ["Body Sensor Cucina"] = {"switch7","switch8"}, ["Body Sensor Sottotetto"] = {"switch9","switch10"}, } -- test ...

boum

Code: Select all

if (deviceName in pairs(switches)) then

this is not valid lua syntax.

boum

In your mosquitto directory, the docker compose file should be completely different and should look like
https://github.com/vvatelot/mosquitto-d ... mpose.yaml

boum

so in short: if you cant use /dev/serial/by-id you are screwed and cant use the zwave anymore?? You can still use default devices names (could change if you plug something more and reboot) or use persistent usb devices, https://www.domoticz.com/wiki/PersistentUSBDevices if zwave is so hard to use ...

boum

remko2000 wrote: ↑Friday 05 January 2024 11:13 Tried it and fill ' /dev/serial/by-id/usb-0658_0200-if00' in in the zwave js ui. Still the same error.............

/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave should be in your docker compose file in the ports section
/dev/zwave should be in you zwave js ui

boum

also not sure about your MQTT server. It should have its docker compose file in its own directory (if you go that way like described in the wiki).
those are 2 different docker images

boum

in the field “Serial Port” of your zwave JS (the one on port 8091/#/settings), there you should only put ”/dev/zwave”
the docker compose file tells to map external (out of docker) usb device by ID to internal (where zwave js runs) /dev/zwave

Search found 129 matches

Re: Something stupid , a dummy problem "actualWatt"

Re: global_data creating global constants

Re: Fibaro Double Switch 2 don't trigger Script

Re: return multiple values from function

Re: compare time from fixing time..

Re: Ikea Remote N2 dimming in DzVents

Re: DZvents bug in handling httpResponses?

Re: invalid device active state after switchOn or switchOff

Re: math.rand gives same results

Re: reading environment variables

Re: dzvents wiki

Re: Get rid of 'Couldn't connect to server' in log when httpResponses server is down

Re: Nest integration

Re: Help on a script involving .filter() or ipairs()

Re: help with possible script

Re: Z-wave JS UI failed to open serial port

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Z-wave JS UI failed to open serial port

Re: Z-wave JS UI failed to open serial port

Re: Z-wave JS UI failed to open serial port