You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 2.15 my Blitzwolf SHP-15 are not reporting updates to the REST API. While, via VNC, I can retrieve the latest values, in REST API calls the sensor indicate lastupdate before upgrading to 2.15, around 10 days ago, see screenshots.
Steps to reproduce the behavior
Call REST API to sensor, e.g. 92
Check last update
Open VNC
Navigate to corresponding cluster
Click "Read" and see updated values
Re-run 1. & 2. and see no updates in REST API
Expected behavior
Devices is reporting updates and manual update should be visible in REST API calls
Screenshots
Environment
Host system: Raspi 4b - Docker setup
Running method: Docker community deconz
Firmware version: 26720700
deCONZ version: 2.15.00
Device: RaspBee II
Other Info
Resetting the device does not solve the issue. But, after deletion of node in deconz via VNC - delete node and re-pairing of the device it starts to work again.
The text was updated successfully, but these errors were encountered:
@Smanar I see these new Blitzwolf DDF files reference a Tuya file:
"script": "../tuya/tuya_swversion.js"
What happens if we create a custom DDF from a copy of this json in the Docker Mount (/docker/deconz/data/devices? This folder does not contain that file in the relative patch ? Will it automatically try to find the file in the installed deconz instance as well, not only in the Docker custom devices folder?
Describe the bug
After upgrading to 2.15 my Blitzwolf SHP-15 are not reporting updates to the REST API. While, via VNC, I can retrieve the latest values, in REST API calls the sensor indicate lastupdate before upgrading to 2.15, around 10 days ago, see screenshots.
Steps to reproduce the behavior
Expected behavior
Devices is reporting updates and manual update should be visible in REST API calls
Screenshots
Environment
Other Info
Resetting the device does not solve the issue. But, after deletion of node in deconz via VNC - delete node and re-pairing of the device it starts to work again.
The text was updated successfully, but these errors were encountered: