WallPanel for Android [Formerly HomeDash]

Third party integrations
344

Yesterday the application was automatically updated, now it can be a desktop and a button for entering a pin code has appeared in the lower right corner, but now I can’t get into the application settings, how do I get there?

345

So I’m using browser_mod (code below) for my doorbell automation which works great. The only issue is that my Amazon Fire Tablet running WallPanel goes into clock screensaver mode after a minute and the browser_mod popup never wakes the screen to show the image. Any workarounds?

service: browser_mod.popup
data:
  content:
    type: picture-entity
    entity: camera.blueiris_pc_frontdoor
  timeout: 5000
  title: Front Door
  size: wide
target:
  device_id:
    - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
346

Anybody else having problem with the sensors becoming unavailable from time to time? I need to kill the app and restart it to get them working again.

347

I’m doing the same for my nest doorbell. In my automation, I’m first waking up the tablet with a mqtt publish command, then sending command for browser_mod popup… Also experiencing sensors bwcoming unavailable, but have sort of made a workaround, by restarting the wallpanel app with an automation when the sensors gets unavailable.

service: mqtt.publish
data:
  topic: wallpanel/mywallpanel/command
  payload: "{\"wake\": true, \"wakeTime\": 30}"
348

Just tested this and it works great. Screen wakes instantly. One question, how would I do this to multiple tablet at once. Would I have to create an action for each one?

349

Great :+1: should be possible to use same action for multiple devices. Just be sure to use the same topic

350

I thought about that, but wallpanel only allows for one base topic. What if I wanted to publish something separately to an individual tablet?

351

Not sure if i understand fully, but wouldn’t that just be:

Base topic:
Tablet 1 - /wallpanel/device1/
Tablet 2 - /wallpanel/device2/
Etc

And use seperate actions in automation for each individual case

352

That’s what I was trying to avoid. I have 15+ tablets throughout the house. What would that automation look like? Also, what kind of delay would that be on tablet number 14?

353

Well then I would just use the same base topic, just use the mqtt publish to wake all the tablets. Then browser_mod is a able to run actions on each individual device using that tablets device_id.

354

@sjefen It would almost be faster to driver over to ask you (from Mandal!), but I guess that would be a bit imposing… :rofl: But you seem to know this stuff, so I’ll try to ask you anyway: I need to wake the tablet with MQTT from Node-RED (standalone) to WallPanel. I have the NR flow set up with topic madmax/wallpanel/command and I have my WallPanel base topic set to madmax/wallpanel/. Then I have the payload set to JSon, "{\"wake\": true, \"wakeTime\": 30}", but nothing happens. Nothing at all. And I can’t see the battery sensor sends anywhere either. This is the setup for the MQTT in WallPanel:

Enabled MQTT Client blue and to the right
MQTT Broker address http://192.168.2.101
MQTT version 3.1.1.
SSL/TLS off
Port 1883
Base Topic madmax/wallpanel/
clientID mywallpanel (didn’t change this)

I have also activated sensors, only battery works. Do you see any weirdness in this?

Edit: I tried it as an automation in Hass as well:

</s> <s>#Test - Vekke nettbrett</s> <s>- id: '15323583268789989'</s> <s> alias: Vekke nettbrett</s> <s> trigger:</s> <s> action:</s> <s> - data:</s> <s> topic: madmax/wallpanel/command</s> <s> payload: "{\"wake\": true, \"wakeTime\": 30}"</s> <s> service: mqtt.publish</s> <s>

I see the MQTT message in Node-RED, but nothing happens to the tablet.

I found the problem: I had misunderstood the need for http://. It works without, of course. Sorry about the brain fart… :upside_down_face:

1 Like
355

Has anyone found a way to have the Wallpanel do a daily refresh? Whenever HA restarts, all tablets display code instead of the dashboard.

356

I use an event for refreshing when the dashboard is updated, you could do the same with a time trigger. Requires MQTT though.

alias: Refresh wallpanels when Lovelace is updated
description: ""
trigger:
  - platform: event
    event_type: lovelace_updated
condition: []
action:
  - service: mqtt.publish
    data:
      payload: "{\"wake\": true}"
      topic: wallpanel/opo/command
  - delay: "00:00:02"
  - service: mqtt.publish
    data:
      payload: "{\"reload\": true}"
      topic: wallpanel/opo/command
mode: single
2 Likes
357

thats nice, copy paste to my system, thanks for sharing.

358

Yeah, i used that, too. But the problem of this approach is that ALL devices are updated each time you press “save”, no matter if they show lovelace you edit or not. It’s not a big deal, but it can get annoying since i have “many” tablets around my house…
So i rather use “selective semi-manual” approach: i created input booleans for all devices and when i edit lovelace i turn on only those effected. Then i created an automation-script which refreshes selected tablets with fully’s rest command.

359

Does anyone have automatic dark mode working?

360

Does anybody know how to open external apps through the wallpanel app with lovlace ui?
According to the docs of wallpanel it has support for the ‘intent’ feature for this purpose. But I can’t get it to work.
I tried different URI syntax I found online, like “app:”, “spotify:” and of course “intent:”, but nothing worked from within wallpanel. I even used the example code given in the source code for intent parsing:

intent:#Intent;launchFlags=0x10000000;component=com.amazon.avod/com.amazon.avod.client.activity.HomeScreenActivity;end

It always opens a new site with the error: “Connection Error”.

Interesstingly, most of the URIs I tried do work if I use the homeassistant companion app on the same tablet.

I did use this intent URI in an lovelace entity block e.g.:

icon: mdi:web
name: Google Maps
type: weblink
url: >-
  intent:#Intent;launchFlags=0x10000000;component=com.google.android.apps.maps/com.google.android.maps.MapsActivity;end

Can anyone help me out with a hint? Thanks!

2 Likes
361

Hi everyone,
I have trouble sending a template mqtt payload:

service: mqtt.publish
data:
  topic: wallpanel/mywallpanel/command
  payload_template: "{ \"brightness\": states.sensor.brightness_smart_clock_conversion.state }"

I have the brightness value as an input_number variable (ranging from 0 to 100%) in order for me to ajust brightness directly through my wall panel and a slider.
Does anyone know what I did wrong?
Thanks !

362

I installed this app today, I have configured everything, I have the MQTT sensors working, but I can’t send any command through MQTT to the tablet…
HTTP commands are working ok, MQTT no.

Any idea?

Edit:

I solved it…

Seems that if you have the base topic like this “wallpanel/mydevice”, the mqtt topic which you want to publish, should be like this “wallpanel/mydevicecommand” (without the dash)… which is very strange…

Thanks to @mannebk with the information from this post Wall panel, help with mqtt commands, locked my self out, mqtt command for settings menu, mqtt command for tts talking - #5 by mannebk

363

When I turn on the MQTT client in the settings, the tablet (Samsung Tab A7 Lite) turns on the screen every 3 minutes. If I turn off MQTT, then there is no problem.

At the same time, there is no such problem on another tablet (Teclast P80).
Any ideas?