I figured there would be a lot of overlap, as you seem to be using many of the same underlying (F/LOSS) tools.
I was wondering if it might be a duplication of effort, until I realized that your tools seem to be mostly written in Java, where Rhasspy is mostly written in Python. The fact that almost all of these language and AI tools also seem to be written in Python also pushed me in that direction (although pros and cons could be made in either direction, especially when integrating with a Java based tool like openHAB).
For that matter, one could use Rhasspy for the STT and then do the intent recognition right in openHAB. I may look into that at some point, because then you could also do things like send XMPP messages to openHAB as another method of control in addition to voice.
On the other hand, there are so many different choices of intent recognition already built in to Rhasspy, and especially the default one (fsticuffs) works great right out of the box and seems to be well suited to the domain of home automation.
There really are so many different potential ways to set this up… It’s wonderful! I really don’t see myself being limited in any way when using Rhasspy, which is one of the main reasons I decided to use it (and the same reason I chose openHAB).