Thanks. Ordered from that webshop. 49 euros total. But hopefully I can remove all the gateways. Hue bridge, TRÅDFRI hub and aqara gateway.
-
New Plugin - [pimatic-raspbee]
-
Hi,
thats nice and i test your plugin on the next weekend.
MfG.PS.: I have my raspee ordered by amazon-germany.
Pimatic, my hobby.
-
Hi,
-
over VPN have i install your plugin OK
-
unlock deCONZ—find the devices OK
-
the hue plugin need i in the moment (i`m not at home and my wife need the livingroom lights )
-
with hue and raspbee plugin active have i this startup error:
error [pimatic-raspbee]: { [Error: getaddrinfo ENOTFOUND mia mia:443] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'mia', host: 'mia', port: '443', __trace: 'Error: From connect\n at Socket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)\n at Agent.exports.connect.exports.createConnection (net.js:68:26)\n at Agent.createSocket (_http_agent.js:180:16)\n at Agent.addRequest (_http_agent.js:149:23)\n at new ClientRequest (_http_client.js:142:16)\n at Object.exports.request (http.js:31:10)\n at Writable.RedirectableRequest._performRequest (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/node_modules/follow-redirects/index.js:61:20)\n at Writable.RedirectableRequest (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/node_modules/follow-redirects/index.js:45:7)\n at Object.wrappedProtocol.request (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/node_modules/follow-redirects/index.js:176:10)\n at dispatchHttpRequest (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/lib/adapters/http.js:130:25)\n at initializePromise (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/-internal.js:244:5)\n at new Promise (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/promise.js:135:31)\n at httpAdapter (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/lib/adapters/http.js:19:10)\n at dispatchRequest (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/node-hue-api/node_modules/axios/lib/core/dispatchRequest.js:52:10)\n at tryCatch (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/-internal.js:195:12)\n at invokeCallback (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/-internal.js:210:13)\n at /home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/then.js:24:16\n at flush (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/node_modules/es6-promise/dist/lib/es6-promise/asap.js:94:5)\n at nextTickCallbackWith0Args (node.js:436:9)\n at process._tickDomainCallback (node.js:406:13)' } 21:17:26error [pimatic]: Invalid config of device "id-raspbee_tradfriremoute": Property "buttons" is not a valid property 21:17:26error [pimatic]: Invalid config of device "id-raspbee_tradfridimmer": Property "buttons" is not a valid property
-
the hue devices are in funktion
MfG.
Pimatic, my hobby.
-
-
@sweebee Well, if you can replace all the gateways with this one please let me know!!
Been looking for something like this for a while now, but didn’t want to commit to one brand… -
Hi @kosta,
i update my pi`s with your new version and over vpn works it good (store the apikey, no error messages). In real life test i this weekend. Good and quick work!MfG.
Pimatic, my hobby.
-
Hi @kosta,
i install the update 0.0.4 of my 2 pi`s. When i start pimatic have i the pimatic error in the log-file.
error [pimatic]: Invalid config of device "id-raspbee_wireless_dimmer": Property "buttons" is not a valid property 10:51:26
error [pimatic]: Invalid config of device "id-raspbee_remote_control": Property "buttons" is not a valid property
MfG and thank you for the plugin.
Pimatic, my hobby.
-
@kosta thank you, the new version is running well. I just had to open the gateway again after the update and everything is working fine.
I’m also having a feature request for your plugin:
Can you also implement a device for the combined temperature and humidity sensor? I can’t to do it on my own, but I can try my best to help, if your willing to implement this.Xiaomi Aqara Temperature Humidity Sensor
I have just added this device succesfully to the raspbee gateway and with some (unprofessional) curl commands within shellsensors I managed to display the temperature, humidity and pressure in pimatic.
Here are the commands I have used to get the values:
{ "attributeName": "temperature", "attributeType": "number", "command": "curl -s http://IP-Adress:Port/api/xxxxxxxxxx/sensors/3 | json_pp | grep temperature | sed -s 's/,//g' | awk {'print $3'} | sed 's/..$/.&/'", "interval": 120000, "id": "xiaomi-sensor-temperature", "name": "Xiaomi Sensor Temperature", "class": "ShellSensor" }, { "attributeName": "humidity", "attributeType": "number", "command": "curl -s http://IP-Adress:Port/api/xxxxxxxxxx/sensors/4 | json_pp | grep humidity | sed -s 's/,//g' | awk {'print $3'} | sed 's/..$/.&/'", "interval": 120000, "id": "xiaomi-sensor-humidity", "name": "Xiaomi Sensor Humidity", "class": "ShellSensor" }, { "attributeName": "pressure", "attributeType": "number", "command": "curl -s http://IP-Adress:Port/api/xxxxxxxxxx/sensors/5 | json_pp | grep pressure | sed -s 's/,//g' | awk {'print $3'}", "interval": 120000, "id": "xiaomi-sensor-pressure", "name": "Xiaomi Sensor Pressure", "class": "ShellSensor" }, { "variables": [ { "name": "temperature", "expression": "$xiaomi-sensor-temperature.temperature", "type": "number", "unit": "°C" }, { "name": "humidity", "expression": "$xiaomi-sensor-humidity.humidity", "type": "number", "unit": "%" }, { "name": "pressure", "expression": "$xiaomi-sensor-pressure.pressure", "type": "number", "unit": "hPa" } ], "xAttributeOptions": [], "id": "xiaomi-sensor", "name": "🌡 Badezimmer", "class": "VariablesDevice" }
Thank you in advance
-
Hi @Fabian,
it´s a nice sensor. My question´s are: the price ( okay google) and how long (distance) can you send from sensor to gateway?Thanks & schöne Ostern!
Pimatic, my hobby.
-
@kosta thank you. I’m quite excited to test the device.
@Jens the sensor is very nice. I had no problems at all (by now… ). I have spent 13 USD on aliexpress. The distance seems to be good. It is placed in the bathroom separated by one wall at about 8 meters distance to the gateway. I will test it in more detail by placing the sensor for some time to my basement and share my findings.
Greetings and happy easter
-
@Jens okay, the reachable distance seems to be amazing. The gateway is placed at 2nd floor and the sensor is in the basement. 3 walls and about 15 m distance, and the sensor is doing well.
-
I have managed to get my fingers on this and added support for contact sensors.
I have tested this with the “old” (no battery status indication) Xiaomi Mi Aqara Window Sensor.https://github.com/treban/pimatic-raspbee/pull/5
{ config: { battery: null, on: true, reachable: true, temperature: null }, ep: 1, etag: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', manufacturername: 'LUMI', modelid: 'lumi.sensor_magnet', name: 'OpenClose2', state: { lastupdated: '2018-04-01T19: 43: 22', open: true }, type: 'ZHAOpenClose', uniqueid: '00: `xx: xx: xx: xx: xx: xx: xx-xx-xxxx' } ``
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@kosta said in New Plugin - [pimatic-raspbee]:
Yeah, that’s no problem. I can implement these device types.
This sensor appears as three sensors on the network. Ideally, it would be nice to have this as a single logical device in pimatic, i.e., a MultiSensor similar to what pimatic-mysensors provides with
MySensorsMulti
. Additionally, it would be nice to allow for the discovery to automatically detect the multi sensor. That is the tricky bit. Apparently, the grouping could be achieved by using the “etag” property or a prefix of “uniqueid” as suggested in #57. I’ll also add my comments to the issue ticket for the record.Temperatue (Original Xiaomi):
{ "config": { "on": true, "reachable": true }, "ep": 1, "etag": "baceb383ac8e25019e439fea82ed501e", "manufacturername": "LUMI", "modelid": "lumi.sensor_ht", "name": "Temperature", "state": { "lastupdated": "2017-08-05T11:03:18", "temperature": 2411 }, "swversion": "3000-0001", "type": "ZHATemperature", "uniqueid": "00:15:8d:00:##:##:##:##-01-0402" }
Humidity (Original Xiaomi, part of the temperature sensor, so it has the same prefix in uniqueid as the temperature sensor):
{ "config": { "on": true, "reachable": true }, "ep": 1, "etag": "baceb383ac8e25019e439fea82ed501e", "manufacturername": "LUMI", "modelid": "lumi.sensor_ht", "name": "Humidity", "state": { "humidity": 5624, "lastupdated": "2017-08-05T11:03:18" }, "swversion": "3000-0001", "type": "ZHAHumidity", "uniqueid": "00:15:8d:00:##:##:##:##-01-0405" }
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Very interesting to read about the implementation of all this new zigbee hardware trough the raspbee module. I was actually thinking about installing esp8266 units throughout my house with temp, humidity and pir sensors, but those Xiaomi Aqara sensors seem pretty nice and well priced as well. I wonder what would be more reliable, Aqara human body sensor, or esp8266 with a pir sensor. I currently have a kaku pir sensor and that one is absolutely garbage(AWST-6600).
-
@zomer 433mhz is garbage compared to zigbee, also the aqara sensors are build very well, better than the KAKU stuff.
-
@zomer I fully agree on @sweebee’s previous comment.
It should be said that there are other capable technologies like DECT ULE, zWave, WiFi (where it makes sense, SmartPlugs, for example), Bluetooth, Homematic IP. The big plus for ZigBee now, in my opinion, is the availability of relatively cheap lightning devices (Ikea) and sensors (Xiaomi). Before the cost per datapoint was above 30 Euros, now it is less than 15 for sensors. Moreover, thanks to raspbee it is possible to use the technology without vendor lockin and cloud spyware.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law