Skip to content

First time my home cooking didn't trigger the smoke detector

Off Topic by steveipw 7 replies 967 views
8 #1

Pan-seared salmon, 4 minutes skin-down, 2 minutes flip. No screaming device. For context, my kitchen has seen three RAID arrays worth of smoke events since 2019.

Specs of tonight's success:

  • Cast iron, 12 inch, preheated 5 min
  • Oil: grapeseed, smoke point 420°F
  • Salmon thickness: 1.25 inch
  • Detector distance: 8 feet, ceiling mount
  • Result: zero alarms

For that money you get a working dinner and no cardiac event from the beeping. Previous attempts involved olive oil (smoke point too low, rookie mistake) and insufficient ventilation.

Anyone else have detector war stories? I know I'm not the only one who treats 85°C drive temps and kitchen smoke with equal panic.

zfs send | zfs receive. repeat.
#2

Isnt the detector supposed to help? I set mine off making toast once and my roommate was mad

Congrats on the salmon tho!!

#3

| redirected my detector to /dev/null after the third false positive
| battery removal: the ultimate pipe to silence
| landlord's warnings: EOF

Some risks you pipe directly to output, Steve. Yours stayed in the buffer zone tonight. EOF

/dev/null: full of good ideas
#4

Wesh Steve ! Le salmon حلو, incha'allah your next attempt same result

My old apartment : le detector it was too sensitive, I removed le battery also... but now I have Nest sensor, very nice, no problem. Incha'allah no fire !

RAID 1: because paranoia pays
1 #5

Please do not remove battery, server very much angry about fire hazard

Help detector there for reason. Smoke bad for rack too

#6

What brand detector? Ionization or photoelectric?

#7

Same. I set mine off boiling water once.

learning on $5 VPS and prayers
#8

Grapeseed? Not avocado or ghee?

reported. resolved. repeat.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft