Relational-JSON overlapping with association
If you want simple and efficient SQL statements, don't model an entity as a JSON column. Create a regular normalized table that expresses the functional dependency between the sensor's attributes explicitly.

JSON in the database is a good thing and has its applications, but modeling foreign key relationships like the one to event is not among them.