But it doesn’t work because this gets cut off at the colon after the cmd=6A
DEBUG:
[DEBUG] [ab.binding.http.internal.HttpBinding] - Executing url ‘h_ttp://192.168.88.247/sec/?pt=6&cmd=6A’ via method GET
[DEBUG] [ab.binding.http.internal.HttpBinding] - Executing url ‘h_ttp://192.168.88.247/sec/?pt=6&cmd=6A’ via method GET
Yes, I’m sure, but I don’t think the method matters to this problem.
Changing method:
[DEBUG] Refreshing model 'http.items'
[DEBUG] [.internal.HttpGenericBindingProvider] - parsing this as an http out binding: ON:POST:http://192.168.88.247/sec/?pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - URL portion of binding config to be processed: http://192.168.88.247/sec/?pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 0: http://192.168.88.247/sec/?pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 1: http://192.168.88.247/sec/?pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 2: http:
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 3: http
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 4: //192.168.88.247
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 5: 192.168.88.247
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 6: /sec/
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 7: ?pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 8: pt=6&cmd=6A%%3A1
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 9: null
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 10: null
[DEBUG] [.internal.HttpGenericBindingProvider] - Group 11: null
Result is the same:
[DEBUG] Executing url 'http://192.168.88.247/sec/?pt=6&cmd=6A%%3A0' via method POST
Executing url 'http://192.168.88.247/sec/?pt=6&cmd=6A%3A1' via method POST
I don’t undestand which device or service should decode from the characters “% 3A” to the character “:”.
And should I want to make url look like “cmd=6A:1” in the debug log?
In russian forum I find some info.
The url with colon worked on OH 1.8 version and stopped working on version 2
May be something wrong with url-decode?
The HTTP binding is still version 1.x, but of course it must run within OH2 framework. Yes, of course something may have changed, it may be in the way xxx.items files are parsed.
It might be worth you playing with a rule and HTTP action, see if that encodes better.