<?xml version="1.0"?>
<rss version="2.0"><channel><title>Shelly control panels Latest Topics</title><link>https://community.shelly.cloud/forum/180-shelly-control-panels/</link><description>Shelly control panels Latest Topics</description><language>en</language><item><title><![CDATA[WallDisplay 2.6.0 Beta – Experiences & Feedback Topic]]></title><link>https://community.shelly.cloud/topic/14090-walldisplay-260-beta-%E2%80%93-experiences-feedback-topic/</link><description><![CDATA[<p>
	Experiences &amp; Feedback Topic for announcement: <a href="https://community.shelly.cloud/announcement/38-walldisplay-firmware-260-beta-released/" rel="">https://community.shelly.cloud/announcement/38-walldisplay-firmware-260-beta-released/</a>
</p>

<p>
	If you have any experiences or issues, please share them here in this thread.<br />
	We look forward to your feedback...
</p>
]]></description><guid isPermaLink="false">14090</guid><pubDate>Wed, 15 Apr 2026 12:26:12 +0000</pubDate></item><item><title>ToDo: RPC-Call for Scheduled Reboot</title><link>https://community.shelly.cloud/topic/9448-todo-rpc-call-for-scheduled-reboot/</link><description><![CDATA[<p>
	In this tutorial, we will show you how to perform a complete reboot of the Walldisplay via a schedule created using an RPC call.
</p>

<p>
	This can help if the display occasionally goes offline due to unfavorable network configurations, for example.
</p>

<p>
	Follow the instructions to improve the stability of the device:
</p>

<p>
	 
</p>

<p>
	<strong>Daily schedule for full reboot:</strong>
</p>

<p>
	One solution would be to have a daily full reboot triggered on a schedule. The correct RPC call for a full reboot schedule is:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.Create?timespec=0 0 3 * * *&amp;calls=[{"method":"Shelly.Reboot"}]&amp;enable=true</span></pre>

<p>
	In the example shown here, a daily reboot at 3:00 a.m. is selected.
</p>

<p>
	timespec: as defined by <a href="https://github.com/mongoose-os-libs/cron" rel="external">cron</a>. Note that leading zeros are not supported (e.g. for 8 a.m. you should enter <code>8</code> instead of <code>08</code>).
</p>

<p>
	 
</p>

<p>
	The created schedule can be seen via this call:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.List</span></pre>

<p>
	JSON output:
</p>

<p>
	<img alt="image.png.7ccdd0e257c9afab0f9e4e9a33c57b01.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7628" style="height:auto;" width="252" src="//media.invisioncic.com/t323932/monthly_2025_04/image.png.7ccdd0e257c9afab0f9e4e9a33c57b01.png" loading="lazy" height="191.52">
</p>

<p>
	 
</p>

<p>
	<strong>Other useful information: RPC URL:</strong>
</p>

<p>
	Delete all schedules:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.DeleteAll</span></pre>

<p>
	Delete a selected schedule:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.Delete?id=SCHEDULE_ID</span></pre>

<p>
	<em>the SCHEDULE_ID can also be found under Schedule.List:</em>
</p>

<p>
	<img alt="image.png.309ca84fb829fe1d20e8c4c272e274ad.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7630" style="height:auto;" width="192" src="//media.invisioncic.com/t323932/monthly_2025_04/image.png.309ca84fb829fe1d20e8c4c272e274ad.png" loading="lazy" height="21.12">
</p>

<p>
	 
</p>

<p>
	<strong>Additional information:</strong>
</p>

<p>
	The URL or RPC call must be entered in the address bar of the browser. To do this, you must be in the same network as the WallDisplays:
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="png" data-fileid="7629" href="//media.invisioncic.com/t323932/monthly_2025_04/image.png.60609c9bae58e0181789f434db11d799.png" rel=""><img alt="image.thumb.png.9dfa735b516813a10741e35225ffb286.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7629" style="height:auto;" width="1000" src="//media.invisioncic.com/t323932/monthly_2025_04/image.thumb.png.9dfa735b516813a10741e35225ffb286.png" loading="lazy" height="30"></a>
</p>

<p>
	-instead of <b><i>IP_WD</i></b>, the IP address of the WallDisplay assigned by the router must be entered here
</p>

<p>
	-instead of <b><i>SCHEDULE_ID</i></b>, the ID from the Schedule.List must be entered here
</p>

<p>
	 
</p>

<p>
	-------------------------------------------------------------------------------------------------------------
</p>

<p>
	 
</p>

<p>
	In diesem Tutorial zeigen wir dir, wie du einen vollständigen Reboot des Walldisplays über eine per RPC-Call erstellte Schedule (Zeitplan) durchführen kannst.
</p>

<p>
	Dies kann helfen, wenn das Display z.B. aufgrund ungünstiger Netzwerkkonfigurationen gelegentlich offline geht.
</p>

<p>
	Folge bitte den Anweisungen, um die Stabilität des Geräts zu verbessern:
</p>

<div>
	<p>
		 
	</p>

	<p>
		<strong>Täglicher Zeitplan für Full-Reboot (vollständiger Reboot):</strong>
	</p>

	<p>
		Eine Lösung wäre ein täglicher vollständiger Neustart, der nach einem Zeitplan ausgelöst wird. Der korrekte RPC-Call für einen Zeitplan für einen vollständigen Neustart lautet:
	</p>
</div>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.Create?timespec=0 0 3 * * *&amp;calls=[{"method":"Shelly.Reboot"}]&amp;enable=true</span></pre>

<div>
	<p>
		Im hier gezeigten Beispiel wird ein täglicher Neustart um 3:00 Uhr nachts ausgewählt.
	</p>

	<p>
		<strong>timespec:</strong> wie von <a href="https://github.com/mongoose-os-libs/cron" rel="external">cron</a> definiert. Beachte, dass führende Nullen nicht unterstützt werden (z. B. solltest du für 8 Uhr morgens <code>8</code> statt <code>08 </code>eingeben).
	</p>

	<p>
		Der erstellte Zeitplan ist über diesen Aufruf zu sehen:
	</p>
</div>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.List</span></pre>

<div dir="ltr">
	 
</div>

<div dir="ltr">
	JSON-Ausgabe:
</div>

<div dir="ltr">
	 
</div>

<div dir="ltr">
	<img alt="image.png.7ccdd0e257c9afab0f9e4e9a33c57b01.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7628" style="height:auto;" width="252" src="//media.invisioncic.com/t323932/monthly_2025_04/image.png.7ccdd0e257c9afab0f9e4e9a33c57b01.png" loading="lazy" height="191.52">
</div>

<div dir="ltr">
	 
</div>

<div dir="ltr">
	 
</div>

<div dir="ltr">
	<strong>Weitere nützliche RPC-URL:</strong>
</div>

<div dir="ltr">
	 
</div>

<div dir="ltr">
	Alle Zeitpläne löschen:
</div>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.DeleteAll</span></pre>

<div>
	                
</div>

<div dir="ltr">
	Einen ausgewählten Zeitplan löschen:              
</div>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">http://IP_WD/rpc/Schedule.Delete?id=SCHEDULE_ID</span></pre>

<div>
	                
</div>

<div dir="ltr">
	<em>die SCHEDULE_ID kann ebenfalls unter Schedule.List gefunden werden:</em>
</div>

<p>
	<img alt="image.png.309ca84fb829fe1d20e8c4c272e274ad.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7630" style="height:auto;" width="192" src="//media.invisioncic.com/t323932/monthly_2025_04/image.png.309ca84fb829fe1d20e8c4c272e274ad.png" loading="lazy" height="21.12">
</p>

<p>
	<strong>Zusatzinformationen:</strong>
</p>

<p>
	Die URL bzw. der RPC Call muss in die Adresszeile des Browsers eingetragen werden. Voraussetzung ist, man befindet sich im selben Netzwerk wie auch die WallDisplays sich befinden:
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="png" data-fileid="7629" href="//media.invisioncic.com/t323932/monthly_2025_04/image.png.60609c9bae58e0181789f434db11d799.png" rel=""><img alt="image.thumb.png.9dfa735b516813a10741e35225ffb286.png" class="ipsImage ipsImage_thumbnailed" data-fileid="7629" style="height:auto;" width="1000" src="//media.invisioncic.com/t323932/monthly_2025_04/image.thumb.png.9dfa735b516813a10741e35225ffb286.png" loading="lazy" height="30"></a>
</p>

<p>
	-anstelle <strong><em>IP_WD</em></strong> muss hier die vom Router vergebene IP-Adresse des WallDisplay eingetragen werden
</p>

<p>
	-anstelle <strong><em>SCHEDULE_ID</em></strong> muss hier die ID aus der Schedule.List eingetragen werden
</p>
]]></description><guid isPermaLink="false">9448</guid><pubDate>Thu, 03 Apr 2025 10:20:44 +0000</pubDate></item></channel></rss>
