New Plugin - [pimatic-raspbee]

---

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'
}
``

@mwittig thx nice work

@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"
}

@mwittig Yeah, you’re right. The best solution would be a combined device.
My ali order with some xiaomi devices is already on the way.

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.

@sweebee are there tiny (< 8cm) contact sensors like the Kerui D026 based on zigbee?

@sweebee and @mwittig thanks for the replays, and how about ZigBee compared to esp modules?

@saxnpaule said in New Plugin - [pimatic-raspbee]:

@sweebee are there tiny (< 8cm) contact sensors like the Kerui D026 based on zigbee?

The smallest one I found is the Fibaro sensor.
https://www.amazon.de/dp/B072PD3GTH/ref=asc_df_B072PD3GTH51537329/?tag=googshopde-21&creative=22398&creativeASIN=B072PD3GTH&linkCode=df0&hvadid=231998698971&hvpos=1o2&hvnetw=g&hvrand=10587978858226583131&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9041573&hvtargid=pla-360538719984&th=1&psc=1

But 40 EUR per sensor is really expensive compared to < 6 EUR for the D026.

@zomer I think, the biggest difference is when you look at battery powered sensors. It is not easy to achieve reasonable battery lifetime with ESPs.

As long as those battery’s will last a long while, this certainly is a huge advantage as I won’t be restricted by the location of my power sockets.

@saxnpaule said in New Plugin - [pimatic-raspbee]:

@sweebee are there tiny (< 8cm) contact sensors like the Kerui D026 based on zigbee?

Xiaomi has a Door/Window Sensor which you can get on AliExpress for about 8 Euros.
I have a pair of these and contributed a device implementation to support this as part of pimatic-raspbee

@mwittig Yes, but they are much bigger than the D026. I have additional 2mm left at my installation. So the sender shouldn’t be bigger/thicker than the Kerui.

I also sent back the MAX! contacts because they are really huge.

@saxnpaule said in New Plugin - [pimatic-raspbee]:

Yes, but they are much bigger than the D026. I have additional 2mm left at my installation. So the sender shouldn’t be bigger/thicker than the Kerui.
I also sent back the MAX! contacts because they are really huge.

No. The length is 4.1 cm and the width is about 2 cm. The height of the magnet is 0.7 cm and the width 1 cm.

Okay, that sound really good. It looks much bigger on the pictures.

@saxnpaule Yes. The “new” Aquara sensor is at about the same size. See
https://community.smartthings.com/t/xiaomi-vs-aqara-door-window-sensors/90738

It looks like it is slightly wider. Besides this the differences are:

• the new one should indicate the battery level. The old one doesn’t
• the one has button for pairing while the old one has a pin hole.

hey guys,
version 0.0.6 is released!

• support for aqara/xiaomi sensor devices
• some bug fixes

(0.0.5 has a bug, do not install !)

The biggest WAF is when you take time for the woman’s birthday weekend and neglect the smarthome. So I was offline for a few days

But @sweebee has been busy and has implemented new devices.
At this point a big thank you!

The raspbee api provides a generic interface. see here
Once all resource types are implemented, all devices should work vendor independent.

I have only received an aqara temperature sensor so far. But I’m impressed by that little one.
In the next days I will add more functions.

@kosta does the scene action provider not work for you? in my installation in works fine.

@sweebee
I didn’t have any errors in my development environment either.
but when i updated my production to 0.0.5, all the rules had a parse error.

It was late yesterday and to avoid any risk for the others,
the easiest way was to remove the action-parser.
I will check it this evening.