Initial support for Sinope Smart in-wall outlet – Zigbee (SP2610ZB)#4889
Initial support for Sinope Smart in-wall outlet – Zigbee (SP2610ZB)#4889ericvandamme wants to merge 3 commits intodresden-elektronik:masterfrom
Conversation
Initial support for Sinope Smart in-wall outlet – Zigbee (SP2610ZB)
Initial support for Sinope Smart in-wall outlet – Zigbee (SP2610ZB)
|
Hi @ericvandamme , would these changes resolve #4870 and #4871 as well? |
I cannot confirm. I only tested with my Sinope device. So the two devices you mentioned I couldn't test. Because it could impact other people's implementations if it is merged, I generally don't assume "works as intended" and a create a merge request. I have uploaded a compiled for deCONZ v2.11.05-raspian-buster-beta; if you trust such a file from a stranger on the internet. It should work just fine. Just need to extract and copy it to the appropriate directory (/usr/share/deCONZ/plugins/). You may wish to make a backup of the old file first. If it works, I can submit those changes too to catch the next release. |
|
Hi,
I now see the power & consumption for all the devices. Which is
great.
There are 2 items missing though. I am not sure if they were accidentally
left out, but when I looked briefly at the code it appeared to be missing:
The RM3250ZB controller has Cluster:
0002 Device Temperature configuration
ID: 0x0000 Current Temperature /S16 which doesn't seem to be picked up or
recognized.
Also in all the Sinope devices, I don't see it in the code, but under the
Electrical_Measurement_Cluster_ID, the AC Frequency field exists and is not
being queried:
0x0300 l u16
Number should be devided by 100 to get reading in Hz.
Regards
Joel Wener
…
On Wed., May 19, 2021, 11:23 p.m. Eric VanDamme, ***@***.***>
wrote:
> Hi @ericvandamme <https://github.com/ericvandamme> , would these changes
> resolve #4870
> <#4870>
> and #4871
> <#4871>
> as well?
>
> I cannot confirm. I only tested with my Sinope device. So the two devices
> you mentioned I couldn't test. Because it could impact other people's
> implementations if it is merged, I generally don't assume "works as
> intended" and a create a merge request.
>
> I have uploaded a compiled for deCONZ v2.11.05-raspian-buster-beta; if
> you trust such a file from a stranger on the internet. It should work just
> fine. Just need to extract and copy it to the appropriate directory
> (/usr/share/deCONZ/plugins/). You may wish to make a backup of the old file
> first. If it works, I can submit those changes too to catch the next
> release.
>
> libde_rest_plugin.zip
> <https://github.com/dresden-elektronik/deconz-rest-plugin/files/6512634/libde_rest_plugin.zip>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#4889 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AUBXQCVSMQSSAQ3AMSCCA5LTOR6DHANCNFSM45BHIGEQ>
> .
>
|
|
While testing the data validity, I came across an issue with the RMS Current Reading : It is showing 63568, as the value for current, but in deCONZ, it is showing 848 -> 0.848 amps. Should be pulling from field 0x0508 | u16 and divided by 1000. "3": { For the plugs with SP2610ZB, the RMS voltage value located in 0x0505 needs to be divided by 100 to get the proper reading. It currently is read as: "voltage": 12333, which should be 123.33 volts (The RM3250ZB currently shows the value directly/correctly, so no modification is necessary for the RM3250ZB). The current value as displayed: current": 5464, is read as 71 in deCONZ. So I am not sure how the value for current is derived. There is something wrong with the RMS Current translation as with the RM3250ZB . ZHAPower **************************** Object info ***************************** Regards |
SwoopX
left a comment
SwoopX
left a comment
There was a problem hiding this comment.
Thanks for raising the PR. The current changes would require some monir corrections as per my comments. Furthermore, as it has been previously mentioned, the values reported by the API are off and require some additional changes in electrical_measurement.cpp. Lastly, to no expose instantaneous demand (as the device doesn't support it, so power in the ZHAConsumption sensor to be more precise), it should be explicitly excluded in de_web_plugin.cpp, L6789 and database.cpp, L3451.
With that taken into account the device should do just fine.
| if (modelId == QLatin1String("SmartPlug") || // Heiman | ||
| modelId == QLatin1String("902010/25") || // Bitron | ||
| modelId == QLatin1String("SKHMP30-I1") || // GS smart plug | ||
| modelId == QLatin1String("SP2610ZB") || // Sinope smart in-wall outlet |
There was a problem hiding this comment.
Based on your screenshots, the device doesn't support instantaneous demand, so this line should be removed.
| rq.maxInterval = 300; | ||
| if (modelId == QLatin1String("SmartPlug") || // Heiman | ||
| modelId == QLatin1String("SKHMP30-I1") || // GS smart plug | ||
| modelId == QLatin1String("SP2610ZB") || // Sinope smart in-wall outlet |
There was a problem hiding this comment.
Based on your screenshot, I doubt this is the correct reportable change, which should reflect the value of 1 Wh. On the other hand, multiplier and divisor for the value are both 1, which would conclude a value of 56636 kWh going purely by the math, however, attribute 0x0303 is also not yet taken into account (which basically tells you where to set the decimal point).
There was a problem hiding this comment.
The value being stored in the Z2610ZB in this field is in Wh, even though it is configured as if it is in kWh. The value being sent seems to be correct.
|
@ericvandamme I am ready to test any changes this evening so that the final version can be submitted for tomorrow's deadline. |
|
I will certainly be able to look at it this long weekend, I don't think I will have time before the deadline tomorrow. I will also be seeking out something with a fixed power draw to test the results. |
|
Hi, thanks for the work on this and no rush :) There are quite some more betas coming out in roughly 1 week intervals so the PR can be added in v2.12.1-beta or v2.12.2-beta. |
Thank you. Have a great long weekend. |
|
It looks as if @joelwener has taken to completing the changes with all devices which he can test independently. I am closing my PR to avoid conflicts. |
|
Hi, Just to be sure, is SP2610ZB fully supported (including power report) ? Did I miss something ? |
|
This PR was closed to use instead #4943 |
|
Your right. Using DDF we can go further than just On/Off control. Thanks |
6 participants
Tested and working with Sinope Smart in-wall outlet – Zigbee SP2610ZB (https://www.sinopetech.com/en/product/smart-in-wall-outlet-zigbee/). Should address issue #4880 as well.