Feat/timeout hack

EmberClient/EmberClient.js

@@ -619,6 +619,39 @@ class EmberClient extends EventEmitter {
         });
     }
 
+    /**
+     * 
+     * @param {TreeNode} node 
+     * @param {string|number} value
+     * @returns {Promise<TreeNode>}
+     */
+    setValueNoAck(node, value) {
+        // This function immediately finish & resolve so we can't get any timeouts ever
+        // This is a pretty ugly hack, but it doesn't look to bring
+        // any negative consequences regarding the execution and resolving of other
+        // functions. It´s needed this because if the node already has the value we are
+        // setting it too, it will cause a timeout.
+        return new Promise((resolve, reject) => {
+            if (!node.isParameter()) {
+                reject(new Errors.EmberAccessError('not a Parameter'));
+                return;
+            }
+            this.addRequest({node: node, func: error => {
+                if (error) {
+                    this._finishRequest();
+                    reject(error);
+                    return;
+                }
+                winston.debug('setValue sending ...', node.getPath(), value);
+                this._client.sendBERNode(node.setValue(value));
+
+                this._finishRequest();
+                this._callback = null;
+                return resolve(node)
+            }});
+        })
+    }
+
     /**
      * 
      * @param {TreeNode} qnode