Connection refused by the Z-way server ver. 3.0

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
Dorotej
Posts: 4
Joined: 09 Jul 2019 14:48

Connection refused by the Z-way server ver. 3.0

Post by Dorotej » 01 Sep 2019 23:07

After upgrading the Z-way server to version 3.0, we noticed very slow performance. We occasionally get a warning "Connection refused by the Z-way server". We didn't have any problems with the previous version!

User avatar
PoltoS
Posts: 4978
Joined: 26 Jan 2011 19:36

Re: Connection refused by the Z-way server ver. 3.0

Post by PoltoS » 02 Sep 2019 03:37

Do you have a lot of connections to the UI (from mobile apps or from third party software)?

Dorotej
Posts: 4
Joined: 09 Jul 2019 14:48

Re: Connection refused by the Z-way server ver. 3.0

Post by Dorotej » 02 Sep 2019 14:36

We are stopping our software. There are no connections to the UI. The problem is if we want to open websites http://89.212.162.78:8083/smarthome or http://89.212.162.78:8083/expert also. You can try that. Note: 89.212.162.78 is IP number of our Raspberry Pie.

User avatar
PoltoS
Posts: 4978
Joined: 26 Jan 2011 19:36

Re: Connection refused by the Z-way server ver. 3.0

Post by PoltoS » 02 Sep 2019 20:29

If you donut across internet, it might happen that due to slow response the UI can complain about no connection. It should recovery once the signal is back.

Please check if it working Okey locally - is it as slow as via internet.

I would also not suggest to expose your Pi to the internet. Why not to use find service to protect the access to the UI?

Dorotej
Posts: 4
Joined: 09 Jul 2019 14:48

Re: Connection refused by the Z-way server ver. 3.0

Post by Dorotej » 02 Sep 2019 21:49

We have the same problem locally. I opened the websites as localhost:8083/smarthome and localhost:8083/expet with the same results - Connection refused by the Z-Way server.

Dorotej
Posts: 4
Joined: 09 Jul 2019 14:48

Re: Connection refused by the Z-way server ver. 3.0

Post by Dorotej » 04 Sep 2019 22:55

We found out where the problem was. We had to replace the SD memory card.

Post Reply