When you upgrade your z-way server, you may find that your temp changed from Fahrenheit to Celsius(default). I addressed this on page 2 of this thread so I’ll briefly mention it here.
/opt/z-way-server/config/Defaults.xml
<CommandClass><!-- Default CC settings for devices -->
<Wakeup>
<WakeupInterval>3600</WakeupInterval><!-- Default Wakeup Interval to set during AutoConfiguration. Value 0 means to use default value from the device -->
</Wakeup>
<SceneActuatorConf>
<MaxScenes>16</MaxScenes><!-- Maximum number of scenes to use -->
</SceneActuatorConf>
<SceneControllerConf>
<MaxScenes>16</MaxScenes><!-- Maximum number of scenes to use -->
</SceneControllerConf>
<Protection>
<Mode>0</Mode><!-- Default Protection Mode to set during AutoConfiguration -->
</Protection>
<SensorMultilevel>
<Fahrenheit>1</Fahrenheit><!-- Default scale to use -->
</SensorMultilevel>
<ThermostatSetPoint>
<Fahrenheit>1</Fahrenheit><!-- Default scale to use -->
</ThermostatSetPoint>
<SwitchAll>
<Mode>0</Mode><!-- Default SwichAll Mode to set during AutoConfiguration -->
</SwitchAll>
<MultiCmd>
<MaxNum>3</MaxNum><!-- Maximum number of commands per MultiCmd -->
</MultiCmd>
<FirmwareUpdate>
<FragmentSize>32</FragmentSize><!-- Fragment size on 3rd gen RaZberry and Z-Stick can not be more than 32 (max packet size was 37, with possible CRC it gives 32). On UZB and new 5gen it can be up to 40 bytes -->
</FirmwareUpdate>
</CommandClass>
After making the change, make sure to stop and start the z-way server…
sudo /etc/init.d/z-way-server stop
and
sudo /etc/init.d/z-way-server start
When using any of the below devices, it’s necessary to install the Niffler module. Here is the author’s thread: [url=https://forum.z-wave.me/viewtopic.php?f=3424&t=21688][userModule] Niffler - An event notification updater - forum
These devices can be controlled via z-way but when using the physical device, updates aren’t reflected. This application alleviates this issue all together. I’ll provide more detailed instructions on how to load the module and perform a setup and selection of devices.
[1] Any GE/Jasco product. This currently includes in-wall dimmers(e.g. light and fan) and binary switches.
[2] Yale (Real Living Cap-Touch Lever Lock).
–
Edit: Does not support the following:
[1] GE/Jasco Add-on switch.
Niffler is a great app and it works to keep not only the GE switches and receptacles updated, it also catches the door locks. Not perfect and not instant, but effective…
Yes, I see that PoltoS just recently reached out to the author to add native support within z-way but there’s been no response just yet. It’s definitely a great app to have as it solved all my issues and I’ve not noticed a lag (knock on wood).
Just added: Jasco Switch (on/off only). Nothing too exciting here, although the routing table is much improved. This is running z-way server 2.2.3 ATM. I was able to exclude/include this switch without any issues even though this switch is in the garage (along with the z-wave GDO).
Yes, this product really loves it when you have a lot of routing devices on mains. This has alleviated almost all of my earlier issues with lack of communication. I’m looking forward to their latest release for test. z-way seems very interested in getting issues resolved as quickly as possible, this is obvious with the number of release candidates they provide to the public for testing.
Doing a major bathroom renovation here in the next couple of months, figured it would be useful behind a shower wall (accessible from the closet area) to control a Sonos system
Yes, I’m hoping this is a simple load and go BUT there isn’t a single post on the z-way forum. Their web site indicates support, but only for 4 scenes. I seem to have lost two along the way. I’ll have to see if I can find out why the limit is 4 rather than the provided 6.
Adding RazBerry board #2 to second test device - a Raspberry Pi 3. Per dsroberts1945 (karma to you), who posted way back on this thread. I used the link provided to prep the Pi3. A key to identifying that you’ve failed to disable Bluetooth (or perhaps a more serious issue), is checking [ip]:8083/smarthome/#/events for the following error, “Cannot start Z-Wave binding: Error: Bad data - communication failed”.
Apparently the new BT port is blocking TTY communications on the PI3B. The temporary workaround is:
Update Raspbian to the latest:
sudo apt-get update
sudo apt-get upgrade
Update RPI3B firmware to the latest:
sudo apt-get install rpi-update
sudo rpi-update
After this: REBOOT
Disable BT on RPI3B:
Open the /boot/config.txt
sudo nano /boot/config.txt
At the end add the line:
dtoverlay=pi3-disable-bt
exit with ctrl-X, select Yes
After this: REBOOT
set the correct baudrate:
stty -F /dev/ttyAMA0 9600
Upgrade the firmware within [ip]:8083/expert/#/uzb
2015-09-18 5.0 Update firmware from 05.00 to 05.03 Upgrade firmware
2018-09-15 5.0 Update firmware from 05.00 to 05.04
And the bootloader within [ip]:8083/expert/#/uzb:
2015-01-01 5.0 Update bootloader from default for 05.00 to 538d Upgrade bootloader
No need to boot between the upgrades, I then poweroff the unit, wait - then power back on…
Important:
DO NOT forget to change your ‘Current frequency’ within [ip].8083/expert/#/network/control as it will default to ‘EU’.
Just added [RaZberry Pi3]: 2gig CT100 by Radio Thermostat Company of America (RTC).
RTCA Thermostat operation (2.0)
Element ID: ZWayVDev_zway_2-0-64
RTCA Thermostat Heat (2.0)
Element ID: ZWayVDev_zway_2-0-67-1
RTCA Thermostat Cool (2.0)
Element ID: ZWayVDev_zway_2-0-67-2
RTCA Temperature (2.1.49.1)
Element ID: ZWayVDev_zway_2-1-49-1
RTCA Humidity (2.2.49.5)
Element ID: ZWayVDev_zway_2-2-49-5
RTCA Temperature (2.0.49.1)
Element ID: ZWayVDev_zway_2-0-49-1
Just added (Razberry Pi2]: Fibaro Swipe FGGC-001. This is going to be fun. I have to generate the sequences and store them as a parameter to the device. Once the gesture(s) are observed, it triggers a scene ID to the controller. I’ll have to figure this one out and write up a how-to. For now though, here’s the information I currently have. I assume a widget won’t be created until a gesture slot is defined. Inclusion was very simple and z-way detected and selected the Fibaro Swipe configuration for me (nice).
Learning a new sequence:
To perform automatic learning of a sequence:
1. Change value of parameter 30 to number of sequence slot you want to fill (1 to 6).
2. Wake up the device using 1st menu position (see "Operating the device" on page 10)
3. The device will enter learning mode, which is signalled by constant beeping.
4. Perform a desired sequence.
Is there any chance this might work with a Raspberry Pi with the UZB instead of the GPIO plug in card? I would like to eventually to try to run this on a processor system that is not the Raspberry Pi, so the USB based controller is desirable.
And if this is possible, does anyone know if the Z-way license from zwave.me is needed? The zwave.me forum comparing the UZB with the RaZberry mentions a license “UZB1 does support Security, MultiCommand and everything else if you have the appropriate license installed.” It’s unclear to me if this license is needed or not for the openLuup support. Probably yes, but I wonder if anyone has tried it?
Yes, it should work with a UZB. Yes you’d need to licence the stick. This makes it quite a lot more expensive that the Razberry board, but it does mean that you can run it on any processor system.
z-wave.us says they will sell the license for $39 and the UZB can be found for $30 to $35. Not too much more than the $59 for the Razberry GPIO board? Seems like this is a good deal for the additional flexibility. Or am I missing something?