Announcement

**rjh** · June 20, 2022, 10:05 AM

Ok, thanks. I suspect some of these are in the legacy plugin as well. We did not change any of the code that handles the devices. But I will need to test to make sure.

Originally posted by John245 View Post

rjh

Hi Rich I did some testing on the beta version of the Z-wave plugin. I summarized my results in the table below, but I prefer discussions in the separate threads. I will update this overview when issues are solved or new issues are found. Looking forward to the next version.

Issue#	Issue type	Description	Status	Criticality	Link(s)	Comment(s)
1	Bug	Z-wave devices not correctly displayed on device information page	Open	Major	https://forums.homeseer.com/forum/ho...91#post1551591	Based on testing 4.0.0.0 beta
2	Bug	Setting decimal places not respected in case last digit is zero	Open	Major	https://forums.homeseer.com/forum/hs...ro#post1553108	Based on testing 4.0.0.0 beta
3	Bug	Fibaro Smoke Sensor (FGSD-002) not reporting battery status	Open	Major	https://forums.homeseer.com/forum/hs...us#post1553102	Based on testing 4.0.0.0 beta
4	Bug	Wake-up interval value incorrect when devices goes into deep sleep	Open	Major	https://forums.homeseer.com/forum/hs...ep#post1553052	Based on testing 4.0.0.0 beta
5	FR	Search option is lacking for device locations when adding a device	Open	Minor	https://forums.homeseer.com/forum/hs...ce#post1553033	Based on testing 4.0.0.0 beta

---
John

**John245** · June 20, 2022, 10:08 AM

Originally posted by rjh View Post

Ok, thanks. I suspect some of these are in the legacy plugin as well. We did not change any of the code that handles the devices. But I will need to test to make sure.

I suspect issue 2 also in the legacy plugin. As my assumption is that this is caused by the device version (3.2 versus 4 for other HomeSeer 4 devices). However it would be great if things are handles consistently.

---
John

**SteveMSJ** · June 20, 2022, 12:14 PM

Originally posted by John245 View Post

I suspect issue 2 also in the legacy plugin. As my assumption is that this is caused by the device version (3.2 versus 4 for other HomeSeer 4 devices). However it would be great if things are handles consistently.

---
John

Yes, I can confirm issue 2 has been there for HS3 devices, as long as I can remember. I hadn’t noticed it was corrected for version 4 devices, probably because the majority of my devices are version 3 due to being Z-Wave.

I’m pretty sure I submitted a bug report on it many years ago and certainly others did as well. It would be good to see it finally addressed, particularly as Z-Wave devices look like they will be stuck at version 3 for some time.

Steve

**John245** · June 20, 2022, 01:14 PM

Originally posted by SteveMSJ View Post

Yes, I can confirm issue 2 has been there for HS3 devices, as long as I can remember. I hadn’t noticed it was corrected for version 4 devices, probably because the majority of my devices are version 3 due to being Z-Wave.

I’m pretty sure I submitted a bug report on it many years ago and certainly others did as well. It would be good to see it finally addressed, particularly as Z-Wave devices look like they will be stuck at version 3 for some time.

Steve

Good that you confirmed my assumption about the root cause as I mentioned in the separate thread.

rjh Can you fix this for version 3.2 devices? Or even better make the Z-wave devices v4..

---
John

**John245** · June 23, 2022, 12:33 AM

rjh I promoted issue 1 to critical as is will occur for more devices. But the most important factor to do this is that these devices are also not visible in HSMobile.

---
John

**spud** · June 23, 2022, 10:55 AM

Originally posted by John245 View Post

rjh I promoted issue 1 to critical as is will occur for more devices. But the most important factor to do this is that these devices are also not visible in HSMobile.

---
John

On your screenshot here : https://forums.homeseer.com/forum/ho...e2#post1551591
your filter in device information page is set to Room= "Terrace(garage)", but your actual root device has a room="Fibaro switch Binary FGS-221". The filter in this page is only checking the location/location2 of the root device, and not the ones set for the features.
Do you see your devices if you set the room filter to Any?

**John245** · June 23, 2022, 02:21 PM

Originally posted by spud View Post

On your screenshot here : https://forums.homeseer.com/forum/ho...e2#post1551591
your filter in device information page is set to Room= "Terrace(garage)", but your actual root device has a room="Fibaro switch Binary FGS-221". The filter in this page is only checking the location/location2 of the root device, and not the ones set for the features.
Do you see your devices if you set the room filter to Any?

O tried it for 2 other examples. the first root device ends with 1&2 and the second root device with 3&4. In the Z-Wave device information I will zee the 1st root device if I apply the following filter:

1) System "Irregation" and room "any"

I will have the same results applying the following filter

2) System "any" and room "Cellar below terrace"

For the devices below I can only see the second root device when filtering.

And even more important in case I apply no filter I will also not see the devices (first example 1st root and second example the second root).

---
John

**John245** · June 24, 2022, 12:32 PM

Text removed as additional info is no longer relevant.
---
John

Announcement

Overview testing results HomeSeer4 Z-Wave plugin

Overview testing results HomeSeer4 Z-Wave plugin

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment