I think I've found a bug in the installation script (http://razberry.z-wave.me/install).
I updated to the new version 2.3.5 and I was wondering why the scripts no longer worked in different modules.
The problem was that the file '/opt/z-way-server/automation/.syscommands' is not backuped, because in line 161 and 163 of the script the file '.../automation/.syscommand' is not found, because an 's' is missing at the end.
(Correct me if I am wrong.)
After upgrading I can no longer select US radio frequency for chipset... It will only allow me to set EU/RU/IN/CN regions...
Can I set operating frequency in a config file somewhere? None of my devices will talk to it now that I cannot set the correct frequency..
Please go to Network -> Controller Info and press Debug. After this you will be able to select all frequencies including US.
We have fixed this for next versions to restore the original frequency after upgrade.
Well I feel dumber than ever. I tried to be clever instead of waiting for your reply, and ran changezwf.sh /dev/ttyS0 US.
This bricks the RaZberry (I bet you knew that). I can still see /dev/ttyS0, but zwave software cannot see the RaZberry. Switching back to EU with same command does not either (I bet you knew that too). expert UI gives warnings about a binding error, and displays no information in the controller info screen except UI version.
Did I kill it completely? or is there something I can do to bring it back to life?
I submit my stupidity as a warning to others, so that they might not repeat my mistake.
So I wrote that data to something entirely different. Not making myself look great here.
Let me reformat the whole Pi and get back to you with more information if I'm still having problems that aren't my fault.
Can you please do IP:8083/JS/Run/zway.ZMEFreqChange(3) ? Or send me via PM your remote access credentials and I'll check what is wrong in the UI
That did the trick. I was wondering about sending commands to it this way, but It did not click in my head until I saw this example. I was expecting it to be more difficult. Thanks for all of your hard work!
Ok. Everything is functioning correctly now, but Z-way-server 2.3.5 does seem to crash after a period of time somewhere between a couple of days and a couple of hours.
I've got 12 devices on my network, little to no packet loss. When I rebuilt my network, i enabled security on all of the devices I could.
between the old version and 2.3.5, z-way-server seems to be slower to respond in terms of the amount of time it takes to load and render menus and such. I also notice that there tend to be jobs waiting in the queue more frequently. I'm assuming that is just because I've enabled security though.
I'm collecting log files right now. I'll upload them when I can get z-way-server to crash...
Edit: what do you know, I've already got a log file for you. It's to large to attach to the post. Where should I send it?
Last edited by wavedoff on 24 Aug 2017 04:56, edited 1 time in total.