z-wave.me

Z-Uno has pure digital outputs, so it gives 0 or 3V only.

What you need is a DAC.

But there is a trick. You can use Z-Uno FastPWM (pwm0) pin and attach a capacitor to smoother this PWM signal. This will give a very good analog signal in range of 0-3 V. This is how Shield is doing analog output.

Please try this first
http://z-uno.z-wave.me/z-wave/interoper ... lers/#Vera

Можно! Много! Тогда будет больше разработчиков

The work on the new release took a bit longer. We will make a notice once it is released.

We are doing new RC's every few weeks and working hard on a new release. You don't notice them because they are now in .deb - search for "3.0.0-rc".

We are working right now on certification and releasing of a new version with S2. Most changes are fixes or minor improvements for the certification.

We have tried to reproduce your case, but all in vain. Need better instructions:
- how to configure the module - we used tcp://echo.websockets.org instead of the docker
- how to reproduce the issue
- how to experience the issue

I don't really get how https is related to wss. The only common thing is OpenSSL library. I think the main problem you experience might be that after an HTTPS error OpenSSL can stop working in all modules. This looks to be an OpenSSL problem that we need to solve by updating the OpenSSL.

The MQTT app is a community contribution. Currently it supports only push mode. You can improve it an publish your version or contact the the developer and ask if he can make the pull side too. Basically it should not be hard - use websockets to subscribe and get updates. Also add devices on the fly...

Looks like the device is only sending Set events, while replies on Get with a Report. I think you should check for config params to configure Reports properly.

Looking here I see that you should downgrade first to 5.06

https://service.z-wave.me/expertui/uzb/ ... ith_hidden