Since upgrading to 2.2.3.135, when I reboot my hub, it comes back up with a message that z-wave is disabled. I have to go into z-wave details and disable, then re-enable it to get it to work.
It's not the end of the world but it does suck given that I do a nightly automated reboot.
There are a number of known issues w/Z-Wave in the current release (last few, actually), and HE staff are hard at work (evenings and weekends) working on resolving them. I'm expecting good things to start happening this coming week.