CoAP | Simple CoAP library for Particle Core and Photon | Runtime Evironment library

For me the requirements are not that clear.

The open source project Eclispe/Californium comes with coap2http cross proxy functionality (and also http2coap). You may try it demo-apps/cf-proxy2

For future individuals that might need help with this, use aioCoAP, its much easier then CoAPthon

get it from here https://aiocoap.readthedocs.io/en/latest/installation.htmlg

all you need to do is mess with three files labeled server.py, clientPUT.py and clientGET.py Add resources and classes for sensors and what not to server.py ClientPUT.py is where you would add your code for the sensors or whatever you need. ClinetGET.py you alter the uri

run it by type in the command in the terminal (go to directory first that has the server) type in python server.py
in another terminal do the same thing but instead run python clientPUT.py

and the server should be running then all you need is a client for the get request. If you were like me and needed to use Copper go here to install it for chrome https://github.com/mkovatsc/Copper4Cr

This is an issue resulting from aiocoap still using (and, in some places, using badly) idioms to support Python 3.7 or (in obsoleted parts) even previous versions.

I'm aware asyncio.run() is preferred, but until the next aiocoap release (in which I plan to update the examples too), the old idiom is what works best across the range of supported Python versions.

The result of

The current CoAP Secure APIs in OpenThread only supports a single active session.

The ESP-IDF build system is built on top of CMake. This means you can use all the standard features of CMake in your files. However, the the ESP-IDF system predefines many functions, and makes many assumptions about the layout of your project, supposedly to make things "easier". Instead of reading CMake documentation, start by reading and understanding the ESP-IDF build system documentation:

https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html

It looks to me like there is a particular layout expected for subcomponents, including the format of the CMakeLists.txt file. Specifically, move Metriful under a new directory called components, or add Metriful to EXTRA_COMPONENT_DIRS near the top of your root CMakeLists.txt

If Metriful is not written as an esp-idf component, this may not work. However, the document also describes how to link to "pure CMake" components, which will look something like this (at the end of your root CMakeLists.txt).

You did not specify if you had any requirements in terms of FreeRTOS version, but you can either:

• use the demo provided in file SW-EK-TM4C1294XL-2.1.4.178.exe available on TI WEB site as is - you will find it in directory examples\boards\ek-tm4c1294xl-boostxl-senshub\senshub_iot
• use this example as a basis to use a more recent version of FreeRTOS: you just would have to replace FreeRTOS source code by the most recent one, and maybe to modify some code in the demo: some function names/signatures may have changed across major versions.

The procedure hereafter describes step by step how to create a minimalist FreeRTOS program with Code Composer Studio 10.3.0 and FreeRTOS v202104.00 in a Windows 10 environment using the second approach. You may have to adjust the drive letter to you specific setup, I am using D: for the purpose of this example..

• Download Code Composer Studio 10.3.0, FreeRTOS v202104.00 and SW-EK-TM4C1294XL-2.1.4.178.exe.

• Install Code Composer Studio with support for the Tiva-C MCU familly. When prompted for a workspace name, specify D:\ti\workspace_v10.

• Unzip FreeRTOSv202104.00.zipinto D:\.

• Unzip SW-EK-TM4C1294XL-2.1.4.178.exe into D:\SW-EK-TM4C1294XL-2.1.4.178.

• Launch CCS

• Use the menu item File/New/CCS Project, and create an 'Empty Project (with main.c).

[]

• Click on the Finishbutton.
• Create the following directories:
  D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\driverlib
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\inc
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\include
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\portable\GCC
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\portable\GCC\ARM_CM4F
D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\portable\MemMang
• Copy D:\SW-EK-TM4C1294XL-2.1.4.178\examples\boards\ek-tm4c1294xl-boostxl-senshub\senshub_iot\FreeRTOSConfig.h into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS
• Copy all .h files from D:\SW-EK-TM4C1294XL-2.1.4.178\driverlib into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\driverlib.
• Copy D:\SW-EK-TM4C1294XL-2.1.4.178\driverlib\gcc\libdriver.a into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\driverlib.
• Copy all .hfiles from D:\SW-EK-TM4C1294XL-2.1.4.178\inc into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\inc.
• Copy all files present in D:\FreeRTOSv202104.00\FreeRTOS\Source\include into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\include.
• Copy all .cfiles present in D:\FreeRTOSv202104.00\FreeRTOS\Source into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel.
• Copy all file present in D:\FreeRTOSv202104.00\FreeRTOS\Source\portable\GCC\ARM_CM4F into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\portable\GCC\ARM_CM4F
• Copy D:\FreeRTOSv202104.00\FreeRTOS\Source\portable\MemMang\heap_4.c into D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\FreeRTOS-Kernel\portable\MemMang.
• Edit D:\ti\workspace_v10\TM4C129EXL-FreeRTOS\main.c, and replace its content by:

CoAP (and so Californium) focus on efficiency for small payloads. POST files will not be the domain of CoAP at all. If you really want that, just load the payload from the file and POST that. Ensure, you configured the MAX_RESOURCE_BODY_SIZE in Californium.properties according your requirements. If you use Californium on both sides, both need to be configured. Alternatively, you may disable the "transparent blockwise" using a 0 MAX_RESOURCE_BODY_SIZE. That will then require, that you handle the single blocks and block-option on your own.

Some hints for the parts I understand:

0xb5 other 0x05, block

1. Option 11, len=5, Uri-Path, value "other" (RFC 7252)
2. Option 11, len=5, Uri-Path, value "block" (RFC 7252)

0x10

Option 12, len=0, Content-Format, value 0 (RFC 7252)

0xb1,0x06

Option 23, len=1, Block1, value 0x06 (num=0,m=false,szx=6/1024 bytes) (RFC 7959)

0x41,0xe6

Option 27, len=1, Block2, value 0xe6 (num=14,m=false,szx=6/1024 bytes) (RFC 7959)