WallPanel for Android [Formerly HomeDash]

did not work on my Fire. Just exits back to main Fire screen after about 1-2 seconds. I reinstalled 0.5 for now. Excited for it though, can stop using IP WebCam!

@quadportnick Really nice how your app is evolving :-).
Before I setup MQTT. For now I would just need it to start/stop the webcam. is this already possible, as it is commented as planned in your api description.

So you’re looking for a feature to turn on/off the camera remotely? This is on the roadmap but currently not in there, I want some means to do the remote config. I haven’t fully planned it to know what the mechanism will actually be but, I expect it will be a JSON blob dropped either via REST or MQTT in the end anyhow, since that pattern is already there in other ways.

Urg hate crashes like that. That was from an upgrade eh? Would it be possible to get that plugged into a computer to get the console output for clues? Unless lots of other people are reporting it may be hard to understand why otherwise.

So far I couldn’t get the camera stream to work with my 7" Samsung Galaxy Tab A. Installing Android Studio now and will have a look using the debug version.
For now it’s working just like 0.5, although the motion doesn’t seem to be published via MQTT. I’m not sure though id every motion event should show up as a new line when using mosquitto_sub. Currently no new line is shown. Waking the screen by motion is working.
With face detection I had a permanent “Face detected!” message in the camera-test-activity. With motion detection enables as well it switched between face detected and motion detected.
The camera stream just gives me a 404, although that might be because of the wrong URI. What I am using is http://1.2.3.4:2971/camera/1, where 1 is the id of the front camera in the settings of the app.

@danielperna84
I get the camera showing in my browser with
http://1.1.1.1:2971/camera/stream with the mpeg feature activated.
but I won’t get it to work in HA
tried both the standard and the mpeg webcam.
guess its just a setup issue in my case.

Huh, turns out it works in Firefox. Only Chrome seems to have problems. May be some privacy-extension then.
By the way: I missunderstood what the URI should be. Somehow I thought I should replace the stream component with the ID of the stream within the device.

If you can walk me through it or point me to some directions, yes.

I uninstalled .5 and .6 and tried it fresh and got the same results.

1 Like

Regarding the face detection, this is the logoutput I get, from activation to deactivation of the feature a few seconds apart:

05-07 21:47:10.831 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: A Camera Setting Changed
05-07 21:47:10.831 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: configureCamera Called
05-07 21:47:10.831 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: stopCamera Called
05-07 21:47:10.831 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: stop Called
05-07 21:47:10.971 9264-9274/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 1 is not owned by the producer (state = 0)
05-07 21:47:10.971 9264-1661/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 2 is not owned by the producer (state = 2)
05-07 21:47:10.981 9264-1661/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 7 is not owned by the producer (state = 0)
05-07 21:47:11.111 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: start Called
05-07 21:47:11.111 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: getCameraInstance called
05-07 21:47:11.512 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: Camera Face detection is enabled
05-07 21:47:11.512 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: startFaceDetection Called
05-07 21:47:11.512 9264-9264/de.rhuber.homedash I/Choreographer: Skipped 40 frames!  The application may be doing too much work on its main thread.
05-07 21:47:11.902 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:11.902 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.072 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.072 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.192 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.192 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.323 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.323 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.443 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.443 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.563 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.563 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.693 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.693 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.813 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.813 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:12.943 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:12.943 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:13.063 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:13.063 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:13.193 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:13.193 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:13.274 9264-9264/de.rhuber.homedash D/ViewRootImpl: ViewPostImeInputStage ACTION_DOWN
05-07 21:47:13.314 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: Face detected
05-07 21:47:13.314 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.SensorReader: doFaceDetected called
05-07 21:47:13.414 9264-9264/de.rhuber.homedash I/org.wallpanelproject.android.WallPanelService: A Camera Setting Changed
05-07 21:47:13.414 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: configureCamera Called
05-07 21:47:13.424 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: stopCamera Called
05-07 21:47:13.424 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: stop Called
05-07 21:47:13.574 9264-1661/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 4 is not owned by the producer (state = 0)
05-07 21:47:13.574 9264-9421/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 5 is not owned by the producer (state = 2)
05-07 21:47:13.574 9264-9644/de.rhuber.homedash E/BufferQueueProducer: [unnamed-9264-0] cancelBuffer: slot 7 is not owned by the producer (state = 0)
05-07 21:47:13.724 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: start Called
05-07 21:47:13.724 9264-9264/de.rhuber.homedash D/org.wallpanelproject.android.WallPanelService: getCameraInstance called
05-07 21:47:14.134 9264-9264/de.rhuber.homedash I/Choreographer: Skipped 42 frames!  The application may be doing too much work on its main thread.

Face detection works for me, however I have to be pretty close :smile:

Did you get the camera implemented?

Yeah, it’s working now. Have to use Firefox though. Seems to be some local issue with Chrome.

how did you setup in config?

You mean in HASS? I don’t use it there. I’m using ZoneMinder. Currently I have no cameras in HASS.

I can confirm 0.6 is working on a 4.2 Odys Ace. Can’t get the stream to work there though. But the browser and wake on motion do work. The not working stream is not relevant for me though since I’m not using the device anymore. So this is just feedback for the lowered API.

1 Like

When I click on a the change Load_dashboard widget i just get a spinning circle and it doesn’t actually load the new dashboard, same happens for the reload widget. This only happens from the app and works jsut fine in chrome (desktop and tablet).

Nvidia Shield running 6.1 if that matters.

Any assistance would be appreciated

ps: Awesome app, wife can finally see whats going in the house without having to ask me all the time :slight_smile:

1 Like

Whew a number of little issues on this release. Going to look into embedding some kind of log submission functionality directly in the app so I can get some telemetry and work it out. It’s not viable to get everyone to keep swapping builds and plugging in cables :).

Thanks for your patience!

I’m just using the Android based face detection in this release which is pretty slow for me too. Really not slow as much as super picky. Probably need to go another direction with that to make it actually useful. The QR code is pretty fast, for comparison.

I notice HASS has a new OpenCV image processing component and maybe having HASS determine it would work. Also maybe OpenCV would work fine on the tablet

Roger. As above I think a crash reporter lib is a better idea for the long term so stay tuned

All operating fine for me on Nexus 7s with Cyanogen/Lineage KitKat. Have not enabled or tested any of the new features though, just an upgrade.

Good to hear no regressions on the core stuff :slight_smile: