To control the duet via PS-ON is nothing new.
link text
But to do this via a smart home actuator might be a more current option.

While searching for an actuator I came across the Shelly 2.5
I have chosen it because it brings its own web interface to control. And because it's not cloud bound by default.
There is no nead for a smart home server. So it's already a good option out of the box.

The goal was to be able to switch the printer in such a way that it cannot be accidentally switched off in the middle of printing. Also all loads should be switched off.
The result is the following schematic. (Only the relevant area)

The key is to switch the actuator parallel to the PS-ON relay output.
I use an industrial relay with several channels, this has the advantage that one can switch a separated feedback channel once the duet is booted.
Currently I have 3 channels in use. Power supply, feedback and the heating bed (220V).

The following setting must be made in the switching channel of the Shelly.

Set the button type to "Detached Switch".

Set an "Auto Off" timer for that channel.
With this setting the input switch (SW) can be queried separately.

With this wiring and setting the printer only can be switched off by G-Code.
Either out of the DWC or automatic at the end of printing.
Of course, it also works via a hard-wired kill or main switch.

When everything worked I have been thinking about how to make it more comfortable and to get acoustic feedback.
The drama began seting up a homeserver starting to build a node red dashboard....
To cut a long story short it ended with the integration of G-codes, video image and the activation/deactivation logic.
Still work in progress...
Demo Duet Remote.mp4

@kwad3d-0

@fcwilt is one of the experienced users who really knows this stuff and spends a lot of time helping. But to help he must first understand what the problem is.
I can not get such an attitude ...

Edit:
Yes and sometimes he is also very accurate about terms. But that is certainly not to bother...

@tecno
In the middle right is an arrow which leads to a submenu where you can select it

@joshuamensch
Your files are set up for heater 4, but the Bltouch is wired to heater 3?

@nikscha
Reduce the frequence for the ssr. (Q parameter for heater) I had the same problem.

Edit:
That is my setting
M950 H0 C"bedheat" T0 Q10

@PaulHew said in Maestro, RRF3 and BLTouch issues:

M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch

M558 P9 C"zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin
M950 S0 C"zprobe.mod" ; servo/gpio 0 is Z probe MOD pin

That should be the right code.

You can do that very easily in Prusaslicer.
https://help.prusa3d.com/en/article/insert-pause-or-custom-g-code-at-layer_120490

@printthatthing
Leave it as it is....
You can edit that later on in the config.g

M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
You have to change that to
M950 S0 C"!duex.pwm5"
or rename to
M950 S0 C"exp.heater7"

You will find the full list of heater pin names here
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

@singhm29
In M557 also a P parameter is available.
Witch in my opinion is the easier way to define the mesh grid.
So in you case M557 X5:600 Y47:603 P10:10 as a suggestion
The grid than will be calculated for 10x10 points and the machine will drive to the set limits.

That's a bug, I have already reported.
Let it set to the e1heat. You have to adjust that later on in the config.g

The probe section then should look like that

; Z-Probe
M558 P9 C"zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin
M950 S0 C"zprobe.mod" ; servo/gpio 0 is Z probe MOD pin

Configuration for Ender3
config.json

@tecno
In the middle right is an arrow which leads to a submenu where you can select it

@tecno
Your Z-endstop is set to low end...

M574 Z1 S1 P"io2.in"

Change that to Z2

Edit:
Forget about it.
I mixed it up with the configuration of a bed slinger....

@Marshalldog
You need a camera that can output a mjpeg stream. Some cheap cameras can only stream rstp, but this cannot be displayed directly in the browser (DWC).

@Tryptamine
I also had this problem with my Hypercube at the initial stage.
Try printing smaller circles. The effect should be more noticeable. The shift was diagonal in my case. Based on this, I have concluded that one axis runs with more friction. I then installed higher quality bearings and the problem was solved.

@T3P3Tony
I had actually hoped that there would be some kind of announcements about changes in the documentation. Or the places that have been changed are easier to find.
I always find very well updated info. One notices that you put effort into it.

@oliof said in Is there a work around to restore the old heater fault handling?:

If that isn't correct, the documentation needs some clarification.

It seems that there was a change in the documentation after this post was made.
I just found it by chance. https://docs.duet3d.com/User_manual/RepRapFirmware/Events
Which brings me back to this topic again.

It is a pity that there was no direct answer to this question. At least the behavior is now described understandable for me.
@dc42 If in 3.5 the standard behavior is reintroduced and only optionally the event handling by macro is accessed this would be great.
One point I would still like to consider. For me it seem to make sense to load the event handling macros already into the memory at boot time . And not only be read in case of an error. But in case of a card error, hopefully the standard routine of the firmware would then take effect.

@tecno
It depends strongly on how big the printer should be and how it is equipped.
My desired configuration is all inclusive at 1800€ for a single 500er (of course with Duet Board).
I suspect that your budget in this size is somewhat exceeded.

@tecno
https://lab.ratrig.com/vc31_idex/

@tecno
If you still have some patience, RAT RIG V-CORE - IDEX will come soon as a kit.

@tecno
For the Mini you can shorten CD_LCD and CD_D pin with the jumper.