Regarding the HTTPGet module (aka app) causing Z-Way to crash...
As written by the author, the HTTPGet module sends an HTTP request whenever there's a change of value in any Z-Wave device. In my Z-Wave network, the module's simplistic logic caused a large number of HTTP requests to be sent. If you have a "busy" Z-Wave network (e.g., lots of devices changing values), the HTTPGet module may be the culprit for Z-Way crashing. Keep in mind, even if you don't have many Z-Wave devices, some Z-Wave devices can be very chatty (e.g., my dimmer switches rapidly send multiple Switch Multilevel Report messages as the brightness changes).
To reduce the number of HTTP requests being sent by the HTTPGet module, I modified the module's index.js file to limit which devices will trigger the HTTP request (to binary and multilevel switches).
Code: Select all
In file /opt/z-way-server/automation/userModules/HTTPGet/index.js, I modified the following:
From:
self.get_url(device, value);
To:
if (device.get("deviceType") == "switchBinary" || device.get("deviceType") == "switchMultilevel") {
self.get_url(device, value);
}
If you only want to send an HTTP request when a specific device changes value, you could modify index.js to check the device.id value (e.g., if (device.id == "[Zway Device ID]") { ... }).
Note that for Z-Way to use the modified index.js, you'll need to either restart z-way-server or reinitialize the module (curl -s -u [USERNAME]:[PASSWD] --globoff '127.0.0.1:8083/ZAutomation/api/v1/modules/reinitialize/HTTPGet).
It will be interested to learn if modifying index.js prevents Z-Way from crashing on your system. If so, the module's logic could be enhanced to have the user configure which devices (or device types) should trigger the HTTP request.