Jump to content
NOTICE / HINWEIS: iOS 18 Update and Today Widgets ×

Home Assistant in Wall Display


Recommended Posts

Dear friends,

We are happy to announce that Home Assistant has finally arrived to the Wall Display screen! Here are the steps to integrate HA on your screen:

 

  1. Update to the latest 2.3.0-beta firmware;
  2. Open Settings -> Network and tap on "Home Assistant";
  3. You will be prompted to update your device to get ready for Home Assistant. You will not be able to use Home Assistant on your Wall Display until you update. Tap "Yes" and wait a few minutes - it's a large update and will take some time, but this is done only once;
  4. After the update go to Settings -> Network and tap "Home Assistant" again. You will be presented with a list of discovered HA servers;
  5. You can edit the address to point to a specific dashboard, enable kiosk mode, etc.;
  6. If your server can not be found (different VLAN, etc.), you'll have the option to enter your HA address manually - enter the full HA address there (e.g. http://192.168.7.165:8123/dashboard-walldisplay?kiosk);
  7. Toggle the instance you want to integrate into your screen;
  8. Tap "Save" and the device will perform a soft reboot to set up the pages;
  9. As with other Wall Display pages, swipe-from-top will bring out a toolbar where you can refresh the page or go back;
  10. Before you ask, no, the bottom bar and swipe left/right gestures are core features and will not be modified.

 

Enjoy and show off with your cool dashboards here. You can take screenshots off your Wall Display screen by opening "http://DEVICE_IP/screenshot" in your browser (e.g. http://192.168.7.4/screenshot).

 

N.B.: It's recommended to log in with a non-admin, local only user, enable kiosk mode, and create a separate lightweight dashboard specifically for your Wall Display. While the large update installs the latest compatible WebView on your device, complicated dashboards will still load slowly and may behave erratically.

N.B.2: The security on the Wall Display is pretty tight. Therefore HA instances with fake SSL (self-signed, duckdns, etc.) will not work. Please set up a proper SSL certificate with a locally resolved domain name in order to use HA with https. Thanks to the guys at LetsEncrypt, you can do it absolutely for free. Here's a nice guide: Setting up HTTPS for HA.

 

Here are some screenshots to get you going:

image.png.b8b3e9610e96e280e637fd2c9aefb4f0.png

 

image.png.e0393eec82a89fe385f8ecfbde436454.png

 

Link to comment
Share on other sites

  • Members

When I try to install the beta I get an error:

[01:20:08] [Generic]: - CURRENT: 240831126-2.2.1-eb899af6, {"version":"2.2.1","build_id":"20240831-114811\/2.2.1-eb899af6","build_number":20240831114811,"commit":"eb899af6","beta":"","stage":"stable","v_inc_i":131585,"v_inc_b":"020201","url":""}
[01:20:08] [Generic]: Firmware update check response: {"beta":{"version":"2.3.0-beta1","build_id":"20240920-135008\/2.3.0-fecb4f7b-beta1","url":"https:\/\/updates.shelly.cloud\/fw\/WallDisplay\/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613"}}
[01:20:08] [Generic]: - STABLE: , none
[01:20:08] [Generic]: - BETA: , {"version":"2.3.0","build_id":"20240920-135008\/2.3.0-fecb4f7b-beta1","build_number":20240920135008,"commit":"fecb4f7b","beta":"beta1","stage":"beta","v_inc_i":131840,"v_inc_b":"020300","url":"https:\/\/updates.shelly.cloud\/fw\/WallDisplay\/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613"}
[01:20:11] [Generic]: --> Downloading OTA from https://updates.shelly.cloud/fw/WallDisplay/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613
[01:20:11] [Cloud]: The exception that was caught while verifying O=Allterco's certificate was CertPathValidatorException: timestamp check failed
[01:20:11] [Network]: Posting everywhere: {"src":"ShellyWallDisplay-000822EF08A6","dst":"user_1","method":"NotifyEvent","params":{"ts":1262305211,"events":[{"component":"sys","event":"ota_error","msg":"Certificate validation failed","progress_percent":0,"ts":1262305211536}]}}

 

Edited by Bieniu
Link to comment
Share on other sites

18 hours ago, Bieniu said:

When I try to install the beta I get an error:

[01:20:08] [Generic]: - CURRENT: 240831126-2.2.1-eb899af6, {"version":"2.2.1","build_id":"20240831-114811\/2.2.1-eb899af6","build_number":20240831114811,"commit":"eb899af6","beta":"","stage":"stable","v_inc_i":131585,"v_inc_b":"020201","url":""}
[01:20:08] [Generic]: Firmware update check response: {"beta":{"version":"2.3.0-beta1","build_id":"20240920-135008\/2.3.0-fecb4f7b-beta1","url":"https:\/\/updates.shelly.cloud\/fw\/WallDisplay\/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613"}}
[01:20:08] [Generic]: - STABLE: , none
[01:20:08] [Generic]: - BETA: , {"version":"2.3.0","build_id":"20240920-135008\/2.3.0-fecb4f7b-beta1","build_number":20240920135008,"commit":"fecb4f7b","beta":"beta1","stage":"beta","v_inc_i":131840,"v_inc_b":"020300","url":"https:\/\/updates.shelly.cloud\/fw\/WallDisplay\/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613"}
[01:20:11] [Generic]: --> Downloading OTA from https://updates.shelly.cloud/fw/WallDisplay/32200e2038a7c9200146d321b1f8edb38a4ba77095dd7f5d7de5cf56e144a613
[01:20:11] [Cloud]: The exception that was caught while verifying O=Allterco's certificate was CertPathValidatorException: timestamp check failed
[01:20:11] [Network]: Posting everywhere: {"src":"ShellyWallDisplay-000822EF08A6","dst":"user_1","method":"NotifyEvent","params":{"ts":1262305211,"events":[{"component":"sys","event":"ota_error","msg":"Certificate validation failed","progress_percent":0,"ts":1262305211536}]}}

 

Did you try again after some time or after a full reboot?

Link to comment
Share on other sites

  • Members
1 hour ago, Dimitar Buckoff said:

Did you try again after some time or after a full reboot?

Many times. Today I managed to install the beta by connecting the Wall Display to a hot spot on my mobile. Now I tried to update to beta2 and the exact same problem, hot spot to the rescue.

Link to comment
Share on other sites

2 minutes ago, Olsche said:

Either directly via the display in the Settings -> General -> About Device -> Check for Updates or via WEB-UI

firmware version 1.2.3-hotfix2
firmware id 20231023-111637/1.2.3-580131e2-hotfix2
You are using the latest version of the firmware. Check again.
Link to comment
Share on other sites

10 hours ago, Hawaflawo said:

Very cool,

 

how can I get smaler gauge? 2 or 3 in a row?

 

Use the Horizontal Stack card. With that and the Vertical Stack card, you can come up with some complex layouts. This one is a Horizontal Stack with two Vertical Stacks on pages two and three.

image.thumb.png.f2f37eb90c0684687bf696157cf2e9b9.png

Edited by bollar
Link to comment
Share on other sites

Hello, 

Really exited about this update! The firmware update to the beta version went fine. 

I can see the home assistant settings and search for a home assistant instance. 

The panel finds the http://xxx.xxx.x.x:8123/ instance (local http address). But i get the message "ERR_EMPTY_RESPONSE" in the home assistant screen.

When i change the address to https://mydomain.duckdns.org:8123/ i get the "No valid HA instance found on....", i tried different addresses (http and https) but noting seems to work. 

Any help would be great!

Regards

Martin

Link to comment
Share on other sites

8 hours ago, MartinShelly said:

Hello, 

Really exited about this update! The firmware update to the beta version went fine. 

I can see the home assistant settings and search for a home assistant instance. 

The panel finds the http://xxx.xxx.x.x:8123/ instance (local http address). But i get the message "ERR_EMPTY_RESPONSE" in the home assistant screen.

When i change the address to https://mydomain.duckdns.org:8123/ i get the "No valid HA instance found on....", i tried different addresses (http and https) but noting seems to work. 

Any help would be great!

Regards

Martin

Have you tried https://mydomain.duckdns.org:443/ ?

Link to comment
Share on other sites

18 hours ago, bollar said:

Unfortunately also the same issue with port 443. Does anyone has anymore luck with the duck DNS domain and the wall panel? Is there also a possibility in home assistant to use a local address with HTTP? Because the panel itself detects the home assistant instance with the http://xx.xx.xx.xx:8123/ adress.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...