@marcel_verpaalen great work with this binding. 
When setting up the binding I run into something I found strange about the action channel.
After issuing an vacuum command the binding is bouncing to the dock state.
Check this log:
17:41:05.516 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'PinguRobotVacuum_Actions_ControlVacuum' received command dock
17:41:05.528 [INFO ] [marthome.event.ItemStateChangedEvent] - PinguRobotVacuum_Actions_ControlVacuum changed from vacuum to dock
17:41:05.734 [INFO ] [marthome.event.ItemStateChangedEvent] - PinguRobotVacuum_Actions_ControlVacuum changed from dock to vacuum
Maybe this is logical if the robot after getting vacuum command have time to scans its state before “taking off” and finds itself still in the dock, eg. reports that (2). And a short time thereafter starts the vacuum and then reports that again (3).
I would find it nice if there would be an debouncing check on 200ms or similar to avoid this behavior. This will make GUI:s correct and scripting much more simple to implement against the binding.
Using device firmware: 3.3.6_003062
Binding version: market:binding-3499123 - 1.0