I usually say no. Component-local state does not belong in Redux because Redux is a global store. It has no awareness of a component's lifecycle, and it's very easy for multiple components to accidentally write to the same slice of Redux state.
Instead, we're looking for ways to make React's state API more functional and Redux-y, so people are less tempted to abuse Redux :)
Valid exceptions include when state serialization/deserialization is really important, or if you want to use the Redux DevTools. Though I think there are better solutions to these problems out there, waiting to be implemented.