3.2.0 release but no changelog
Re: 3.2.0 release but no changelog
In my case, I had to downgrade to 3.1.4 from 3.2.0 because the websocket does not write notifications in version 3.2.0. I do not know if there is any change in version 3.2.0 that affects the connection through websocket.
Re: 3.2.0 release but no changelog
For what it's worth, apart from the (for me) broken init.d script the 3.2.0 web frontend and the app feels a bit snappier and I have observed no other issues so far.
Last edited by xurg on 06 Sep 2021 19:26, edited 1 time in total.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster)
RaZberry ZW0500 1024/2 SDK: 6.82.01 API: 05.39
Z-Way version v4.1.0
Raspbian GNU/Linux 10 (buster)
RaZberry ZW0500 1024/2 SDK: 6.82.01 API: 05.39
Z-Way version v4.1.0
Re: 3.2.0 release but no changelog
My upgrade to 3.2.0 also failed and I had to downgrade to 3.1.4 to get it back working.
Rpi4 2Gb, Z-Way 3.2.2, UZB 5.39
Re: 3.2.0 release but no changelog
Yeah, I think that is what node-red is using, that is why I had issues
I saw in the changelog these points :
* New Websocket API on :8083
* Adopted to new WebServer API with WebSocket Auth handler and new ws.push parameter with list of IDs to be notified with the event
not sure if that had anything to do with it...
Re: 3.2.0 release but no changelog
Oh, guys, we are sorry for your frustrations... Let's go step by step.
@vinisz Could you please let us connect and check your issues one by one?
As for the node-red, if it uses the websocket API, you can easily fix it by adding the authentication. I've made a fast commit (without testing - I don't have node-red to test). You can check it! https://github.com/bkorda/node-red-contrib-zway/pull/11
@añep Yes, we are preparing Websockets API. Currently it already works (like before), but you need to authenticate yourself using any valid auth method like with simple HTTP: cookies, header, Authe Bearer, Basic Auth.
@insiorc Please help us to understand the issue.
@vinisz Could you please let us connect and check your issues one by one?
As for the node-red, if it uses the websocket API, you can easily fix it by adding the authentication. I've made a fast commit (without testing - I don't have node-red to test). You can check it! https://github.com/bkorda/node-red-contrib-zway/pull/11
@añep Yes, we are preparing Websockets API. Currently it already works (like before), but you need to authenticate yourself using any valid auth method like with simple HTTP: cookies, header, Authe Bearer, Basic Auth.
@insiorc Please help us to understand the issue.
Re: 3.2.0 release but no changelog
PoltoS, I upgraded through the UI then waited several hours but no automation, and unable to login via the find.z-wave.me or IP:8083. In Putty using top there was no usual instance of z-way. I tried starting the z-way server which replied 'done', but still no run. Once I downgraded everything worked as expected.
Rpi4 2Gb, Z-Way 3.2.2, UZB 5.39
Re: 3.2.0 release but no changelog
@insiorc I fear it is a libmosquitto issue. Can you please provide remote access to check it?
Re: 3.2.0 release but no changelog
PoltoS, I've PM'd you the access details
Thanks
Thanks
Rpi4 2Gb, Z-Way 3.2.2, UZB 5.39
Re: 3.2.0 release but no changelog
We found one issue that can affect backup/restore and few other parameters of the system. The fixed code is already on github, we will make a hot release next week.