Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Escape Character #495

Closed
craiglt opened this issue Feb 24, 2017 · 3 comments
Closed

Using Escape Character #495

craiglt opened this issue Feb 24, 2017 · 3 comments

Comments

@craiglt
Copy link

craiglt commented Feb 24, 2017

I have created bridge device with the type of TCP device and a target item of:
tcp://192.168.0.4:2500/task 36 \n

The call does not work. The entry in the device.db file looks like this:
"onUrl":"[{"item":"tcp://192.168.0.4:2500/task 36 \\n","type":"tcpDevice"}]"

If I manually edit the device.db file to look like this:
"onUrl":"[{"item":"tcp://192.168.0.4:2500/task 36 \n","type":"tcpDevice"}]"
then the call works.

Am I making a mistake when I first create the bridge device?

@bwssytems
Copy link
Owner

I need to rework encoding

@craiglt
Copy link
Author

craiglt commented Feb 24, 2017

Thanks, but it looks like my original posting does not appear exactly as I entered it.

In the devices.db file, the call that does not work ends with:
task 36 backslash backslash backslash backslash n backslash

The call that does work ends with:
task 36 backslash backslash n backslash

@bwssytems bwssytems added this to the V4.2.1 milestone Mar 8, 2017
@bwssytems
Copy link
Owner

This has been added to the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants