no connection to RaZberry

Discussions about RaZberry - Z-Wave board for Raspberry computer
Post Reply
cyberhofi
Posts: 26
Joined: 31 Oct 2015 13:48

no connection to RaZberry

Post by cyberhofi »

In the last days i got some connection issues with firmware 2.1.1.
It was not possible to connect to port 8083 but the connection to 8084 was ok.
I also tried to use the API, there the login is working but im not getting any data.

After that i tried upgrading to 2.1.2-rc2 and downgrading again to 2.1.1 but nothing changed.

If i try to login via internet i get this:
Type: connect
V8-Version: 3.24.38 (candidate)
Protocol-Version: 1
Embedding-Host: zway
Content-Length: 0

Content-Length: 96

{"seq":2,"request_seq":1,"type":"response","command":"disconnect","success":true,"running":true}
Also i did not find the config.json file. Was this removed in V2.1.1?

I did no changes to my raspi, so this must be a bug...
cyberhofi
Posts: 26
Joined: 31 Oct 2015 13:48

Re: no connection to RaZberry

Post by cyberhofi »

I formatted my SD card, made a new install of Raspbian Wheezy, installed all updates and made a clean install of Firmware 2.1.1

Still the same Problem: Port 8084 is working Port 8083 does not work.
Can someone provide a workaround for this problem?
cyberhofi
Posts: 26
Joined: 31 Oct 2015 13:48

Re: no connection to RaZberry

Post by cyberhofi »

Got the solution:

For some reason the raspberry firmware was too old. Maybe this comes from (automated) software updates?

Code: Select all

sudo rpi-update
starts the firmware update of the Raspi

Code: Select all

sudo reboot
reboots the device, after that everything should be work
User avatar
PoltoS
Posts: 7649
Joined: 26 Jan 2011 19:36

Re: no connection to RaZberry

Post by PoltoS »

Your problem looks like you have selected debug port to 8083 and Z-Way stopped serving HTTP on that port, since it was already used by debugger. This is done in config.xml. Use another port for debugging like 8183
jonator
Posts: 5
Joined: 13 Nov 2015 09:21
Location: Sweden

Re: no connection to RaZberry

Post by jonator »

cyberhofi wrote:Got the solution:

For some reason the raspberry firmware was too old. Maybe this comes from (automated) software updates?

Code: Select all

sudo rpi-update
starts the firmware update of the Raspi

Code: Select all

sudo reboot
reboots the device, after that everything should be work

"should" work? Did it work or did it not? :) I am asking as I have this problem as well and the rpi-update didnt help when I tried last time.
Post Reply