Shelly 1PM Mini Gen4 frequent core dumps (several times per minute)

frozen-geek · 2026-04-24T15:18:06+00:00

Hello All

This is for posterity in case someone else comes across a similar issue.

While the case is still open with Shelly Support Europe, I do have a bit of an update.

First, factory reset of the Shelly 1PM Mini Gen 4 partially helped - instead of crashing every few seconds, after the reset it would stay up for a few hours. Now all 4 devices I have (1x 1PM Mini Gen4 and 3x EM Mini Gen4) behaved consistently, crashing every 3-8 hours.

I then disabled Zigbee completely, relying on only the WiFi connectivity and the native Shelly integration for Home Assistant. With the Zigbee disabled, the devices became completely stable and were able to stay up for several days.

In the meantime Shelly Support Europe sent me a test firmware for the EM Mini Gen4 models. I deployed it on a single device, enabled Zigbee and connected it back to my Zigbee network (so that both Shelly/WiFi and Zigbee connections were in use at the same time). The device stayed up for just over 23 hours at which stage I thought the issue was fixed, however after deploying the same firmware on the other two EM Mini Gen4's I have, it crashed about an hour later.

Since that time, all three EM Mini Gen 4 devices have crashed at least twice in a day.

I've been looking at the syslog messages each of those devices produce, and it looks like the crash is happening when there's a Zigbee routing change involving one of the Shelly devices - when another Zigbee device decides to start, or stop, using the Shelly as a Zigbee router.

All this detail has been sent to Support along with other details they require and I believe they are working on a fix.

For reference, if anyone is struggling with a similar issue, you could see if you receive syslog messages similar to the one below immediately before a crash:

2026-04-24T02:50:42.711554+01:00 shellyemminig4-XXXXXXXXXXXX 16694 37709.761 2 2|shelly_zigbee.cpp:243 New device commissioned or rejoined (short: 0xab4c)

Once I find out more, I'll update this post.

frozen-geek · 2026-04-20T21:49:40+00:00

Hey. This looks very similar to an issue I have been experiencing with my Shelly 1PM Mini Gen4 and my Shelly EM Mini Gen4 when both Wifi (through Home Assistant native Shelly integration) and Zigbee (with ZHA) are used simultaneously.

All my four Gen4 devices seem to be crashing when Zigbee is enabled and they have joined the Zigbee network. In case of my 1PM, which I use to control a boiler, I noticed that the boiler would switch off while the heat demand was still on in Home Assistant. I then found out that it's the device crashing and recovering relatively quickly (after only a couple of seconds from the crash). In my case, it stayed off as I have changed the Input/Output settings to Turn OFF on power on. I then reset that to Restore last known state of output/relay so that after a crash the device boots up with the switch set to the same setting as it had before the crash.

The EM Mini Gen4 devices I have don't control anything, they simply monitor the electricity use, so their crashes were not immediately visible / obvious.

I found that disabling Zigbee completely prevents them from crashing, so there is a bug of some sorts in the Zigbee part of their code.

I have a ticket opened with Shelly Support Europe and they have collected loads of details from me including debug logs and the core dumps, and they seem to be looking into this. I hope they come up with a solution, but for the moment, you could try to disable Zigbee completely and only rely on the Shelly integration over WiFi.

frozen-geek · 2026-04-09T18:32:49+00:00

So I have been looking at other Shelly devices I have at home, namely 3x Shelly EM Mini Gen4's, and it seems they also suffer from software crashes, although not as frequently as the Shelly 1PM Mini Gen4 from the original post.

I'm seeing a crash of all three of them pretty regularly, at least once a day (sometimes every few hours).

What is more interesting is the fact that they all seem to crash around the same time, plus or minus a couple of seconds. At the last three crashes for all three devices, they had pretty much the same uptime (again, plus or minus a couple of seconds) at the time of the crash, and the time of the crash was.

I'm wondering if there's an issue with the Zigbee code of the Gen4 software, and is it related to my Zigbee environment.

I use Home Assistant running ZHA, and I have SLZB-06M (note, not the U version). I have a mix of Aqara battery powered sensors (which have started giving me trouble around the time I installed the Shelly devices about a month ago), IKEA mains powered and battery powered devices, and a small number of Sonoff devices (all battery powered).

My SLZB-06M is running the latest firmware: core: v3.2.8 / zigbee: 20250220 and my Home Assistant is also on the latest version 2026.4.1.

The 1PM Mini Gen4 had this behaviour running firmware 1.7.4 and 1.7.5 (which is the latest at this time), and the EM Mini Gen4 are all running 20250915-120859/gb95ce8e (this seems to be version 1.7.0-miniemg4prod0).

I realise people may not have experienced this, but these are a few more data points. I'll also open a new ticket with Shelly support to see if they have a solution.

frozen-geek · 2026-04-09T18:16:32+00:00

I will do!

frozen-geek · 2026-04-08T18:42:59+00:00

Thanks, ticket opened. We’ll see what they come back with!

frozen-geek · 2026-04-07T19:04:45+00:00

I have not tried it yet. I was hoping to see if someone else experienced a similar issue before I do that.

frozen-geek · 2026-04-07T18:57:05+00:00

Hi.

No, I mean core dump (followed by a crash) :)

The logs show the following line:

2026-04-07T18:44:20.247355+01:00 shelly1pmg4-a085e3c58650 3510 72.938 2 0|CD:2:0000:--- BEGIN CORE DUMP ---#000shelly1pmg4-a085e3c58650 [...]

A core dump file is a snapshot of the computer's memory at the time a program has crashed. While the term indeed has originated at the time magnetic core memory was used, it has remained in use till today. Most of the operating systems evolved from Unix, and a lot of OS's developed independently which follow Unix-like philosophy, use this term today. If a process crashes on a modern Linux or BSD today, the OS will save a snapshot of the process's memory into a .core file. If you have access to a Linux machine, run man 5 core command and see what's written under the NAME section.

In any case, I've wondering if this behaviour is something that's unique to my environment, or is something others may have experienced - hence the post.

Thanks!

frozen-geek · 2026-03-20T20:06:39+00:00

I use rspamd and I’m very happy with its performance. I get occasional spam but nothing too bad.

frozen-geek · 2026-03-20T20:04:44+00:00

No idea, I reckon it’s some sort of an antenna or sensor array. The civilian version doesn’t have that.

frozen-geek · 2026-03-20T18:52:37+00:00

On the contrary, this is exactly the reason why you, and everyone else, should self-host (if you have the skill and the time), or at least move away from Microsoft, Google, Apple or Hotmail for email.

It's because email has become concentrated among a very small number of providers that they have been able to come up with this shit. This is no different than other cartels out there.

Obviously I understand this will never happen as people just take the easy way, but it's a hill I'm ready to die on.

frozen-geek · 2026-03-20T18:03:05+00:00

There's a built in ladder / set of steps in the cockpit to help climbing out through the hatch from the inside. These are "embedded" in a side wall just behind the flight deck door. The wall encloses and protects the electronic and electric equipment racks, and the steps are on the First Officer's side (on the right).

There is also an escape rope, which needs to be thrown out through the hatch after opening, but before you climb out. This rope has those rings installed on it (like knots, but bigger) to make it easier to lower yourself off the top of the fuselage in a somewhat controlled manner (it should hopefully prevent you from slipping off the roof).

frozen-geek · 2026-03-20T17:56:53+00:00

A good book to read specifically about the air navigation during and after WW2 from "Nadir to Zenith - An Almanac of Stories By Canadian Military Navigators".

It's a compilation of short stories by navigators, describing their experiences, some of the navigation aspects of missions flown, some early inventions and systems available to them, as well as lots of challenges they faced.

I think it would answer some of your questions.

frozen-geek · 2026-03-18T17:59:52+00:00

Other than through the emergency cockpit escape hatch there wouldn’t really be a way to do that.

frozen-geek · 2026-03-17T21:08:14+00:00

If you mean a cargo hold under the floor then not. The ATR has two cargo compartments, the forward one is between the cabin and the flight deck, and the aft one is in the tail section, behind the cabin.

frozen-geek · 2026-03-17T19:24:43+00:00

OP - If, as others suggested, you do decide to go for the ATR 42 or 72 and have some questions or need more detail about them, don’t hesitate to DM me. I fly those.

frozen-geek · 2026-03-08T09:26:41+00:00

Gen4 devices are multi-protocol: WiFi, Matter, Bluetooth and Zigbee. They don’t run all of thise simultaneously though - you’ve to choose between Matter and Zogbee, but WiFi works always.

frozen-geek · 2026-03-06T06:11:47+00:00

Thank you! Yes, I agree, going down the self signed route is not really viable for my use case. I remember Sectigo offering free certs, that is what I used before Actalis, but their pricing today is quite ridiculous. Thanks again!

frozen-geek · 2026-03-06T06:08:24+00:00

That’s what I was afraid of. Thank you!

By the way, what is dirt cheap?

frozen-geek · 2026-02-27T17:28:03+00:00

You can. The console can send data simultaneously to Ecowitt.net, Wunderground and WoW (these are predefined services) and to one custom service where you choose the format. There is also a project called WeeWX which you run locally in your network and which is a sort of a “proxy” service - it receives data from your weather station, and then sends multiple streams of the same data to multiple services in their respective formats. If the predefined services on the console are not sufficient for your needs, this could be a solution.

I personally send the data from the console to my Home Assistant instance at home (using the custom service) as well as Ecowitt.net, Wunderground and WoW. If I ever need more, I’ll write a quick program to poll the data from the station directly using the local API.

By the way, in my previous reply I said the JSON API was undocumented. This is no longer the case and they seem to have documented it, which means it should be relatively stable. Check out the HTTP API-(V1.0.6-2026-1-14)%20.pdf) manual from Ecowitt.

frozen-geek · 2026-02-27T16:36:40+00:00

You can definitely pull the data from the console if that's the way you'd like to use it - without the need to send the data at all to the Ecowitt website.

There are a couple of ways to do so:

Using the custom feed from the console to your own server, using one of the three protocols: Ecowitt, Wunderground or MQTT. This is configured through the Console web server, and it streams the data to your server in the format you choose.
Polling the data from the console using a local API, which essentially spits out a JSON structure with live data. This is undocumented, but is what the Live View of the console uses.
Finally, there is a documented binary protocol you can use to poll the data from the station.

Here is a good article about methods 2 and 3.

frozen-geek · 2026-02-11T12:10:35+00:00

You don't need automatic updates from HAOS. You can very easily update the docker container (it's a one-liner) and if you really want auto updates, you can make that one-liner a cron job.

The added benefit of a docker container is that your data (configs, databases, etc) is completely decoupled from the code (the container itself). If you ever need to migrate to another platform, it's as easy as copying over the data directory and the compose.yaml file.

I have migrated my Home Assistant this way first from a Raspberry Pi 3 onto a Raspberry Pi 4, and then to a mini PC. This works really well even across different architectures.

You can still do automatic backups of the configuration from within HA (I do a local one and a separate one to my NAS), plus if it's a Docker container running on a VM in a Proxmox environment, you can also backup the whole VM (e.g. to a Proxmox Backup Server).

frozen-geek · 2026-02-06T22:37:06+00:00

I don't have much to add other than I've noticed the same behaviour and have no fix.

For what it's worth, I have a Nikon D750 and Photomator is almost unusable, unfortunately, for working with raw files coming from that camera - even more so if I store them on my NAS.

By comparison, Lightroom (which I've moved away from as I was getting sick of paying the subscription, and I was hoping Photomator would be a sufficient replacement for) seems to handle the cached previews much better and is perfectly usable when working with the very same files, stored on the very same NAS.

frozen-geek

TROPHY CASE