forum

It looks like problems with serial port /dev/ttyAMA0 are being reported by multiple users. From my experience with bookworm OS, Z-Way's installation script (called RaspbianInstall) needs to be updated. Here are the issues I've encountered with the installation script for the 32-bit lite version of b...

Have you considered downloading Z-Way's SD card image from here: https://z-wave.me/z-way/download-z-way/? If your Raspberry Pi using Z-Way's SD card image works correctly, then you've isolated the problem to not be a hardware issue. The approach you've taken of installing Raspberry Pi OS using rpi-i...

It sounds like you have a complicated configuration. You may want to use the Easy Scripting app instead of adding your own bindings. This is a very useful app for creating complicated rules in JavaScript. Assuming your heater is a virtual device within Z-Way, you could have Easy Scripting logic that...

The logs you provided show 2 different issues. For the issue related to RaZberry PRO 7 reliability, follow the instructions in this post: https://forum.z-wave.me/viewtopic.php?p=98974#p98974 For the issue related to JavaScript errors ("at automation/ userModules /SwitchPollingSelect/index.js:60...

You are correct, a device created using the "Dummy Device" app has very limited functionality. It will not do what you want. A binary switch created using the “Virtual Device (JavaScript)” app will do what you want. Here's a screenshot that shows you how to create a binary switch using the...

PoltoS wrote: Thanks to @aLiEnHeAd, let's add a few more:

The HTTP Device app index.js sets async=true. This is not configurable from the app's web UI.

Parser for on/off status: JSON.stringify($$).split('"')[3] === 'ON' ? 'on' : 'off'

Please help us to collect more info: users who do and don't experience it, what are your HTTP requests: - I do / don't experience the issue - IP or DNS - HTTP / HTTPS / WS / WSS - to a service at localhost, LAN, Internet I do experience the issue, URL uses DNS, request is HTTP GET with no auth, LAN...

Now I have a question of understanding: do you think, that the http.request() command is buggy? Yes. The code for http.request() is in /opt/z-way-server/modules/modhttp.so. Since it is compiled code and Z-Wave.Me has not made the source code available on github (see: https://github.com/Z-Wave-Me), ...

Eureka! Based on the information provided by @aLiEnHeAd, I replaced the HTTP devices with instances of the app called "Virtual Device (JavaScript)". As a result, the z-way-server process on my Raspberry Pi has a CPU load of 4% instead of 12%. Here's what I did: 1. Added the following line ...

You can also use the top command to see similar info, as follows: $ top -b -n 1 -H -p `pidof z-way-server` top - 17:11:34 up 36 days, 5:27, 1 user, load average: 0.13, 0.11, 0.09 Threads: 10 total, 0 running, 10 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.2 us, 0.0 sy, 0.0 ni, 96.8 id, 0.0 wa, 0.0 hi, ...