machines: fix wrong usage of nested setState calls
machines: fix wrong usage of nested setState calls

This was resulting on console warnings:
Warning: An update (setState, replaceState, or forceUpdate) was scheduled from inside an update function

martinpitt/cockpit,garrett/cockpit,martinpitt/cockpit,garrett/cockpit,cockpit-project/cockpit,garrett/cockpit,cockpit-project/cockpit,mvollmer/cockpit,mvollmer/cockpit,mvollmer/cockpit,cockpit-project/cockpit,garrett/cockpit,cockpit-project/cockpit,martinpitt/cockpit,martinpitt/cockpit,martinpitt/cockpit,mvollmer/cockpit,cockpit-project/cockpit,garrett/cockpit,mvollmer/cockpit