New Plugin - [pimatic-raspbee]

---

@sweebee @kosta thanks a lot. The RaspBeeMultiSensor is working fine for the Xiaomi Aqara Temperature Humidity Sensor.

Is it possible to a add the features to change the

• acronym,
• lable and
• maybe also the position of the battery state (like the sensorIDs)

by the user?

At last I have recognized that I have to open the gateway and do a automatic device search to get a connection to the raspbee module again after updating the plugin. This is not necessary for the hue plugin. The connection is bulid up by this plugin automatically. Maybe the automatic request of the API-key is the problem…

version 0.0.7 is released!

• new action providers for scenes / light temperature and rgb
• scenes are now button-devices and accessible over the GUI and rules
• acronyms for multisensor

Bugs please @github.

@Fabian I will check this in the next release. I’m thinking about a “new” and flexible mutisensor device.
The current one is for the aqara respectively for temp/hum/pressure combinations designed.

Normally no new connect should be necessary after an update. The API Key is persistent in the config.

@kosta Both new options

• scenes button-device and
• acronyms for multisensor

are working very well. Thank you.

I don’t want to bother, but can you possibly implement also a rounding option for the sensor-device? I think it is neither necessary to show a second decimal place nor the accuracy is given. That will be great.

At last just a info to the mentioned connecting problem. I think this is a very special problem of my setup because I’m running the raspbee module at same raspberry where pimatic is running. I want to run pimatic at port 80 and deConz at port 8080. Therefore I have changed the port settings of the deCONZ software to 8080 but that doesn’t work very well. Only if I start deCONZ after pimatic this is working. So the problem comes up when pimatic is starting and your plugin is trying to reach the raspbee module which is not started yet. By now I don’t think it’s a problem which can be solved by your plugin and it’s maybe solved if the raspbee module is started before pimatic. I will give feedback when I have found a solution.

Hello @Fabian. I will check the improvement of the decimal places. This plugin uses the standard built-in variable device. For pimatic there is already a feature request for configurable decimal places for all devices. I’ll see if I start right there.
I will look at the connection handling from the plugin to check if there is a problem.

Hi @kosta
yesterday I received a xiaomi contact sensor and it is also working without any problems with your plugin. Again, thank you for the amazing plugin.

Can you improve the contact sensor by adding xAttributeOptions? I just want to hide the online info from the gui.

Hi,
thank you for your plugin. How make i a fade in to a dimlevel in a rule?
In the moment work i with this rule:

"when Lichtkomfort is turned on and samsung-tv is present and after sunset starts or when lichtevent is turned on and samsung-tv is present and it is before sunrise then dim id-raspbee-innrA to 10% and dim id-raspbee-lampe-glasbau to 10% and dim id-raspbee-philips-living-iris to 45%"

MfG, Jens.

@Fabian xAttributeOption is on the way with next release.
@Jens the light devices have a transtime option. This is the transition time for all changes. You can play with this option. But this is a global option. I will include a extended dim rule to change it individually.

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

xAttributeOption is on the way with next release.

see pending PR

@mwittig That’s what I meant with: It’s on the way. thx for PR

Hi @kosta
I used the long weekend to test your pimatic-raspbee plugin. Really good job! The xiaomi temperature sensor as ‘RaspBeeMultiSensor’ device and a xiaomi SmartSwitch as ‘RaspBeeSwitchSensor’ was working faultless out of the box without any problems. I’m also able to control the IKEA tradfri bulbs, but not as a group.
If would like to use the ‘RaspBeeCT’ class to dim a group and to change the light temperature for a group.
The Phoscon App provides the dimming and temperature slider for the group, but the device discovery shows the bulb group only as ‘RaspBeeDimmerGroup’ and not as expexted as ‘RaspBeeCT’.
Is this functionality not yet implemented ?

@MrSponti yeah. I will create a extended group device with CT and RGB feature in the next release.

is it normal that ligths are sometimes not visible to the deconz software and produce error in pimatic?
will open a issue on the deconz git repository. Hope they can fix this, or change the behaviour of that…

Hey @Felix-Haverkamp,
I have the problem that after a restart from deconz all devices which are not reachable, for example if the power is off, are removed from the frontend.
But I have not tested if it’s always or only sometimes.

I’m looking forward to buy the raspbee shield and some xiaomi aqara wall switches (to control existing lights), some ‘virtual’ switches (to control smart switches) and together with some zigbee/wifi smart plugs but I have a question:

Is this plugin able to change the status of a smartplug and wall switch (that is not a light that dims, but only on/off)? The idea is to control the smart plug from pimatic given the status of the virtual switch, and also be able to turn on/off the wall switch.

Thanks

@mat1990dj
Thats no problem. The deconz software supports smart-plugs.
Plugs are exposed as light for On/Off.
I have now also ordered an osram smart switch for testing.

But I will create a new simple On/Off device for plugs, because dimming makes no sense,
and add a power consumption variable for devices they support it.

Today my Aqara temp/humidity/air pressure sensor arrived.
Works fine with this plugin, but the shown air pressure is wrong. It shows 9.9kPa instead of 99kPa. In the Phoscon App the value is given by 990hPa what sounds right.

In general I suggest to show the value in hPa instead of kPa. This is more common.

Today the window contacts arrived. Is it possible to add x-Attribute options for the RaspBeeContacSensor? I don’t want to see the “online” status. And hiding it by CSS is not the best way in my opinion.

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

Is it possible to add x-Attribute options for the RaspBeeContacSensor?

It is already in the code base, but it has not been released yet as far as I can see.

https://github.com/treban/pimatic-raspbee/commit/fa3bd1516b9d1607ec7ce2ece32d1d0dc3305a9c

And the bug with kPa vs. hPa?

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

And the bug with kPa vs. hPa?

See https://github.com/treban/pimatic-raspbee/pull/18
This may not be the final solution as I think it is preferable to provide the value in hPa rather than kPa. For this the base measurement unit as part of the attribute devlation needs to be changed accordingly