I think it's OK to allow yourself a break. You don't have to be achieving, or particularly productive (from your own perspective). Sometimes I imagine a life where I wake up, dawdle around and make breakfast, wander into work and do my 9-5 with my colleagues and then wander home to cook dinner and enjoy some mindless movie on TV. You can think of it as "passionless", but I think of it as "vacation".
It's a nice idea. You don't strive for anything, or fight for anything. You don't argue with your colleagues, or push to "get it right" or to "be successful". You just hang out and enjoy everyone's company and the small challenges that your job provides for you every day.
This is much better than dropping everything because when you drop everything, it's easy to drop into depression. It's easy to see everything that you've given up and see this temporary lack of energy as a "failure". It's much better to give yourself permission to enjoy merely existing and doing the simple things that get by. This is not "working without passion", this is just spending your time enjoyably with your colleagues. Like, I said, it's 100x better than locking yourself up and playing video games all day, or drinking yourself into oblivion, or even travelling the world to "find yourself".
For people who are really driven by passion, it's not like you will end up staying in that simple world. Slowly your passion will well up and take over again. Take your time and learn to enjoy it.
The issue is not taking passion for granted and ending up being bipolar, ability to actually enjoy mundane casual work is good. But it's also tough to balance with marketplace demands, sometimes you can't have unproductive days even if you're out of attraction (say a large contract badly built on fragile tech with no design and no care). Your paycheck depends on it.
But if you think back, how many times did people thank you (before the end of the project) for doing what was necessary to get the project back on track? How many times did you use super human effort to claw a monstrocity from the brink of disaster and have half the dev team pissed off at you because of it.
I don't want to get into a large discourse, but your posting stood out a bit, in a "I know that pain" kind of way. I don't know you so this may be totally wrong, but my experience has been that there are many roads to success. Even that word "success" is arbitrary (as we have seen so frequently when managers redefine it after the fact). You are allowed to choose your definition.
Sometimes you just aren't up for the gunslinging heroics that are required save the project. But you might be up for spending some quality time with the other developers and helping them improve themselves. The project may tank, but everybody might end up thanking you because of it. Even better, you may inspire someone else to do the necessary heroics now that they have someone to cheer them on.
The one (somewhat disturbing) reality that I have learned in this job is that neither my pay check, nor the way people feel about me seems particularly related to the success of any particular project. Sometimes giving people what they should value (success) over what they actually value (support) is a form of hubris in itself.
Anyway, I hope that is interesting even if it doesn't seem useful ;-)
I've found that as I've gotten a little older, my tolerance for unnecessary complexity, unnecessary time demands, and doing pointless things, has plunged. I have also found that I'm much happier and more productive after stripping away as much of that as possible. There are various costs to doing so, but it has been worth it so far. When I was 20, I felt like I could juggle anything and everything (and no doubt reducing how effective I was in the process).