I’m sorry to insist on this one, but IMO, OH should not throw such error upon unexpected request ( Content-Type header is not mandatory upon RFC7231). Although I agree that the HB module should be more accurate in its request, it is a regression as it was working on OH2, and not anymore in OH3 (change of behavior).
It also generates pollution to have those errors in the stack trace
May I suggest to handle the default behavior as text/plain instead of application/octet-stream ? I know that the RFC7231 mentions that the default is application/octet-stream, but it also mentions:
[…] or examine the data to determine its type.
It would as such not be a deviation to the RFC to try to figure out if the POST payload is text/plain instead of application/octet-stream.
As you run into something you don’t understand or can’t figure out how to do, please go to these topics (note there are several posts for each thread) and if you can’t clarify the documents, please at least post a reply or edit inline with the question or request for clarification.
The docs won’t be any good without contributions from the community, especially early adopters of OH 3.
This is just a general question and not meant to push anything but more to understand the intended direction of the future of OH.
There was discussion in previous threads of making Python/Jython a “first class citizen” as it were for programing rules in OH3. OH2 requires a lot of set to make it work, which I’ve successfully done, and it’s not difficult, just requires effort.
Are there still plans to integrate it better into OH3 or will the config be about the same as OH2? I value Python integration greatly as it really makes OH2 an amazing tool and opens a lot of possibilities. Either way I just don’t want to see Python/Jython dropped from OH3, which I’m assuming is not the plan.
More just for my own understanding of what the developers are thinking.
Have you tried with a clean database? You should try the fix with a clean db or with one migrated from OH 2.0.
If the DB has previously written readings from OH 3.0 nonfixed addon it’s normal it fails.