@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.
New Plugin - [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.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
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:
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
hey guys,
version 0.0.6 is released!
(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 @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
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!
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
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.
Pimatic, my hobby.
@kosta said in New Plugin - [pimatic-raspbee]:
xAttributeOption is on the way with next release.
see pending PR
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
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 ?
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.