dzVents not working after upgrade from 11670 to 11724.  [Solved]

Easy to use, 100% Lua-based event scripting framework.

Moderator: leecollings

Post Reply
lepe
Posts: 7
Joined: Wednesday 17 May 2017 21:04
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

dzVents not working after upgrade from 11670 to 11724.

Post by lepe »

Hi all,

After upgrading from 11670 to 11724 dzVents doesn't work anymore. No logs, no actions. So dzVents scripts are ignored now.

Version: 4.11724
dzVents version: 3.0.0
Python Version 3.7.3 (default)
Raspbian 10 (buster)

i can see the domoticzData.lua and data folder is not updating anymore.

I already checked the comments from https://www.domoticz.com/forum/viewtopi ... 59&t=31404 but no solution. (cache clean, install to new domoticz folder, ...)

Any thoughts where to search/troubleshoot further?
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: dzVents not working after upgrade from 11670 to 11724.

Post by waaren »

lepe wrote: Tuesday 25 February 2020 21:29 Any thoughts where to search/troubleshoot further?
Assuming you already checked [setup][settings][other] tab to confirm EventSystem (Lua/Blockly/Scripts): and dzVents: are stil enabled
Can you share the first 30-40 of the log directly after starting domoticz ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
lepe
Posts: 7
Joined: Wednesday 17 May 2017 21:04
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: dzVents not working after upgrade from 11670 to 11724.

Post by lepe »

waaren wrote: Tuesday 25 February 2020 21:53
lepe wrote: Tuesday 25 February 2020 21:29 Any thoughts where to search/troubleshoot further?
Assuming you already checked [setup][settings][other] tab to confirm EventSystem (Lua/Blockly/Scripts): and dzVents: are stil enabled
Can you share the first 30-40 of the log directly after starting domoticz ?
Yes i checked those settings. These worked normally fine but no results in the logs about dzVents. This is longer going one there are no logs anymore... but the dzVents worked fine with previous versions... (i had to take care about the logging... but time was the issue)

About the logs... Not much for the moment. (used x for masking)
i'm aware there was in the past some dzVents information... but that's gone.

Code: Select all

2020-02-25 22:43:38.450  Sunrise: 07:34:00 SunSet: 18:14:00
2020-02-25 22:43:38.450  Day length: 10:39:00 Sun at south: 12:54:00
2020-02-25 22:43:38.450  Civil twilight start: 07:01:00 Civil twilight end: 18:47:00
2020-02-25 22:43:38.450  Nautical twilight start: 06:23:00 Nautical twilight end: 19:25:00
2020-02-25 22:43:38.450  Astronomical twilight start: 05:45:00 Astronomical twilight end: 20:03:00
2020-02-25 22:43:38.544  Active notification Subsystems: email, gcm, kodi, pushbullet (4/13)
2020-02-25 22:43:38.620  Starting shared server on: :::6144
2020-02-25 22:43:40.723  Kodi: (kodi master) Starting thread.
2020-02-25 22:43:40.823  Kodi: Starting I/O service thread.
2020-02-25 22:43:41.725  Kodi: (kodi master) Connected to 'x.x.x.x:9090'.
2020-02-25 22:43:42.127  MQTT: Topic: domoticz/in, Message: {"idx": xx, "nvalue": 0, "svalue": "0"}
2020-02-25 22:43:45.090  MQTT: Topic: domoticz/in, Message: {"idx": xx,"nvalue": 726}
2020-02-25 22:43:45.439  MQTT: Topic: domoticz/in, Message: {"idx": xx, "nvalue": 0, "svalue": "1"}
2020-02-25 22:43:46.259  (Xiaomi Gateway Central) Color Switch (Xiaomi RGB Gateway (x.x.x.x))
2020-02-25 22:43:46.315  (Xiaomi Gateway Central) Temp + Humidity + Baro (Xiaomi TempHumBaro)
...
2020-02-25 22:43:46.563  (Xiaomi Gateway Central) Temp + Humidity + Baro (x)
2020-02-25 22:43:46.614  (Zigbee2MQTT) Debug logging mask set to: PYTHON 
2020-02-25 22:43:46.615  (Zigbee2MQTT) onStart called
2020-02-25 22:43:46.615  (Zigbee2MQTT) MqttClient::__init__
2020-02-25 22:43:46.615  (Zigbee2MQTT) MqttClient::open
2020-02-25 22:43:46.693  (Zigbee2MQTT) onConnect called
2020-02-25 22:43:46.694  (Zigbee2MQTT) Connected to MQTT Server: 127.0.0.1:1883
2020-02-25 22:43:46.694  (Zigbee2MQTT) MQTT CLIENT ID: 'Domoticz_158266xxxx_xxx'
2020-02-25 22:43:46.694  (AC) MELCloud connection OK
thanks!
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: dzVents not working after upgrade from 11670 to 11724.

Post by waaren »

lepe wrote: Tuesday 25 February 2020 22:51
I don't see this one confirming the Eventsystem is active.

Code: Select all

2020-02-25 21:50:07.509  Status: EventSystem: reset all events...
Can yo try to disable the event System and dzVents and apply the settings and after that enable them again ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
lepe
Posts: 7
Joined: Wednesday 17 May 2017 21:04
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: dzVents not working after upgrade from 11670 to 11724.  [Solved]

Post by lepe »

waaren wrote: Tuesday 25 February 2020 23:03 Can yo try to disable the event System and dzVents and apply the settings and after that enable them again ?
yes, i've seen the issue now. Strange that i didn't noticed the entries of eventsystem earlier (This is because it's a 'status' line) It's the same issue off the missing logs...
I changed the domoticz.sh file with the following information (found on this forum):

Code: Select all

DAEMON_ARGS="$DAEMON_ARGS -loglevel normal, status, error"
but this didn't gave me the LOG results.
I changed this to:

Code: Select all

DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error"
(just removed the spaces) and the LOGS are populated fine now.

now i can see errors:

Code: Select all

Error: EventSystem: in /home/pi/domoticz/dzVents/runtime/dzVents.lua: /home/pi/domoticz/dzVents/runtime/EventHelpers.lua:644: attempt to concatenate a nil value (global 'moduleName')
I disabled a dzVents script and error is gone. Strange thing is that i use that script. I'll have to check that later (not important)

Strange thing is that dzVents works again now. (also with the 'defective' script enabled) Was timing an issue? just changing the loglevel cannot cause this? Maybe it's my environment specific.
Thanks for helping me in the right direction. (dzVents AND logging solved!)
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest