Cool. Did you try changing the polling intensity?
light.linear_lb60z1_dimmable_led_light_bulb_level:
ignored: false
polling_intensity: 1
refresh_value: true
Cool. Did you try changing the polling intensity?
light.linear_lb60z1_dimmable_led_light_bulb_level:
ignored: false
polling_intensity: 1
refresh_value: true
Tried setting the polling intensity to 1. No change.
Again not knowing what you saw. I would tail -f OZW_Log.txt an see what openzwave reports as you operate the sensor.
In the OZWCP is there a Reporting parameter for the device? If so what is it set to?
In the first few min the log updates with each sensor trip. Then it just stops. No more updates. No errors in the HA log either.
Haven’t setup OZWCP, the zwave xml file is posted above if that helps. Should have all the same info OZWCP has.
I would try looking at the syslog file in /var/log
Use a simple grep error /var/log/syslog
If nothing jumps out then try zwave
What install method do you use?
I’ll check the logs tonight see what pops up.
Installed via the virtualenv docs.
I went to your github link and see you have 2 installs. One virtual and on a Pi. If this is the virtual one you are having issues with, you might also want to check logs on the ESXi server as well as the VM logs in the HA VM folder. If you haven’t already, you can redirect the ESXi server logs to permanent storage (Local or NAS) since they are blown away after a restart and they are much easier to get to when you need to track down problems.
Thanks for the continued troubleshooting options.
I was thinking of trying restoring the hub and sensor to factory defaults and then try both on the pi instance. See if it is something in the virtual instance causing the issue.
I think HA works well on the Pi but, every time I have to rebuild the Pi I think I really should set it up virtually. So easy to back up a complete bootable image in a few minutes.
Another thing to try is a different USB port but if you are going to move it to the Pi, maybe no need to extend the agonies.
If you already have the device paired, it should just work when transferred to the Pi. Just add the zwave lines to your config and install openzwave if needed. It may auto install???
I have tried different USB ports, should have mentioned that.
I was thinking of starting fresh on the hub and sensor just so nothing gets carried over that could hamper the Pi operation. Both can be restored to defaults in about a minute so not a time consuming task. If the Pi instance doesn’t work I may run out and pick up a powered Zwave switch and see how it behaves. If it drops to after a few minutes it would point me to the USB hub, if it works fine, I think the door sensor would be going back.
Lots of options to try tonight, thanks, Ill report back with the outcome.
Hope it goes better than it has. I have really liked z-wave, but it took adding a few powered devices before it became really reliable. When you are looking for devices, lean towards z-wave plus if you have the choice. Don’t give up!
Well looks like its an issue with my server or the virtual instance. Set things up on the Pi and working nicely.
Thanks for the help zarthan.
Glad you got it figured out.
Every time I have to rebuild a Pi instance of HA I think, why don’t you just spin up a VM and be done with it. So maybe not.
It would be interesting to know why it failed. I have a spare zwave stick so I may give it a try. I have some zwave things coming so I will have some things to test with. What version of ESXi? Did you need any community drivers to get it running on the Dell?
Yeah, I think tonight I may move the zwave stick back to the server and see if it behaves. Its nice that its working on my Pi and I know that the zwave stuff doesn’t need to be returned but all my automations for the sensor dont work because they are on the wrong instance, connecting the two is a bit of a pain.
Im pretty sure Im on 6.5, it installed nicely on the dell. This is the first issue I have run into related to that server.
I’ve noticed on some occasion that ESXi will drop the USB passthru for no reason intermittently or just stop communication with the device all together.
I’m not sure that a zwave stick would be considered an ideal candidate for ESXi passthrough. You might want to try dedicating CPU / RAM to the HA VM?? Maybe Since business devices aren’t restricted as much for RF shielding, you might want to try a USB extension to get it away from the box???
I have just started up my HA VM and will do some looking.
@silvrr I thought I would check back. I did move my install from the Pi to a dedicated Debian VM. I did a straight install with no Python virtual_env. I have ESXi 6.5 running on an Intel Skull Candy NUC. There are 6 to 10 VMs on this NUC with nothing significantly active besides a MythTV recorder. I don’t know how this compares with your VM load. My install seems to be working well for now. I will update this if I experience any issues.
Posting just incase anyone is having issues in the future with this. @firstof9 posted a fix that has provided zwave stability in my virtual instance.