# Shelly 1PM Gen2 has no "mqtt\_update\_periode"?

**URL:** <https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146>\
**Category:** General\
**Tags:** mqtt\
**Created:** [13 December 2022 17:25 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146 "2022-12-13T17:25:58Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [13 December 2022 17:25 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/1 "2022-12-13T17:25:58Z")

</div>

Hello!

**Question:**  
Can I set the update interval for status message in shelly 1pm Gen2 like in Gen1?

**Additional infos:**  
I've managed to implement my shelly 1pm into node-red.  
With the xx/status/switch:0 I get nearly every second a update:

```auto
{"id":0,"source":"MQTT","output":true,"apower":142.1,"voltage":232.7,"current":0.699,"aenergy":{"total":123.414,"by_minute":[1029.85,2084.317,2243.308],"minute_ts":1670951908},"temperature":{"tC":37.2,"tF":98.9}}

```

I saw in the Gen 1 Docs, that there is a setting -\> mqtt\_update\_periode. Because in my flow I get every second an update - this is way too much!  
Is there something similar for the gen2

> **[Welcome! | Shelly Technical Documentation](https://shelly-api-docs.shelly.cloud/gen2/)**
>
> The second generation of Shelly devices, called Shelly-NG, is finally here. These devices use faster processor, have more memory, and perform better than the classic Shelly devices. They support Bluetooth Low Energy feature which makes the task of...

Thanks for your help.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [13 December 2022 17:43 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/2 "2022-12-13T17:43:30Z")

</div>

You can use scripts on shelly gen 2 devices, not tried as do not have any gen 2 yet.  
[Generate periodic messages](https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Mqtt/#step-10-generate-periodic-updates-over-mqtt-using-shelly-script)

> **[Script | Shelly Technical Documentation](https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Script/)**
>
> Since version 0.9.0

---

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [13 December 2022 18:03 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/3 "2022-12-13T18:03:22Z")

</div>

Thanks for your reply.

But as far as I can see, is this just a periodic message (yes I could make HTTP-Requests...). All these things I can fullfil within in nodered.

Greetings

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [13 December 2022 18:17 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/4 "2022-12-13T18:17:32Z")

</div>

Yes a periodic message of what ever info you wish to send, you can create any script you wish.

Maybe I am not understanding your request

If you require notifications when things have changed [Notifications | Shelly Technical Documentation](https://shelly-api-docs.shelly.cloud/gen2/General/Notifications)

---

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [13 December 2022 18:41 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/5 "2022-12-13T18:41:42Z")

</div>

I'm getting the status on the standard topic ../status/switch:0

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/c/6c8ea4d4a2083a5ca04d1448d82b6afe996a549b.png)

Everything works fine BUT! I got the message every SECOND! I'm sure this could be changed - as in GEN1 with "mqtt\_update\_periode" but I'm not able to find in the docs....

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [13 December 2022 19:30 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/6 "2022-12-13T19:30:07Z")

</div>

As said I do not have a device, I cannot find any info in gen2 docs that show the `../status/switch:0` topic.  
As far as i have read Shelly GEN2 try to limit network chatter.  
So it publishing status every second seems strange to me.  
I thought GEN2 MQTT uses `<shelly-id>/rpc` topics and commands and data where json, except notifications which are `<shelly-id>/events/rpc`, and for periodic status updates you would use scripts.

---

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [14 December 2022 06:34 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/7 "2022-12-14T06:34:29Z")

</div>

Thanks again for your reply - really appreciate it!

In the docu under ShellyPlus1PM you can find the topic "switch:0" - and I catched this topic with MQTT Explorer.

> **[Shelly Plus 1 PM | Shelly Technical Documentation](https://shelly-api-docs.shelly.cloud/gen2/Devices/ShellyPlus1PM/)**
>
> Shelly Plus 1 PM is a one-channel device with a wide range of functionalities. The channel supports the use of automatic timers, webhooks, and schedules. The device has a built-in power meter to instantaneously measure the power and energy consumed...

I also read that GEN2 try to limit network chatter - and sending every second those messages are exactly the opposite 😃 And the problem - also when I'm implementig scripts... shelly will sent this message nevertheless

okay, than I will try the scripts and create my own "status" infos

edit: also on the topic "myshelly/events/#" I get every second a message...  
Over the dayit is ~ 17MB: JSON has ~ 200B \* 60 \* 60 \*24 ~ 17 mb on traffic

Greetings

---

<div class="post-metadata">

**Author:** ![piwi447](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/piwi447/32/67335_2.png) [@piwi447](https://discourse.nodered.org/u/piwi447)\
**Post date:** [14 December 2022 07:41 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/8 "2022-12-14T07:41:33Z")

</div>

Hello,  
I got recently some gen2 Shelly but not the 1pm  
The documentation is optimized in the way they reduce number of page of website but it does not help to see which setting are really available on each device type.  
The network chatter reduction seems to apply more on the battery powered device, not sure if the 240V AC powered device have this option.  
I would advice to check in the rpc status, which wake\_up reason is given.  
There are wake up period parameter but I am not sure, as said before, that they apply in case of AC supply.

Pierre RUWET

---

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [14 December 2022 08:26 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/9 "2022-12-14T08:26:22Z")

</div>

Interessting - according to the docs the last two items of Sys.GetStatus should have "wakeup\_reason" and "wakeup\_period"  
([System | Shelly Technical Documentation](https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Sys#configuration))

I haven't both of them

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/7/872df356deda601116923d1b2801c05e6e9e703a.png)

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [14 December 2022 09:05 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/10 "2022-12-14T09:05:50Z")

</div>

Right above that section is says  
`Information about boot type and cause (only for battery-operated devices)`

---

<div class="post-metadata">

**Author:** ![escapist3734](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@escapist3734](https://discourse.nodered.org/u/escapist3734)\
**Post date:** [14 December 2022 09:10 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/11 "2022-12-14T09:10:54Z")

</div>

My Second Shelly 1PM hasn't this behaviour - also a factory reset hasn't changed the mass flood on mqtt message... Whatever

So I switched to the second one and there everything looks good:

With ../rpc Topic and method "Switch.GetStatus" I get all my desired Infos.

Thank you all for your inputs!  
Greetings

ps.:  
found it - uncheck both notification and everything is good!  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/9/995bd5563ac4db8a42741b5718c85002a24774ea.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [28 December 2022 09:11 UTC](https://discourse.nodered.org/t/shelly-1pm-gen2-has-no-mqtt-update-periode/72146/12 "2022-12-28T09:11:52Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.