<feed xmlns='http://www.w3.org/2005/Atom'>
<title>iot-contact/fw/app/Kconfig, branch main</title>
<subtitle>IoT device to check if doors and windows are closed or open</subtitle>
<id>https://cgit.xengineering.eu/iot-contact/atom?h=main</id>
<link rel='self' href='https://cgit.xengineering.eu/iot-contact/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit.xengineering.eu/iot-contact/'/>
<updated>2025-04-02T18:43:29Z</updated>
<entry>
<title>fw: app: Fix native_sim build</title>
<updated>2025-04-02T18:43:29Z</updated>
<author>
<name>xengineering</name>
<email>me@xengineering.eu</email>
</author>
<published>2025-04-02T18:43:29Z</published>
<link rel='alternate' type='text/html' href='https://cgit.xengineering.eu/iot-contact/commit/?id=d19fc7e34f783b343e77b757c4f37aaadb5b66ca'/>
<id>urn:sha1:d19fc7e34f783b343e77b757c4f37aaadb5b66ca</id>
<content type='text'>
To reduce the number of Kconfig options the network hack was added two
both boards - the native_sim and nucleo_f767zi one. It reboots the
device if the network connection cannot be established since this is a
known bug of the nucleo board.

Nevertheless it seems that for the native_sim board this command is not
defined. Since it is a Linux application this makes somehow sense.

This commit introduces the boolean Kconfig option
`IOT_CONTACT_NETWORK_HACK` which is only enabled for the nucleo board
fixing the native_sim build.
</content>
</entry>
<entry>
<title>fw: app: update: Add source file and HTTP 204 handler</title>
<updated>2025-03-30T16:51:33Z</updated>
<author>
<name>xengineering</name>
<email>me@xengineering.eu</email>
</author>
<published>2025-03-27T20:19:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit.xengineering.eu/iot-contact/commit/?id=b2afe2a52d421a6f9ce87d6b20c0230f93ecbdc4'/>
<id>urn:sha1:b2afe2a52d421a6f9ce87d6b20c0230f93ecbdc4</id>
<content type='text'>
This adds the HTTP PUT /update handler which just returns HTTP 204 No
Content.

This is the minimal first step towards a working /update handler.
</content>
</entry>
</feed>
