You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it's necessary to assign values containning national characters to string items (and this works ok). The problem is that http binding is not URL encoding such characters, therefore linking them in string channels results in errors such as
Assign a value to the string item not containning national characters -> no errors in log
Assign a value to the string item containning national characters -> errors in log
Context
I am using the http binding for multiple purposes. In above case I'm using it instead of the telegram binding (I don't need to poll received messages, I only need to send occasional alerts and http binding is perfect for that).
Your Environment
Version used: 3.2.0
Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...): QNAP NAS
Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...): QTS 5, Java11 (Zulu)
The text was updated successfully, but these errors were encountered:
Expected Behavior
Sometimes it's necessary to assign values containning national characters to string items (and this works ok). The problem is that http binding is not URL encoding such characters, therefore linking them in string channels results in errors such as
In above message the national character
ã
should have been encoded by the binding. In fact, ifa
was used instead ofã
the message is sent.Current Behavior
Errors are produced in
openhab.log
when national characters are assigned to string channels.Possible Solution
Steps to Reproduce (for Bugs)
Create a thing as follows:
message
to a string itemContext
I am using the http binding for multiple purposes. In above case I'm using it instead of the telegram binding (I don't need to poll received messages, I only need to send occasional alerts and http binding is perfect for that).
Your Environment
The text was updated successfully, but these errors were encountered: