Have been trying 0.7b1 for sometime. Looks like after I changed the mqtt parameters and set the server to http://hassio/homeassistant Wallpanel goes into a loop crashing over and over and asking to sent a crash information. If I answer ok it stops. Tried to force stop and clear cache but that didn’t help. As soon as I open the app it crashes. Cleared data and then had to reset all params and start over again. I am running android 6.0.1 on a RCA Voyager tablet.
What should the mqtt server be set too. I am using http://hassio/homeassistant in node red without any problem. My main hassio uses duckdns so will give that a try.
nickrout - thanks for the reply. I am sorry but being very new to all of this I am not sure what you mean by “hostname”. In my config.yaml file I have my mqtt broker set to 127.0.0.1 (localhost). Should I set it to localhost or the tcp/ip address.
Anyone running wall panel on Android 8? I’m using an old phone which has been updated recently to 8.0. 0.7b of wall panel keeps crashing when the screen is woken when motion is detected.
It is really hard to know whether you are asking for what to put in your configuration.yaml file or into your wallpanel setup.
If your broker and your home assistant are running on the same machine then the broker entry in configuration.yaml should be 127.0.0.1, although localhost should also work.
In wallpanel, you need to set the mqtt server name so it can find your home assistant/mqtt machine. From the tablet that will NOT be 127.0.0.1, it will be whatever address your home assistant/mqtt machine has on your lan, like 192.168.1.100 - or if your internal dns works, you could use the hostname like hass-server (or whatever name it is called on the network).
nickrout thanks again for the reply. I guess what got me confused is that in Wallpanel address of the Hadashboard can’t be the simple IP address such as 192.168.1.10 but must have the http:// and the port 1883. I therefore assumed it had to be in the same form for the MQTT address (without the port). Your second answer clarified it for me and now it is working.
Don’t know how to help with this issue. All was working then I set camera enabled, motion detection enabled, motion wakes screen and then as soon as I set motion increased brightness it crashed. I tried to restart it but it crashed again. Went to settings apps and forced stop. Cleared Cache. Tried to restart but crashed again and this time went into a crash loop. Had to uninstall and re-install Wallpanel. Using 0.7b1 with android 6.0.1 on an RCA voyager tablet.
Any additional information I can gather let me know
Anyone experience an issue with WallPanel not updating when an event occurs? After WallPanel has been a sleep and movement wakes it the current status is not correct. The temperature from dark-sky is wrong as well as the status of various sensors.
@quadportnick is WallPanel still being worked on? I’ve used the pre-release (0.7b1) but find it unstable for general use. Will roll back to 0.6 for now but interested in future development.
Unfortunately, I just can’t seem to break away and get into this. Taking forever to do so little isn’t fair, so I’m hoping to find someone(s) to pick this up.
Question, any progress on getting this to work on Android 4.x? Just getting the blank screen with blue bar on top when loading. Have a Lenovo 7" tab I want to reuse for this, but doesn’t seem promising from this thread… Tried both ip and duckdns address, both https as I have let’s encrypt installed.
FYI, if anybody is having the same issues: My Lenovo was apparently running at 5.0.1 Android. I force updated Android WebViewer and ran the latest version of the WallPanel, and it now works flawlessly
Moved from a kiosk browser that was working fine, but wanted the extra options wallpanel has to offer.
However, ive noticed it drains my battery in no time and my 3amp charger cant keep up.
Is there any options i should be changing? i’ve disabled the camera options but still the same.
Any thoughts / tips appreciated…