search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.88k stars 485 forks source link

Ubisys S1-R Metering functions #4203

Closed tgoerlich closed 3 years ago

tgoerlich commented 3 years ago

Describe the question or issue you are having

Hi all, I successfully conneted the Ubisys S1-R rail switch, however I seem to miss the metering functions that come with it. I cannot see any sensors in the phoscon web app, also not in other connected applications („Hue Essentials“ iOS App, iobroker deconz adapter). In the deconz application itself I see the sensors, so they must be somewhere! Am I missing something? Can anyone confirm if the metering functions of the S1-R are implemented fully?

Screenshots

26407B08-18CC-4E8B-BE44-12252761E774

Environment

Host system: Raspberry Pi Running method: Raspbian Firmware version: 26520700 deCONZ version: 2.05.74/25.2.2020 Device: RaspBee II Do you use an USB extension cable: no Is there any other USB or serial devices connected to the host system? No

deCONZ Logs

Additional context

Thanks

tgoerlich commented 3 years ago

Additional info: In Deconz, I read power measurement values that look plausible. So, the more precise question is: how can the metering sensor be made visible through the API? Thanks, Thomas

ebaauw commented 3 years ago

Should already be exposed as a ZHAConsumption /sensors resource for cluster 0x0702 and a ZHAPower /sensors resource for 0x0B04.

tgoerlich commented 3 years ago

There is no ZHAConsumption or ZHAPower in my /sensors list. According to the supported devices list, the sensor functions of the Ubisys S1-R should be supported without any known issue. Strange! Any idea what I should do? Thx, Thomas

tgoerlich commented 3 years ago

Ok, Problem solved (at least for me). It seems that the S1-R is only recognised as a sensor when there is current load during the pairing process. So, switch on a radiator, go downstairs, press reset for 10secs, pair again... and here we are. Since it worked in deconz also before, I would consider this as a bug in the REST-API. IMHO there is no reason why there should be a different behaviour of the api depended on load while pairing...