I was wondering whether the websocket functionality was broken, because it hasn't worked for me for over a year.
Since I heard little complaints about it on the forum I guess either nobody uses it (unlikely) or it's just broken for me.
Are there any special prerequisites to using the websocket? I tested in Safari, since it seems to be made for that browser, but it didn't work.
I did test in Safari on iPad, instead of iPhone though.
Or does the web-socket only work on an unsecured TCP connection?
In that case it is of little value to me, since it would essentially bypass all security measures.
Websocket broken?
Moderator: hvxl
Re: Websocket broken?
I'm struggling with the same problem. WebSockets are working fine on my Android devices or in IE, it fails however when I visit the thermostat page on my iPhone. It doesn't matter wether I'm using a secure connection over https or a standard connection over http. OTMonitor runs behind an nginx server and I would like to see the WebSockets working on my iOS devices. 

Re: Websocket broken?
At least in Apache you have to use a 'special' proxypass for websockets and in nginx it seams also:
https://httpd.apache.org/docs/2.4/mod/m ... unnel.html
https://www.nginx.com/blog/websocket-nginx/
So maybe you need to adjust this in your reverse proxy config?
https://httpd.apache.org/docs/2.4/mod/m ... unnel.html
https://www.nginx.com/blog/websocket-nginx/
So maybe you need to adjust this in your reverse proxy config?
Re: Websocket broken?
I already adjusted these settings to make the WebSockets working on non-iOS devices. The WebSockets are also failing when I visit the thermostat page via my internal WiFi bypassing the reverse proxy.
Re: Websocket broken?
The otmonitor side of things doesn't seem to be the problem as it works fine with firefox.
I originally tested the iphone page with IOS 5. At that time it worked. Since then bugs appear to have crept into the webkit framework. I noticed myself that client certificates are no longer being sent for urls added to the home screen. And since Apple only allows browsers based on webkit on their devices, there's no way around these bugs. Another reason not to use Apple equipment.
I originally tested the iphone page with IOS 5. At that time it worked. Since then bugs appear to have crept into the webkit framework. I noticed myself that client certificates are no longer being sent for urls added to the home screen. And since Apple only allows browsers based on webkit on their devices, there's no way around these bugs. Another reason not to use Apple equipment.
Schelte
Re: Websocket broken?
When I visit the page https://websocketstest.com on my iPhone (iOS 7) it says that WebSockets seem to work on my device. Is it possible to get the setpoint manipulation working without the need of WebSockets by editng the iphone.html page?
Re: Websocket broken?
Maybe you can try this solution: http://stackoverflow.com/a/27534443janh wrote:When I visit the page https://websocketstest.com on my iPhone (iOS 7) it says that WebSockets seem to work on my device. Is it possible to get the setpoint manipulation working without the need of WebSockets by editng the iphone.html page?