general.xml changes for innr SP120 missing from v2.05.30

[ebaauw]

The Smart Energy domain needs to be added to the ZLL profile, see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/432#issuecomment-395757777.

[manup]

Ok, will be added to 2.05.31 scheduled later tomorrow :)

[ebaauw]

@manup, can you please use this file: general.xml.zip?

It also contains some additional multipliers and divisors for the Electrical Measurement and Simple Metering clusters (only supported by the Heiman smart plug), and the Window Covering cluster 0x0102, used by the Xiaomi curtain (see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/593#issuecomment-390404203).

[manup]

It's merged now and finally the general.xml is now part of the public repository :)

[ghost]

I use a Innr SP 120-plug with Deconz v2.05.31 and Home Assistant 0.74.2 (hass.io w/docker), and are not getting any power measurments from the plug. The only attributes I get from light.Innr_plug_1 in Home Assistant are brightness: 254 min_mireds: 153 max_mireds: 500 effect_list: colorloop friendly_name: Innr_plug_1 supported_features: 41 And no sensor-entity like sensor.Innr_plug_1 that I get from other power metering plugs like from Fibaro or Hank.

[Kane610]

Same for me, no power measurement with Innr SP120

[Gnaget2]

i dont get any power measurement with Innr SP120

deconx 2.05.31 and the innr SP120 reports version 2.0

using Home assistant 0.75.0_

[ssahlender]

Same with: Version 2.05.34 / 8.8.2018 Firmware 261F0500

When I use the Rest API I don't get any measurement not matter if I query /sensors or /lights.

At least for lights I get some output: "1": { "etag": "", "hascolor": false, "manufacturername": "innr", "modelid": "SP 120", "name": "Innr SP 120", "state": { "alert": "none", "bri": 25, "on": true, "reachable": true }, "swversion": "2.0", "type": "On/Off plug-in unit", "uniqueid": "" },

[ebaauw]

Is uniqueid really empty, or did you edit that?

Looks like the plug hasn't been fully configured by the REST API. Could you open the network/search for devices in the web app/Phoscon app, and re-read the Basic cluster in the deCONZ GUI? That should trigger the creation of the /sensors resources.

If not, try resetting and re-pairing the plug. If that doesn't help either, could you please post screenshots from the deCONZ GUI showing the node and its endpoints and clusters, the Node info panel, and the Custer info panel for the Basic cluster (after reading the attributes)?

[Kane610]

This re-read basic cluster is mentioned a lot, (almost like a silver bullet) could we get that available through Phoscon in some way @manup ?

[ssahlender]

@ebaauw Thanks for the quick reply ... I removed it ... here is the full output "1": { "etag": "b54ea3ef4d021de1803b00746e19149c", "hascolor": false, "manufacturername": "innr", "modelid": "SP 120", "name": "Innr SP 120", "state": { "alert": "none", "bri": 25, "on": true, "reachable": true }, "swversion": "2.0", "type": "On/Off plug-in unit", "uniqueid": "00:15:8d:00:02:17:bd:2c-01" }, Sorry about the question ... but how do I

re-read the Basic cluster in the deCONZ GUI

[ssahlender]

@ebaauw Ok ... found it here: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/593

In the web app, click the Open Network button on the Settings page (under Menu in the upper right corner. Then, in de deCONZ GUI, go to the Cluster Info panel of the Basic cluster and press the Read button. That should trigger the creation of the ZHAPresence /sensors resource.

Still quite tricky ... even with that description ... but it is working now

"10": { "config": { "on": true, "reachable": true }, "ep": 1, "etag": "ca8f1d5e3e95945d4334538e5f427d09", "manufacturername": "innr", "modelid": "SP 120", "name": "Consumption 10", "state": { "consumption": 0, "lastupdated": "2018-08-08T21:44:28" }, "swversion": "2.0", "type": "ZHAConsumption", "uniqueid": "00:15:8d:00:02:17:bd:2c-01-0702" }, "11": { "config": { "on": true, "reachable": true }, "ep": 1, "etag": "02056a04136b6b6f101df783dcf7b829", "manufacturername": "innr", "modelid": "SP 120", "name": "Power 11", "state": { "current": 0, "lastupdated": "2018-08-08T21:44:39", "power": 0, "voltage": 241 }, "swversion": "2.0", "type": "ZHAPower", "uniqueid": "00:15:8d:00:02:17:bd:2c-01-0b04" } }

Thank you

[ebaauw]

This re-read basic cluster is mentioned a lot, (almost like a silver bullet)

Still quite tricky ... even with that description ... but it is working now

To create resources, the REST API plugin needs to receive a message from the node while the network is open (for the REST API plugin). If you previously paired a node with an older version of deCONZ, it will only create the newly supported resources under these conditions. The read of the Basic cluster attributes causes such a message and makes sure the Model Indentifier attribute has been read, which is used for whitelisting nodes for /sensors resources.

could we get that available through Phoscon in some way @manup ?

Tricky. The REST API (on which Phoscon and the web app are based) is asynchronous - it only queues ZigBee requests, but does not wait for the response from the ZigBee network. In particular a GET only returns previously cached values. We'd need a new endpoint (on both the /lights and /sensors resource?) to issue the request, and a web socket notification when the response has been received. Then the app should wait for the notification, perhaps retrying on timeout, and issue a message when it's done (or fails).

[Kane610]

@manup @ebaauw I think this is quite important to implement this feature, moving away from the desktop all together. Most people running raspberry pies are definitely locked out of using the desktop in an easy manner especially when using the rasbee.

[LordVoodoo]

Hey folks,

I have just unpacked a new Innr SP120 and do not get any power measurement. I have already updated to v2.0.5.35 and deleted the plug in Phoscon App, followed by pairing it again.

Wenn accessing the sensor section (/sensors) not entry is listed, in the /lights part, I get:

"27":{ "etag":"9e8cb3f37bd5706ad0d7a.....................", "hascolor":false, "manufacturername":"innr", "modelid":"SP 120", "name":"Wohnzimmer Ladestation", "state":{"alert":"none","bri":254,"on":false,"reachable":true}, "swversion":"2.0", "type":"On/Off plug-in unit", "uniqueid":"00:15:8d:00:01:fe:55:98-01" }

How can I force Deconz to integrate the power consumption? Even further: After joining the Innr a second time, I did not had to enter a readable name again, it was still "Wohnzimmer Ladestation".

[kasteleman]

Just added the SP 120

It is added as a ZLL device.

As the picture shows cluster 0702 ( Metering cluster (0×702) ) is unknown.

I used the device in Homey and there it is defined as HA. Also then the metering cluster is defined and readable.

Further on I want to write to the following attribute in order to get the reporting working:

I got this info from INNR.

Any suggestion to get this to work would be very appreciated!

On 22 Aug 2018, at 21:58, LordVoodoo notifications@github.com wrote:

Hey folks,

I have just unpacked a new Innr SP120 and do not get any power measurement. I have already updated to v2.0.5.35 and deleted the plug in Phoscon App, followed by pairing it again.

Wenn accessing the sensor section (/sensors) not entry is listed, in the /lights part, I get:

"27":{ "etag":"9e8cb3f37bd5706ad0d7a.....................", "hascolor":false, "manufacturername":"innr", "modelid":"SP 120", "name":"Wohnzimmer Ladestation", "state":{"alert":"none","bri":254,"on":false,"reachable":true}, "swversion":"2.0", "type":"On/Off plug-in unit", "uniqueid":"00:15:8d:00:01:fe:55:98-01" }

How can I force Deconz to integrate the power consumption? Even further: After joining the Innr a second time, I did not had to enter a readable name again, it was still "Wohnzimmer Ladestation".

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/654#issuecomment-415159814, or mute the thread https://github.com/notifications/unsubscribe-auth/AFpiKPdk_0MnjBcUSo5bI9f4jENTKn1yks5uTbflgaJpZM4U0u4K.

[ebaauw]

It is added as a ZLL device.

Because it is a ZLL device (or, more precisely, the profile ID on the endpoints is set to ZLL). That's why it also works with the Hue bridge (contrary to the SP 110).

As the picture shows cluster 0702 ( Metering cluster (0×702) ) is unknown.

You don't have the latest general.xml. Are you running the latest version of deCONZ?

Further on I want to write to the following attribute in order to get the reporting working

The latest version of deCONZ sets up the attribute reporting alright. As always, it might take a little while.

[manup]

@manup @ebaauw I think this is quite important to implement this feature, moving away from the desktop all together. Most people running raspberry pies are definitely locked out of using the desktop in an easy manner especially when using the rasbee.

The problem with the basic cluster is, that sadly often we just can't read the basic cluster since devices may be sleeping or not supporting reading it at all (Xiaomi). Waking up a device is very device specific, some wake up periodically and send reports (here we can jump in) or might be triggered by pressing a button..

In my opinion a button won't fix the problems and is too geeky for the Phoscon App.

We need to improve:

• Collect which devices cause problems
• Querying of missing attributes after a device wakes up
• Improve or add proper setup wizards

[kasteleman]

I’m on deconz 2.05.20 Ubuntu Linux, you want me to switch to beta?

On 23 Aug 2018, at 19:52, Erik Baauw notifications@github.com wrote:

deCONZ

[ebaauw]

Support for the SP120 is in the latest beta. I'm not sure about availability of the Ubuntu releases, I'm on Raspberry.

[kasteleman]

That did the trick. Now it shows the right info for the clusters, but the values are not visible in de Phoscon app. What am I missing?

On 23 Aug 2018, at 20:15, Erik Baauw notifications@github.com wrote:

Support for the SP120 is in the latest beta. I'm not sure about availability of the Ubuntu releases, I'm on Raspberry.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/654#issuecomment-415517201, or mute the thread https://github.com/notifications/unsubscribe-auth/AFpiKA7sc4RfzaddcKFCv57R965Yzh4Xks5uTvE1gaJpZM4U0u4K.

[ebaauw]

Not sure if the measurements are supported by Phoscon yet.

[manup]

The values are not visible in the Phoscon App yet.

[kasteleman]

Ah yet! That pops up the question: estimate?

;-)

Op do 23 aug. 2018 om 22:29 schreef Manuel Pietschmann < notifications@github.com>

The values are not visible in the Phoscon App yet.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dresden-elektronik/deconz-rest-plugin/issues/654#issuecomment-415560668, or mute the thread https://github.com/notifications/unsubscribe-auth/AFpiKG3J-kV4Y1OZvMFi9nLeAgMy6JYiks5uTxCdgaJpZM4U0u4K .

[jo-me]

Hi, I'm on

RPi2 + Conbee Version 2.05.35 Firmware 261F0500

and just tried to add a Innr SP120 plug. The "light" part showed up but no sensors.

Tried to remove it from the DB and re-add it but did not help.

Any ideas? Will it fix itself after a while or does deconz need to have the info right away?

Thanks

[ebaauw]

If it shows in the REST API, but not in Phoscon, it will fix itself once Phoscon supports it. If the /sensors resource doesn't show in the REST API, you'll need to re-pair the device, once the REST API supports it.

[jo-me]

@ebaauw : it does not show up under sensors. Do you mean I just have to try paring until I get lucky? Or is something missing in deconz that currently prevents this alltogether?

[ebaauw]

Changes have been made and general.xml is now included in deconz-rest-plugin package.

[Kane610]

What is the process to get the sensor? Remove and readd?

[ebaauw]

What is the process to get the sensor? Remove and readd?

I'd try powering down all routers, and re-pairing the plug close to the RaspBee/ConBee, but it might be tricky without the GUI to force-read the Basic cluster attributes.

Make sure you're on a recent version of deCONZ, preferably with firmware 0x26230500.

Most people running raspberry pies are definitely locked out of using the desktop in an easy manner especially when using the rasbee.

All my Raspberry Pies are headless, but I still run the graphical environment over VNC. I set Authentication to VNC Password and created /etc/avahi/services/rfb.service, so they're discovered and working with macOS Screen Sharing (incl. shared cut/paste buffer). With ScreenSharingMenulet, they're only a mouse click away.

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
    <name replace-wildcards="yes">%h</name>
    <service>
        <type>_rfb._tcp</type>
        <port>5900</port>
    </service>
</service-group>

[Kane610]

Then I wait a couple of weeks before upgrading to deconz and firmware. Still sounds like a lot of luck to me. I'm running headless through docker so no option of GUI for me.

[Gnaget2]

still no power sensor on my inner sp120 added a third one yesterday with 2.35.39 and latest FW (405).

running deconz web app with conbee