official forum

https://github.com/Z-Wave-Me/home-autom ... b393f6edca

That was the change. Please check it

Please try this:
https://github.com/Z-Wave-Me/home-autom ... 0dc7e2d3d8

If you can tell us part of your token (only part, some 6 symbols only - not to give full access ;), we can check it on our system. But so far we have noticed that some Google servers have problems reaching our servers. Anyway, we can check - also give us time when it complains and where it does not ...

check the manual for system(). You can also use sockets.tcp() and http.request(). CodeDevice is also a nice tool to combine with JS code mentioned here.

You need to go in firmware upgrade and install 3 channels firmware. It is a special one for KR/JP. Please got on /expert/#/uzb and anter token "all". You will see proposals to upgrade the bootloader and firmware. Please follow up to 5.39. You will see 3 channels (JP) version there.

Ясно. Включу в список. Но в основном у всех один стик, поэтому по приоритету не подскажу

It is already. You can upgrade via apt-get

Thanks, this is known, we have it on our list for v3.1.3

Okey, we will look in it.

Ineed, from the log you can see that first time it was fired because you changed the value of the device (value has changed to the target one). Second time it is fired when the update is confirmed from the device (value finally adopted). It should happen only once if it comes from the device. But if...