I’m running a Raspi 4B, with 8GB and OH 5.0.1 directly on the Pi. Since I have WLAN connection issues I’ve connected as well a WLAN-USB extension and that problem vanished. For Zigbee I’ve connected directly a SLZB-07 and bound it with Ember Coordinator. I’ve connected 6 temperature sensors from Sonoff (SNZB-02P/D) and one power plug from INNR (SP 240-2).
My main problem is the connection lost of the sensors. They are connected properly after restart for some time and then the sensor are obviously not any longer connected. The temperature line remains on the same level (as well for the humidity values). For one or two sensors this seems reasonable because they are outside the range but for the remaining ones I have no clue what to do.
Analyze the sensor data shows a single straight line even when I zoom into the period (e.g 4h). This single straight line gives me the clue that the stick has lost the connection to the sensors. The data won’t remain on exactly the same level for that long. I’ve tried as well to plug the stick into an USB cable with additional extension but the behavior remains the same/similar.
The situation is little bit fuzzy since I don’t get an “exact” time stamp when the connection is lost. Most of the time its half a day or even longer. I was hoping to improve the situation with the INNR power plug since it mentioned to be a Zigbee bridge. But the situation remains the same.
- Is there a better indicator for loosing the connection beside the straight line?
- Is there as well some state which gives a clue about the connection quality? With the Mosquitto it seems there is a Linky Quality Indicator - but this cannot run at the same time as the Zigbee binding.
- Is there a way to see if the sensors are connected to the INNR or directly to the coordinator?
- Are some advises or hints which I could check - and most likely improve my situation?
and last but not least: it seems like some unicode characters are not displayed properly in my WebBrowser (FF connected via https://home.myopenhab.org/). Any idea how to display them correctly?
Hi,
The first thing that catches my eye is the device you are showing in the screenshot does not appear to have been discovered correctly.
the SNZB-02 is a battery-operated device and it currently shows as being mains powered that is not correct. I would try removing the device and then reset it and discover it again be patient during the pairing process and allow it plenty of time to complete. If the device does not discover correctly, it likely will not reliably report.
I would start there and make sure all your devices are discovered with correct power source.
you can create an item that uses the last changed as a date time type and it will show you the last time the value was updated. as a quick indicator if the device is reporting changes in value.
This is not correct. You can run a mosquito MQTT broker at the same time as ZigBee binding. What you cannot do is use the ZigBee binding and the zigbee2mqtt external app connected to the same coordinator at the same time. You can have 2 coordinators as well; they should also be set up on 2 different channels to prevent interference. However, keep in mind a device can only be connected to one coordinator at a time also.
Not from the UI using the Zigbee binding. There are some commands that you can run from console that can give more information, but I do not recall if that will show child parent relations off the top of my head.
You can also set the logging for the binding to a more verbose level to also give more insight to what is occurring.
Although I think its a good starting point, I don’t know what the “correct” power source would look like. I’ve checked my other sensors and they all report the same type. Therefore I wonder if they could even have a different one.
I really like the idea of this approach. Are there some practical hints how to achieve this? Because what I understand from this approach is that I need to have a Thing which displays the time. Honestly I have no idea what that Thing could be.
Thanks for the clarification about the MQTT broker because I now I understand why my previous setup failed. I cannot run on one coordinator two different Bindings.
This is what one of my Sonoff SNZB-02 temp sensors discovered as and displays it is a real one came in the orange box not a knock off. I allowed discovery via UI.
No, you just need to add a duplicate item to the channel you want to get last changed time on not a new time thing.
this is the code for a last updated time item I created for it.
label: Temperature
type: DateTime
category: Temperature
groupNames: []
tags:
- Point
when I linked the duplicate item for the temp
I set it up like this and I formatted the time to how I wanted it to display in metadata pattern with this
%1$tH:%1$tM:%1$tS %1$tm.%1$td.%1$tY
you may want something different
I modified a widget to provide the update so I see this
Hope this answers your questions
