MaxCube is absent sometimes, how can pimatic monitor MaxCube

---

Hello, together, there is to use a possibility the announcements (error messages) of the MaxCube in a Rule?
The reason: Every now and then my MaxCube hangs itself and makes nothing more. Until I it with agree it sometimes lasts something. But then it gets cold or it just does not get cold.
Now I have planned to switch the Cube with an Espimatic from to restart him then. Switch off and on when absent.
But how can I do it?

I get the following error messages if the MaxCube not reacted:

04:00:26error [pimatic]: Error on evaluation of rule condition of rule wz-fenster-auf: Unknown mode: undefined
04:00:26error [pimatic]: rule wz-fenster-auf error executing an action: Unknown mode: undefined
04:00:14error [pimatic]: Error on evaluation of rule condition of rule temptest3: No awnser from cube after 10000ms
04:00:14error [pimatic]: rule temptest3 error executing an action: No awnser from cube after 10000ms
04:00:04error [pimatic-max]: connection error: Error: The cube is busy

is the cube still available in the network when having this issue (ping)? you could ping it and when it is offline you can restart it with a poweroff over the espimatic relais or rf outlet

@leader21
I do not know of the cube on ping answers if he “busy” is. But a good idea. I will create a rule. Then I can find out it certainly. I hope so.

I had tried out a rule with Ping. Unfortunately, without success, The Cube is accessible in the net, even if he does not react any more.

However, this problem has taken care for me.
I use a CulStick with pimatic-maxcul since some time.

Still thanks for the help.

I think the the problem is that the underlying max-control does not reset the busy state on connection failure. The busy state is used to make sure no command is sent before data has been received for the prior command. I’ll provide a fix as soon as I have access.

https://github.com/sweetpi/max-control/blob/master/index.js#L56-L80

Released pimatic-max@0.9.0 with tentative fix for “cube is busy” issue. This version also provides destroy functions for the max device classes.