This is exactly what happened to me on Hubitat. Never happened to me on SmartThings. These motion sensors are key elements in most of my Home Automation and have NEVER failed me. I consider them the best zwave devices I own. But when I moved to Hubitat it was acting terrible. I moved it back t ST and it is working 100% again. I plan to move it back to Hubitat one more time to be sure. I don't know how to tell what firmware I am running so not sure how to check. But again the 4 I own are rock solid.
Fibaro buttons on the other hand are 100% garbage...just sayin LOL
The only thing I could possibly attribute to their performance issues was that they are unique among my motion sensors in that they only pair using "secure" mode. All my other sensors either have the option to pair secure/standard or do not offer secure as an option. I don't know enough about z-wave networking to know if this could be a factor mesh performance as none of my repeaters offer secure mode as an option either. Maybe I was experiencing a weak signal issue, not sure. All I know for sure is changing brands solved my issues.
The stock driver for this device isnt awesome, but it`s not this bad. Sounds like the configuration parameters didnt set.
I have 4 of the original sensors in production and they do not behave this way.
I think there are few firmware versions of the ZW5 so it's possible the clusters or product number changed between versions which could explain why it didn't get assigned to the correct driver.
I wrote the original ST handler that was linked to above so if you post the fingerprint data i can see if there's a difference between my ZW5 and yours.
I still need to port my ZXT-310 IR Extender, but Remotec devices can sometimes be challenging so I'm saving that one for last.
I already did, see screenshot above. However technically it doesn't matter because when I pick the ZW5 DH the device doesn't work at all and is non-responsive. I tired uninstalling and re-installing several times and it jus doesn't work. I see activity in the logs but states don't change. When I move the device back to ST it works perfectly. I went back and forth 3 times last night with same results. Since I can't see the code behind the ZW5 device I can't add debugging code to it to figure out what is happening. That is the main reason I am considering leaving the platform. SmartThings published their DH code to github in open source so I can look at it, make changes and test. I can also use the open code for reference when working on custom code. Given the lack of documentation it seems to me that open code would be helpful. Is the code the system uses available? I was told by another owner that it is not.
Unfortunately it is very hard for me to debug these issues because I have a full time job and living in Hawaii by the time I start working on the system at home each night it's is the middle of the night for the support folks. The turn around on issues will be too slow. I thought the devices listed as working, which is quite large, meant that they actually worked. I didn't realize that the state of this device was so beta. I don't feel like that was made clear at point of purchase.
The Driver code that Hubiat themselves produce is not disclosed. All Community supplied code must be, since copy paste is the only way to add it to our Hubs.
Therefore, you might want to try the Code @krlaframboise produced. It would give you the chance to inspect/modify the code to debug. IF at the end, you find you can return to the "native" code, you have that option.
Yes, this the code I am talking about. Given that it should be the best designed code written by the company stakeholders. It would be a good reference. But it isn't open.
But the version was posted as a comment, not in github. The thread that follows discusses issues with it. No offense to Kevin, he does great work. But given that his version is now the base code for the system version I want to see the official code. I can't debug issues with the "native" code by switching to random code posted on the community forum. That would just be a waste of my effort.
I purchased Hubitat because I wanted to port my ZXT-120 code over. I wanted to contribute. But with no documentation to help me convert other than random comments from anyone that is hacking away at converting their own and no ability to view clean approved code I don't have the time to invest to help this product succeed. Especially when I realize that the code I provide will eventually be taken into the system (that would be my hope anyway) and then closed down so I have no way to maintain it. I feel this isn't the place for me. I was hoping this effort was going to be more open like HASS but on a platform better designed for easy implementation. I think the second part is planned but I think the plan is to create a closed product given the fact I can't see the existing DH and App code.
It is my understanding that customer's whom have been dissatisfied with their purchase within the specified return period, have been offered a refund for return of the product. Contact @bobbyD via PM for detail
FYI, someone else ported that code posted as a comment and I'm the one that reported it most likely had issues because they didn't change certain things that needed to be changed...
Sorry, my bad. I know you do excellent work. This is kinda why I don't like community only software management. It took a long time for ST to get github working but I depend on it now
That's great, I really wish mine did. I would love to debug the issue but I don't see how I can without some source code.
I am happy to try again if someone can tell me something I need to do differently than
-Include the device
-switch the DH from the incorrect "Fibaro Motion Sensor" to "Fibaro Motion Sensor ZW5"
-send configuration to the device (including 5 button press on the device to wake it)
At this point the device is non-responsive. State remains as Motion:Active Acceleration:Inactive
Sorry if I missed it somewhere else, but after you switch the driver from "Fibaro Motion Sensor" to "Fibaro Motion Sensor ZW5", are you then clicking the "Configure" button in the device window before clicking on "Save"?
If you want to configure your motion sensor, click the B button 3 times quite quickly.
The sensor will glow blue. It is now in configuration mode.
Hit the configuration button in the driver to 'push' the configuration to the device.
I have spotted some sort of anomaly though.
My device is an old version so has HE's 'Fibaro Motion Sensor' allocated to it.
When I look at the device in HE I am seeing this.
This does not seem correct to me.
Any thoughts @mike.maxwell
EDIT: Also since I have been playing, my battery level has dropped to 0%. Put in brand new battery and this is showing the same. Something is afoot me thinks.
yes, that is what I mean when I say "switch" to new DH. save would be required to make that happen. Sorry I didn't make that clear
I should also point out that configurations are working. The device follows my settings. If I set the tamper to flash red white blue it does but status remains static for tamper. If I set it to flash on motion, it does. But status remains motion:active it never returns to inactive.
I kinda know what I am doing. It just isn't working.
