Yeah, that’s a good point. For me it’s mostly family that is not very technical, so I’m not too concerned of them using a fork.

Poor security implementations that would become the weakest link in the security chain

Definitely. Capturing the messages isn’t my concern though as much as interacting with non authentic clients

Yes of course. Signal can archive messages and they can be restored, you can screenshot messages and you can have them backed up as part of a policy like icloud backups.

My question is more about how do you know you’re interacting with an authentic signal client, and not a bastardized one.

This might feel bad, but honestly you’re still killing it. I graduated at like 30 after grinding out years and years of CC. You have great prospects, just stay focused

Why is Incogni bad?

I recently started playing with scenes too. Maybe I should go that route with more of my lights

Molto bello!

Yes, definitely. That’s one of the reasons I’ve implemented this way. If a light (for example) had the physical switch turned off and back on, a lot of smart bulbs will go to the on state, even if HA had previously set (and expects it to be) off. The next execution may turn it off in an off state, on in an on state, on from an off state or off from an on state, but either way that truth table will resolve after an iteration

Oh that’s good to know. I have a handful of Kasa bulbs and I don’t give them WAN access. They seem to be mostly fine without WAN, but I do get communication issues with them from time to time (which is why I’m exploring zigbee as an alternative). Thank you for the reply!

Great points. I have white a few smart switches through the house to control things both physically and via Home Assistant. Most of the other lights are wifi based and work mostly as expected with occasional drops (which can get annoying). Was wanting to experiment with ZigBee to see if it was more reliable, but it sounds like that might not be the case

That would be my exit sign