Hi
I have Z-way and OpenRemote coexisting since more than 3 years. OR connects with Z-way-server via http protocol. After updating z-way to 2.2.2 version, OR cannot connect via http any more. Z-way log says
Can not make request: Not Found
any help?
v 2.2.2 and OpenRemote
Re: v 2.2.2 and OpenRemote
I should add that calling the Zway API with the browser works just fine
Re: v 2.2.2 and OpenRemote
There is a problem with HTTP authentication
A work around is to create a user anonymous Assign all rooms to this user.
(I have made one room Devices, and assigned all devices to that room)
A work around is to create a user anonymous Assign all rooms to this user.
(I have made one room Devices, and assigned all devices to that room)
- Attachments
-
- anonymous.PNG (20.6 KiB) Viewed 9925 times
Since 29-12-2016 I am no longer a moderator for this forum
Re: v 2.2.2 and OpenRemote
I did this, it is not the problem. In fact, I can send request to z-way-server from curls or browser without username and password. The problem is that 2.2.2 does not understand encoded urls. I downgraded to 2.1.1, same set up, and works just fine. Is there a workaround for 2.2.2 to understand encoded ulrs?
Re: v 2.2.2 and OpenRemote
What is the command you send? How do you encode?
Re: v 2.2.2 and OpenRemote
Hi (thanks for the replies).
I'm sending (for instance):
I'm sending (for instance):
And I get a "Internal Server Error" in OR. Then I sniff tcp traffic going from OpenRemote (OR) to z-way-server and I see the same command sent as:
Thus the request is encoded by OR, and I cannot change it. Please note that by downgrading Z-Way to 2.1.1 everything works, meaning that the encoded request is well accepted by 2.1.1 but not by 2.2.2. Am I correct?
Last edited by mcfanda on 26 May 2016 00:26, edited 2 times in total.
Re: v 2.2.2 and OpenRemote
Did you enable Zwave API in the Zwave App?
Not desirable from a security point of view, but I learned to live with it
Not desirable from a security point of view, but I learned to live with it
- Attachments
-
- Capture.PNG (18.71 KiB) Viewed 9888 times
Re: v 2.2.2 and OpenRemote
I do not have this switchMultiLevel, so I can't try unfortunatelymcfanda wrote:Hi (thanks for the replies).
I'm sending (for instance):
http://10.0.0.3:8083/ZWaveAPI/Run/devic ... evel.value
And I get a "Internal Server Error" in OR. Then I sniff tcp traffic going from OpenRemote (OR) to z-way-server and I see the same command sent as:
http://10.0.0.3:8083/ZWaveAPI/Run/devic ... evel.value
Thus the request is encoded by OR, and I cannot change it. Please note that by downgrading Z-Way to 2.1.1 everything works, meaning that the encoded request is well accepted by 2.1.1 but not by 2.2.2. Am I correct?
What brand and type of switchMultiLevel do you have?
Re: v 2.2.2 and OpenRemote
I'm afraid id does not matter. I have fibaro dimmers but they work fine with Z-Way server. The problem I mentioned above occurs for any kind of command that Openremote sends to Z-way-server. It does that for all http requests, no matter the z-wave hardware one uses (I have dozen of them of different brands).
I've done different tests, the problem is on the encoding-decoding of the urls between Openremote and z-way-server. I'm afraid I should wait and hope a newer version of z-way-server will work with OpenRemote.
But really thanks for the help
I've done different tests, the problem is on the encoding-decoding of the urls between Openremote and z-way-server. I'm afraid I should wait and hope a newer version of z-way-server will work with OpenRemote.
But really thanks for the help
-
- Posts: 46
- Joined: 23 May 2016 21:41
Re: v 2.2.2 and OpenRemote
Are you able to do this HTTP request in your web browser on your computer? You should be able to login at http://10.0.0.3:8083/ and then after logging in, you can copy/paste the API command and it should work. If it works on your browser, but not in OR, then my guess is that OR is either not logging in correctly, or there is an issue with the encoding of the URL in OR. But I would test it with your browser first.mcfanda wrote: I'm sending (for instance):
http://10.0.0.3:8083/ZWaveAPI/Run/devic ... evel.value
And I get a "Internal Server Error" in OR.