Hi,
Yes its super basic. I’m just toying with it for now to se what I can actually do before investing more. I dont have any automations yet. I for now would want to see statuses on all of my devices at home using different integrations as I have some sonoffs some smartlife and some smartdgm devices. Also some xiaomi temp sensors so would be good to make them work.
Hah it works, thank you for all the help. It turned out I had a typo in mac instead of F6 I had 6F ;] Now it works great and does not slow down the pi. Weird thing is that it did slow down really bad when it has a typo in mac o.O
Your observation about performance degradation is quite valuable - since in the case of a typo in the mac address most of the code is not executed at all (there is no decryption, and there is no further parsing of the packet either, and the component simply proceeds to the next packet) - we have an almost empty cycle that loads processor due to the fact that it works very fast.
In the next release, I will include a small solution that will delay the empty cycle a bit (by 1 millisecond).
The situation described by you is completely normal.
Since the sensor actually sends data every 10 minutes, my component has nothing to work with, there is nothing to average over these time intervals. If, for example, with a period of one minute, I can not average the data by actual measurements, but will do it with the previous value, then I will violate the main principle of the component - to transmit the actual data updates, not “invented” ones. In addition, even if I do, this will not solve your problem, because there will still be a “jitter moment” (“bounce problem”, 20.01 and 20.00, for example) - therefore this is not a solution to your problem and this is not such a simple question as it might seem at first glance.
A typical solution to the bounce problem is to introduce a delay in operation - that is, you need to introduce a delay in automation. Let’s say turn on the heater after the temperature is below 20 degrees for 5 minutes. But such a solution may not always be feasible (for example, in the case of LYWSD03, a delay of at least 10 minutes more is needed), since the additional delay with an already very slow sensor may be unacceptable - this is another aspect because of which I do not like LYWDS03, and like my LYWSDCGQ (20 measurements per minute!). In the case of Home Assistant, you can also use the last triggered automation attribute or an additional timer (as described here, for example).
I am the control engineer in my daily life, and there is a simple and obvious axiom in this area - to control fast process you need a fast sensor!
@macia10 tell me, do you use cooling radiators on your raspberry pi zero? I ask to make sure that thermal throttling does not taking place in your case.
Hi,
Yes I have a radiator and it gets worm in touch. Just measured it and it’s 39,5C. So most likely there is no throttiling going on there. And my power supply is 2A. Also measured it and it draws around 0.3A and 0.1A then idle.
Hi,
I have also something to add here. As I was toying with the sensor yesterday and changing it’s temp reading all the time it refreshed for me every 5min not 10. Could it be something dependent on the FW?
Hmm. Interesting. Perhaps the frequency of measurements sendings depends on the degree of change. But on my sensors, I did not notice this behavior. I have firmware version 1.0.0_0106, hardware B1.4.
Hello! That means you still have the original mitemp_bt component loaded. Follow the instructions carefully - it says HA should be stopped and started and second restart required (installation, step 3). Such double restart required only first time.
Thank you for your guidance. I’ve joined the device. No error has been reported. But I haven’t found the entity in the developer tool. How can I solve this problem? Thank you
The reasons can be very different. To get started, try placing the sensor as close to the HA host as possible to make sure that poor reception is not the reason. Further, I strongly advise you to read our FAQ (especially this part and this one).
In general, more information is needed to deal with any situation. Describe your installation (hardware, software). Turn on debugging for the component and attach HA log lasting 10-15 minutes.
Hi Alexey, thanks for your work. I am already having a NodeMCU esp32 with Esphome for this, but it is just another device to be powered on, hanging around the house. So decided to give a try to your components. After two days of working in parallel, cannot see any reason not stay on this component and to switch off the esp32.
@schilea Thanks for the positive feedback! Usually, users write to me only about problems, and the feeling begins to appear that the component works well only for me Just kidding )
Can you tell us more about your installation, and how far are the sensors from the host?
@Magalex it is better to draw: pi4 is upstairs, 2m height from the floor on the halway top of the stairs. Sensors are one in the room behind, opposite wall approx 4m, the second one on the room from the right opposite wall, 7 to 8m, while the last one, marked with solid is downstairs, bottom of the stairs an the entrance of living room that is open space. let’s say 4m vertical height and a floor between pi and sensor. There will be another sensor on the room from the left but this is on the way. I have tried to place pi/ node mcu at relative equal distance to the sensors.
Just kidding )
