So the physical buttons can be used to for example change cards.
Maybe have one card for the light and another card for “everything else”.
Would be nice to be able to press the left button for on-screen light control and the right one to access the rest (Here that would be heating and electric curtains and Sonos player in a typical room)
Or…Maybe have the buttons be on/off for the light and then have the rest on the screen ?
Hi
Maybe you could create a thread on https://xdaforums.com for help with developing.
Oldest/biggest site i know for android custom roms …
I think that would speed up things a lot …
thx and greetings.
atleast you get something useful, i get someting that looks like wrong baud rate when using the exact same settings as you.
I have finaly manage to yalebrake my Shelly with the MTK and activat the debug mode. But, whats next? Can some one help me with a easy step by step guide to run HA in kiosk mode or similar?
The goal is to have a HA dascboard one the screen, maby in Chrome or another browser.
Well youll need to figure something, or wait. I plan to do some cool stuff for this device, but very busy nowdays.
Hi! I created a GitHub repository with a detailed guide on how to hack the wall display. Additionally, I wrote a small app that integrates the display with Home Assistant, allowing you to use its relay and run the Home Assistant GUI while still viewing the temperature in Home Assistant.
You can check out the repository here. The guide includes step-by-step instructions and all the necessary files to get started. Enjoy!
Wow … really looking forward to finally be able to use the Wall Display. Do you have some screenshots of the ShellyElevate.apk?
THX
Do you have any progress?
There is now official integration?!! KBOOM!
@solarjunkie Thanks for the info! I installed it and it works great. The only thing that bothers me is the bottom control bar, which you can’t hide…
Does anyone have an idea how to activate the screen of Shelly Wall Display via automation? For example: If movement is detected in the room, then activate the screen.
I tried using JSON-RPC 2.0 commands and was able to use them to toggle the switch, for example. Unfortunately, I couldn’t find a command to activate the screen.
Screen activation on movement:
I asked for a solution in the Shelly community. You can simulate a UI tap in Home Assistant. I wrote the following in configuration.yaml:
rest_command:
my_request:
url: http://Wall-Display-IP/rpc
method: POST
payload: '{"jsonrpc": "2.0", "method": "Ui.Tap", "params": {}, "id": 1}'
content_type: 'application/json; charset=utf-8'
After restarting Home Assistant, you can execute the REST command as an action in an automation.
Does anyone know how to go back to the shelly app as it’s now supporting HA natively? Starting the Shelly app doesn’t work. It’s only flashing up, but then stopping to work. I’ve also tried to enable the service again with
adb root
adb shell pm enable cloud.shelly.stargate
but it doesn’t help
---------20241003
strange, but the second try worked.
After several restarts, the start up screen asked me to set the shelly app as default starter.
Great. Was really looking for this! Thank you!
One remaining question on my side:
Is this working if Authentication is enabled at the WallDisplay?
If not: Can you help me how to modify the code?
Thank you, a lot!
This is my current output:
content:
code: 401
message: >-
{"auth_type":"digest","nonce":1728212829,"nc":"1","realm":"ShellyWallDisplay-00082248CFE8","algorithm":"SHA-256"}
status: 401
I don’t know how to include the digest authentication and I don’t really understand the corresponding Shelly API documentation.
OK, thank you! So you do not have authentication activated with your WallDisplay, right?
No, I have not activated authentication
If anyone is interested: Could realize it using shell command.
shell_command:
wakeupwalldisplay: >-
curl --digest -u admin:<password> 'http://<IPofWalldisplay>/rpc/Ui.Tap?x=300&y=300'
Hi. I bought a new Wall Display to use it with the new integrated HA dashboard function.
Therefore I have to update it from FW 1.2.5 zu 2.x (beta).
I have no clue how to do it. The device is in my network with a fix IP and I can connect to the web UI.
When I search for Updates in both (device or web UI) it says that 1.2.5 is the latest. No option to go to FW 2 or a beta.
Can some one point me the way?
So, the answer from Shelly Support: As of FW 2.x, static IP is no longer supported. So you have to uncheck the box for static IP in version 1.2.5 (which is not easy because the setting is not saved. I then deactivated the WiFi 1 connection and continued with WiFi 2. Later it jumped back to WiFi 1 - all very strange). Finally, when DHCP was set and restarted, I was able to select 2.3.0 beta3 under Firmware. They just don’t have their software under control, but well - so be it.
Then I was able to initiate the further upgrade under Settings → Network → Home Assistant and when that was done, I was able to select the server again under Home Assistant and connect to a user.
Now a small HA dashboard is running on the WD. Nice!