If you are going to change something I would say get the multisensor 6 - it worked a lot better. HA ran fine for me on a PI2 although I have upgraded to a PI3 then Beebox since then. I don;t remember ever getting the gen 5 to work well, the grn 6 works great.
barry, i had the same sensor and same issues.You will need zwave control panel (install as a docker install)
The fix is easy.
remove the sensor from your zwave controller via the control panel. Then ensure your sensor is powered via USB as it wont go to sleep. Then add the device, and configure group 1 225 and ensure iset to binary sensor. Ensure the device doesnt sleep during this process. Use the following docker command to get the config synced, replacing your zwave xml file name. Once saved, ensure that the xml file in the hass directory has the right value for the Command Options (i deleted the file xml in my hass to know once i saved in control panel the file was being saved by control panel).
Below it looks like its set to basic set as the vindex is “1” but its not. The options are either 0 or 1, 0 is basic set, 1 is binary sensor report.
> <Value type="list" genre="config" instance="1" index="5" label="Command Options" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="2" vindex="1" size="1">
> <Help>Which commands to send when PIR motion sensor triggered OZW Ideal Value is Binary Sensor Report</Help>
> <Item label="Basic Set (default) " value="1" />
> <Item label="Binary Sensor Report" value="2" />
sudo docker run -d
--name="ozw-cp2" -u 0 -p 8008:8008 --device=/dev/ttyACM0 -v
/home/hass/.homeassistant/zwcfg_0xcxxxxxxx.xml:/home/ozwcp_user/open-zwave-control-panel/zwcfg_0xcxxxxxxx.xml
openzwave/openzwave-control-panel
1 Like
That’s fantastic news switched. Thank you. And thank you aimc - I might get a ‘6’ anyway, just to get things working.As long as someone has it working I’m not wasting my time plugging away.
One step I have definitely been missing is the remove device and add device part when making changes. I think I’ll reset all the z-wave devices tomorrow and just add a single sensor and see if I can get it to work.
Hang on… If I copy the zwcfg…xml from the OZCP directory to the home assistant directory and replace/delete the existing xml will this achieve the same thing as the command above? (After making the changes of course.)
The all-in-one installer installs the control panel at /srv/hass/src/open-zwave-control-panel . It’s working, making changes but I have noticed the xml in the HASS directory only changes modification date after I initiate a restart of HASS. I don’t know if it’s a docker install or not, I think the OZCP file changes as I make and save the changes in the control panel.
And yes, the vindex=0 on my HASS xml despite changing in OZCP to binary reporting.
The final arbiter of whether or not a device is paired is the stick itself. The zwcfg seems to be a cache and can be deleted and will be recreated by OpenZWave by running either HA or OZWCP. However, it seems to be possible to add some info and have it picked up like for instance device names by editing the file (although I always do this in OZWCP to be on the safe side) - in either case you should synchronize the file between OZWCP and HA - I use a symbolic link to do so.
Thank you aimc, I’ll look up symbolic links later.
Some success, they are now stuck on 0 instead of 7! I’ll see if they shape up after a few restarts.
I’ve reset the devices, reset the stick, even updated sensors to latest firmware (1.03) and seem to be doing the same thing over and over with no success. I think I might be missing something obvious. I tried editing the xml directly but no luck.
I might have to consider ditching my v5 sensors and replacing them with v6.
Is it possible to check if motion is even being reported at the sensor end with a Windows application?
One of my Aeon 5 sensors was “7” and still is i believe, this inst what you need to be monitoring. The motion detect is the BINARY sensor, infact just checked my configuration file and this is the name below. Check in your STATES to see what the status of this sensor is (it would be prefixed with “binary_sensor”)
binary_sensor.aeotec_zw074_multisensor_gen5_sensor_5:
These are the sensors that are useless, I’ve hidden them as they don’t change.
sensor.aeotec_zw074_multisensor_gen5_sourcenodeid_5:
sensor.aeotec_zw074_multisensor_gen5_alarm_type_5:
sensor.aeotec_zw074_multisensor_gen5_alarm_level_5:
I have the lux, temp, humidity and motion detect working.
Before using ZWCP, stop HASS process, remove the XML file in the HASS directory (zwcfg_0xc…xml). Fire up ZWCP, initialise device ensuring the unit was factory reset and USB powered before joining), from memory i joined to the contorller whilst in USB powered mode. Once added you should see the device not go to sleep mode… this is very important.
Make the changes, and then save the config. If all is successful, it will save to your config directory at this point. Check to ensure. Validate settings in XML as per the above and you should be good.
Remember to modify the docker run command to suit your environment, my config is in /home/hass/ as I am a standalone installer (not AIO) change the path to your directory, and to match the same name as your XML file name (this is different per controller).
1 Like
EUREKA!
There it is, my stupid simple error. It was working all along, I’d done it properly but was looking at the wrong sensor.
Thank you so much.
Glad you got it sorted, like you, I was close to just getting a 6 version of it!
Now, I thoroughly enjoy setting off the motion, and having it send me an alert via pushbullet for all my hours spent working out what and how to use zwave!
Already had the lights set up, and they are reacting nicely now, once I changed the sensor names it all came good. Had a “6” in my shopping cart today but decided to hold off for a week because I couldn’t really afford it. On to the next challenge!
1 Like
After restarting HASS, my motion (burglar) sensor is stuck in the ‘motion state’ (value 8) until actual motion is detected and the timeout has occured. Anybody happen to have this problem too with the Multisensor 6 (running the latest firmware V1.07)? And if so, how can it be fixed?
I’m getting tired of having to wave at my Multisensor 6 after restarting HASS. On top of that, I don’t always remember to do so. And it’ll only get worse if/when I decide to add more of these sensors to my setup.
Same error at my 2 Multisensores. Any solutions yet?
I have two sensors and after restarting one is stuck with value 8 and another one with value 3. Both of them report correct values once motion is detected. I assume that incorrect state value is stored in hass.
I think the culprit is OpenZWave rather than Home Assistant in that case, for the following reasons:
- If you manually change the state of the sensor through the developer tools in Home Assistant, the state will just flip back. So the only fix is triggering the sensor physically.
- I recently went into OpenZWave to add a new node I had purchased (an Aeotec Smart Switch 6). Ever since then, the state of the burglar sensor has been showing up correctly in Home Assistant after restarting it or rebooting the host. I have no idea how or why…but obviously, I am not complaining
1 Like
Multi 6 sensor works fine on Hassio. I have 2 both working on battery 
Some instructions would be nice…
All you should have to do is add the sensor as explained in the documentation. If you’re having problems, then please explain what they are.
Of course, you’re best off starting your own thread, given that your problem is unrelated to the subject of this thread 