🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

i'm not sure if the error is on the cloud adapter or this one, but i'm afraid it's a problem of the deconz-adapert.

I'm not able to add my Osram Smart+Plug to the cloud-adapter, looks like the "on" is set to state instead of switch.

Before it is possible to get an API key it is necessary to save the settings after input of IP and port.

If I add a new scene in Phoscon App the scene is not displayed under the group. Even a restart of deconz instance doesn't help.

Is this a bug or how to update already added groups to see the new scenes?

Thanks

Beat

Hallo erstmal!
Ich sehe an meinem Vorschreiber daß hier auch deutsche Einträge verstanden werden... macht es um einiges leichter für mich LOL !!

Mir ist aufgefallen, daß ich mehrere Objekteinträge (folder) mit teilweise gleichzeitigen Einträgen in den Objekten habe.

Bei den Zwischensteckern von IKEA ist es ein Eintrag
Türkontakte Xiaomi: 1 Eintrag
Bewegungsmelder Xiaomi: 2 Einträge
Taster Xiaomi: 2 Einträge
Temperatursensoren Xiaomi: 3 Einträge

Die einzelnen Folder zeigen, wenn sie doppelt vorhanden sind, gleiche Werte an,
Teilweise gibt es bestimmte Werte auch nur jeweils in einem der Folder

Das ist zwar alles etwas verwirrend und unübersichtlich, aber trotzdem komme ich damit klar,

Ich wollte nur mal wissen, ob das hier bei mir ein Bug ist oder es so vorgesehen ist bzw. bei Anderen ebenfalls so angezeigt wird.

Grüße
Michael

Is the adapter working with Ikea trådefri?
Hardware: RPI 3 and dresden usb stick (ConBee)
I have setup deconz software and linked three device (light bulb, motion sensor and switch) and i see them in deconz we-gui.
I have the deconz adapter loaded and configured.
There is only one objeckt in instances tab.

In the script tab I can see all three objects,

There are five objects because i renamed two of them in deconz!

I need help!

Its ok to answer in German.(google translate works ok)

Ich habe den Conbee2 getestet. Nachdem ich gehört habe, dass Datenpunkte bei diversen Produkten verteilt in verschiedenen Ordnern landen haben ich diverse Produkte in der Phoscon App angelernt und auch gelöscht und mir dazu immer die Datenpunkte im ioB angeschaut. Beim Xiaomi Lumi Plug wird ein Ordner für den Plug unter Lichter im ioB angelegt sowie ein Ordner unter Sensors wo der Datenpunkt für den Stromverbrauch des Plugs drin ist. Mal davon abgesehen, das diese sehr unübersichtlich ist weil man irgendwann gar nicht mehr weis welche Sensoren zu welchen Gerät gehören bleiben bei mir auch Leichen im Bereich Sensoren übrig wenn ich den Plug in der Phoscon App lösche und den Adapter aktualisiere. Der Plug ist dann im Ordner Lichter weg aber der Datenpunkt für den Stromverbraucht ist im Ordner Sensoren noch da. Auch der Adapter Neustart hat nicht geholfen. Erst wenn ich den Stick komplett über die App zurücksetzte sind die Leichen weg. So wie alles Andere auch :-)

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz

• [E118] Versions in package.json and in io-package.json are different
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.deconz"
• [E301] Tests on Travis-ci.org are broken. Please fix.

Thanks,
your automatic adapter checker.

I use version 1.1.1 of the adapter but i had this issue already since upgrading from 0.3.2. The recalling of scenes inside a group is not working. Nothing happens when pressing the "button" in the "objects" list or when sending a "true" to the "recall" button from a script.

The devDependency gulp was updated from 4.0.1 to 4.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gulp is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Ist es geplant diesen Sensor einzubinden?
Beim Zigbee adapter steht er in der Liste der kompatiblen Geräte.
Ich würde mich sehr freuen.

Nach dem Update auf 1.0.1 hat sich die Struktur verändert.
Anstelle von Sensor_2 zum Beispiel auf Sensor/2.
Allerdings werden nicht alle Objekt Attribute mit übernommen.
Es fehlt zum Beispiel der Zeitstempel (Update).
Somit sind meine Scripte nicht mehr lauffähig.

Would it be possible to add the Manufacturer (Ikea, Philipps, Osram..), the Model (ColorBulb, ColorStrip...)the Name of the device and for example the Firmware-Version of the device as a State so it can be used for displaying the device correctly with a AccessoryInformation Service in Yahka?

Hey,

i just got my conbee and connected iobroker with it.
Its working good with fast updates, but one point is not so good.
In my list i have 8 groups with name like "FLS-PP3 helper1 for group 17".
You should not display them in iobroker and skip them in Line 711.

Also the states are a bit confusing, maybe you can create channels for lights, groups and sensors?

Hi,

DJT11LM sends many interesting parameters like state.orientation, state.tiltangle, state.vibration and state.vibrationstrength,

{
	"config": {
		"battery": 100,
		"on": true,
		"pending": [
			
		],
		"reachable": true,
		"sensitivity": 11,
		"sensitivitymax": 21,
		"temperature": 2700
	},
	"ep": 1,
	"etag": "0d5f099e494192253bee48d582bb067c",
	"manufacturername": "LUMI",
	"modelid": "lumi.vibration.aq1",
	"name": "Vibrationssensor Mobile",
	"state": {
		"lastupdated": "2019-04-29T16:33:45",
		"orientation": [
			2,
			-1,
			88
		],
		"tiltangle": 360,
		"vibration": false,
		"vibrationstrength": 8
	},
	"swversion": "20180130",
	"type": "ZHAVibration",
	"uniqueid": "00:15:8d:00:02:b9:32:23-01-0101"
}

and

{
	"config": {
		"battery": 100,
		"on": true,
		"pending": [
			
		],
		"reachable": true,
		"sensitivity": 11,
		"sensitivitymax": 21,
		"temperature": 2700
	},
	"ep": 1,
	"etag": "5a7869a900da7366b0b05f344c3f6993",
	"manufacturername": "LUMI",
	"modelid": "lumi.vibration.aq1",
	"name": "Vibrationssensor Mobile",
	"state": {
		"lastupdated": "2019-04-29T16:42:09",
		"orientation": [
			6,
			-2,
			-83
		],
		"tiltangle": 171,
		"vibration": true,
		"vibrationstrength": 8
	},
	"swversion": "20180130",
	"type": "ZHAVibration",
	"uniqueid": "00:15:8d:00:02:b9:32:23-01-0101"
}

but I do not see it in ioBroker :-(

What am I doing wrong? Can I create and link these objects manually?
Help, I do not know enough yet
Thank you.

Software versions:
deCONZ: / 2.05.64 (on Raspbian)
ioBroker.deconz: 1.0.2

The devDependency gulp was updated from 4.0.0 to 4.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gulp is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

You have to check your scene settings. New scenes will only be created if the lightcount is greater than 0. If the state of your light(s) in the scene is off, the count is 0.

There is no way back to 0.4.0

Hi

I've checked again my scenes and all of them have lights and the state is not off. Please see screenshot.

Could you please let me know if this should work like that and that I should see all scenes under my groups?

Thanks

Beat

Originally posted by @easybeat in #43 (comment)

The restAPI does not seem to work properly when setting hue and sat values. It changes the color of the light, but does not update the hue and saturation datapoints.

It may be an option to generate extra datapoints "convertedHue" and "convertedSat" which are driven by either the ct value, if the light is in "ct" mode, or the xy value, if the light is in "xy" mode. Internally, the idea is to generate a message to the restAPI changing the xy value to one calculated from convertedHue and convertedSat if these datapoints are changed in ioBroker, and in return populate these datapoints with hue/sat values calculated from either the color temperature or the xy coordinates reported by the restAPI.

Generation and use of these datapoints could be configurable in the plugin, and would only apply to lights which report color present.

https://github.com/iobroker-community-adapters/ioBroker.deconz/blob/8b0afa01f1ea6996361cf21ca19db6a4de11c523/main.js#L1143

In der Funktion getSensor(sensorId) wird im switch unter "temperature" keine Verarbeitung vorgenommen, daher werden in iobroker Temperaturänderungen von Sensoren (bei mir Xiaomi) nicht aktualisiert.
Ein eifnaches Copy / Paste von humidity reicht aus um den Bug zu fixen.

Frage: Wieso werden trotz websocket die ändernungen jeweils über ein neuen request abgefragt und nicht direkt aus dem WS Objekt genommen? Ich habe gesehen, dass im WS Objekt der Name des Sensors nicht vorhanden ist. Könnte man das nicht resourcenschonender gestallten in dem man eine Temporäre Liste irgendwo zwischenspeichert mit ID und Name vom Sensor und somit nur dann ein neuer http request gemacht werden muss wenn der Sensorname unbekannt ist.
Einzige "Gefahr" sehe ich, dass so Namensänderungen ggf. nicht sauber übernommen werden

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz

• [E116] No SPDX license found. Please use one of listed here: https://spdx.org/licenses/
• [E117] Licenses in package.json and in io-package.json are different
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.deconz"
• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E405] Icon must be in the following path: https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz/master/
• [E407] Meta URL(latest) must be equal to https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz/master/io-package.json
• [E426] Icon(stable) must be in the following path: https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz/master/
• [E428] Meta URL(stable) must be equal to https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.deconz/master/io-package.json
• [E802] No topics found in the repository. Please go to "https://github.com/iobroker-community-adapters/ioBroker.deconz" and press "Manage topics"
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2019 Jey Cee [email protected]" at the end of README.md

Thanks,
your automatic adapter checker.

Would it be possible to also include recalling scenes from deconz?
I find that setting up scenes for me in Phoscon is easier and more reliable than using the scenes adapter.

testing show an error ... missing dep?

https://travis-ci.org/Apollon77/ioBroker.deconz/jobs/324301916

Hi,

I updated the adapter from 0.2.5 to 1.0.2. Now there is a problem with deconz 2.05.60. I can control devices (for example switch wallplug), but I do not get any updates from the devices (state of wallplug, temperature, humidity, ...)
There are no errors in the log.
I switched back to 0.2.5 and all is working again.

Changing the xy datapoint on a hue lamp causes a warning from the restAPI:

2019-01-08 17:17:56.716 - debug: deconz.0 stateChange deconz.0.Light_1.xy {"val":"0.245041,0.242574","ack":false,"ts":1546967876711,"q":0,"from":"system.adapter.admin.0","lc":1546967876711}
2019-01-08 17:17:56.717 - debug: deconz.0 dp: xy; id:Light_1
2019-01-08 17:17:56.726 - info: deconz.0 setLightState: {"transitiontime": 0, "xy": "0.245041,0.242574"} 1 deconz.0.Light_1.xy
2019-01-08 17:17:56.738 - debug: deconz.0 STATUS: 400
2019-01-08 17:17:56.739 - info: deconz.0 options: {"url":"http://localhost:80/api/78CC3AFC48/lights/1/state","method":"PUT","headers":"Content-Type\" : \"application/json","body":"{\"transitiontime\": 0, \"xy\": \"0.245041,0.242574\"}"}
2019-01-08 17:17:56.739 - debug: deconz.0 setLightState BODY: [{"error":{"address":"/lights/1/state/xy","description":"invalid value, 0.245041,0.242574, for parameter, xy","type":7}}]
2019-01-08 17:17:56.740 - warn: deconz.0 Set light state with ID: 1 parameter: {"transitiontime": 0, "xy": "0.245041,0.242574"} Code 400: Bad request

The target value was copied from the setting of the object, but the formatting in the message does not match up with the formatting in the response to getLightState:

debug: deconz.0 getLightState: {"ctmax":500,"ctmin":153,"etag":"e720da66da458021a7b387fa0e21c362","hascolor":true,"manufacturername":"Philips","modelid":"LCT015","name":"Hobby Room Color","state":{"alert":"none","bri":254,"colormode":"hs","ct":153,"effect":"none","hue":40655,"on":true,"reachable":true,"sat":168,"xy":[0.234363,0.289572]},"swversion":"1.46.13_r26312","type":"Extended color light","uniqueid":"00:17:88:01:03:12:4d:c3-0b"}

Using the Adapter version 0.3.1 i have an issue when changing the color of Philips hue lamps attached to a raspbee:

If i change the hue through the phoscon app, the hue value changes in the range of 0 to 65535.
if i try to change the hue from ioBroker, i can only enter values between 0 and 360. These will change the hue of the lamp, but deconz updates the value with 0 to 65535.

for me, this fix:

Fixing hue from range 0-65535 to 0-360

did not work.

Hallo.
Mir ist aufgefallen, da0 die Temperatursensoren von Xiaomi keine Batteriedaten ausgeben, auch wenn das in den Objekten vorgesehen ist.

Grüße
Michael

Hi,

i had bought some Xiamoi Motion Sensors. After adding them to phoscon it generates 2 Objects in iobroker (e.g. Sensor_2 & Sensor_3). Its not a problem at all, but maybe its a bug ;)

The dependency ws was updated from 6.1.4 to 6.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ws is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi all,
i have been reading through the issues and discussions on button press event handling in the adapter, and have come up with an idea which might be easy enough to implement and give a major improvement to the use.

The idea is to implement an extra datapoint, just for sensors which have the "type": "ZHASwitch" set in their native descriptor. This datapoint is set when an update message is received through the rest-API, but not on initial load of the adapter. Setting the datapoint activates a timeout of 1 second to reset the datapoint. It will not work for catching multiple button presses, but with the current setup, those cannot be caught either.
The added load on the system by having these 1 second timeouts should be neglectible.

A.

Ich habe gerade das Update auf die Version 1.0.1 durchgeführt.
Das Dimmen von Gruppen ist nun nicht mehr möglich.
Wenn ich einen ...bri Datenpunkt ändere werden die Lampen nicht gedimmt. Das dimmen der Lampen einzeln über den jeweiligen solo Datenpunkt .bri ist möglich.
Wenn ich die Lampen in der Phoscon APP dimme wird auch nicht der korrekte Wert in ioBroker angezeigt.

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

I use deconz gateway v2.0.5.28 and have a xiaomi motion sensor connected to the gateway.
The motion sensor works as expected, when motion is detected, states in deconz and iobroker are updated accordingly. Unfortunately this isnt the case for lightlevel and lux which the sensor provides. The value is updated in deconz, but the update isnt reflected in iobroker.

As you can see by the timestamp, the state for presence is updated while the lux state is not. I have testes this with a longer timeframe than just a few minutes, the state hasnt changed over 24 hours with significant changes in deconz for lux value. These screenshots are just from my last test before opening this issue.

https://pasteboard.co/Hosrz1P.png
https://pasteboard.co/HosuWaM.png

Is there any way to update all states, when an update in deconz occurs?

Wie kann ich ein Device löschen? In der Phoscon App geht es ohne Probleme. Wenn ich ihn aber über den ioBroker lösche, kommt folgende Meldung: "
deconz.0 | 2019-05-09 11:32:54.090 | info | Delete light with ID: 6 Code 404: Ressource not found

Wird der Vibrationssensor von XIAOMI unterstützt? Bei mir legt er nur 2 Devices an, aber nichts mit objects for "tiltangle", "vibration", "vibrationstrength" and "orientation"

Hallo.
Ich habe hier 12 Trådfri-Zwischenstecker im System.
Zwei von denen schalten sich an und eine aus, wenn ich ioBroker neu starte.
Das ist unabhängig davon, ob die Stecker vorher an- oder ausgeschaltet waren.

Es ist definitiv der deconz-Adapter, nicht die Phoscon-App die die Schaltung vornimmt.
Der Schaltvorgang ist beim booten der Raspberry in der log. ersichtlich.

"type": "string", this field is not a string

look at: https://forum.iobroker.net/topic/22205/gel%C3%B6st-zeichenkette-in-zahl-umwandeln-aqara-deconz-vibrationssensor-winkel/25

thank you

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

states should be named "unique" to be used with the cloud-adapter etc.
example: https://github.com/Somberland/ioBroker.deconz/blob/feature/name_fix/main.js

Sensors does not set a expire time for reachable and it is not possible to ping the sensors. So we have to set a expire on client side.

Examples here: https://github.com/ioBroker/ioBroker.discovery/blob/master/lib/adapters/zwave.js

Is it possible to group one sensor to one folder in ioBroker objects? Many values like battery, reachable and so on are holded multiple times for the same sensor. Would be better to handle when they would be grouped in ioBroker even when deconz api split them in multiple devices. You could use the Sensor Name as Identifier. Maybe with an adapter option where u can decide the object behaviour?!

Don't get me wrong, the adapter is nice and it worked this way too, but with many sensors it is much nicer to handle. In the zigbee Adapter it worked like that for example.

Das Dimmen von Gruppen über den Adapter ist wieder möglich.
Wenn eine Änderung über die Phoscon APP durchgeführt wird, dann wird diese Änderung nicht nach ioBroker übertragen. Wenn die Lampe aus und wieder ein geschaltet wird stimmt der aktuelle Dimmwert.

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Hi,

in the function getSensor the adapter is generating ghost clicks by updating the buttonevent (due to the fact the function getSensor is called on websocket messages and these are also used to report temperature/battery). In order to avoid this I added this to the case buttonevent:

                        case 'buttonevent':
                            adapter.setObjectNotExists(`Sensor_${sensorId}` + '.' + stateName, {
                                type: 'state',
                                common: {
                                    name: list['name'] + ' ' + stateName,
                                    type: 'number',
                                    role: 'state',
                                    read: true,
                                    write: false
                                },
                                native: {}
                            });
                                 if (stateName == 'buttonevent' && list['modelid'] == 'lumi.sensor_switch.aq2') {
                                      //paalap: new
                                      let LastUpdate = Number(new Date(list['state']['lastupdated']));
                                      let Now = Number(new Date().getTime());
                                      let dateoff = new Date();
                                      let TimeOffset = dateoff.getTimezoneOffset() * 60000;

                                      if ((Now - LastUpdate + TimeOffset) < 2000) {
                                      adapter.setState(`Sensor_${sensorId}` + '.' + stateName, {val: list['state'][stateName], ack: true});
                                      //adapter.log.debug('buttonevent updated, time diff: ' + ((Now - LastUpdate + TimeOffset)/1000) + 'sec update to now');
                                      } else {
                                           adapter.log.info('buttonevent NOT updated for ' + list['name'] + ', too old: ' + ((Now - LastUpdate + TimeOffset)/1000) + 'sec time difference update to now');
                                      };
                                 } else {
                                       adapter.setState(`Sensor_${sensorId}` + '.' + stateName, {val: list['state'][stateName], ack: true});
                                 }
                                 //paalap: instead of 
                                //adapter.setState(`Sensor_${sensorId}` + '.' + stateName, {val: list['state'][stateName], ack: true});
                            break;

May be this could be included in similar form to the code :)

If you send e.g. two new values to a light the first one is reverted.

Assume you;d to switch the color temp and the level inside a script.

setState('deconz.0.Lights.6.bri', bri, false); setState('deconz.0.Lights.6.ct', ct, false);

The lamp will inc the level for a few millisec an then fall back to the original value. This will also happend if the second setState will be inside the callback.

Volker

Please add battery status for battery operated device.

Irgendwie wird der Wert meiner Sensoren "lastupdated" immer in UTC (Universal Time) erzeugt.
Die eingestellte Local-Time wäre hier der bessere Wert.

Im Phosconapp ist die Uhrzeit die richtige (local-time).
Andere Trigger von anderen Adaptern laufen auch mit der richtigen Zeit (local-time).