fix: Klipper reset should only reset its own state

Signed-off-by: Pedro Lamas <pedrolamas@gmail.com>

src/mixins/services.ts

@@ -9,8 +9,8 @@ export default class ServicesMixin extends Vue {
    */
   async _klipperReset () {
     this.$store.commit('socket/setAcceptNotifications', false)
+    await this.$store.dispatch('server/resetKlippy', undefined, { root: true })
     await this.$store.dispatch('reset', [
-      'server',
       'printer',
       'charts',
       'wait'

src/store/server/actions.ts

@@ -15,6 +15,10 @@ export const actions: ActionTree<ServerState, RootState> = {
     commit('setReset')
   },
 
+  async resetKlippy ({ commit }) {
+    commit('setResetKlippy')
+  },
+
   /**
    * Init moonraker components.
    * During app init, we want to initially init these once, irrelevant

src/store/server/mutations.ts

@@ -11,6 +11,15 @@ export const mutations: MutationTree<ServerState> = {
     Object.assign(state, defaultState())
   },
 
+  setResetKlippy (state) {
+    const { klippy_retries, info } = defaultState()
+
+    Object.assign(state, {
+      klippy_retries,
+      info
+    })
+  },
+
   setServerInfo (state, payload) {
     Vue.set(state, 'info', payload)
   },