@Goss66 The fact that the LED is still fading in and out indicates that the communication between the RPi and the PowerBlock is not working for some reasons. It the the PowerBlock driver on the RPi that signal that the driver is loaded. In that moment the LED that is attached to the PowerBlock should change to a steady state.

Do you have other peripherals connected to the RPi? Or other device drivers that might interfere with the PowerBlock driver?

@blacknell Hi! I have just replied to your email.

Generally, the default PowerBlock firmware does not return to the previous power state upon power loss. However, I did work on this feature some months ago and I built an updated firmware version for the PowerBlock that contains this feature: Upon switch on, the PowerBlock persists the ON state as target state. When in ON state and a power button switch off event is observed the OFF state is persisted as target state. When a power-reset event occurs the PowerBlock returns to the previously persisted target state.

If you have a programmer for the ATTiny85 microcontroller on the PowerBlock you could just download this other firmware.

I am happy to provide this firmware upon request. New batches of the PowerBlock might get this firmware per default, eventually.

@BigBadHodad Please open a new topic and add more details about your setup.

@suleske I found several inexpensive and simple circuits I could build. This little board has some added features (e.g. setting the key press switch delay), so I bought it: https://www.ebay.com/itm/262199569276

@ebtalk If it did not overheat after you physically attached the button and the behaviour only started after the script was installed then that is your issue. Remove the script. Reboot and see what happens. Then re-initialise the script. If it is the script then remove it and start again. To be honest it should work or not. It just sends a sudo shutdown -h now command to the Pi. Just seems very odd behaviour. Maybe find another script and compare the two.