I continued testing VINDSTYRKA and noticed one more thing:
The unit for VOC in openhab is specified by default in mg/m³.
My measured values are between 10 and 421.
When I looked for recommended values for apartments for this value, the range is from 0-10 mg/m³.
This has already been discussed in another smart home forum. (Link1) A description of the manufacturer of the sensor is also linked there. (Link2)
It says:
“The VOC Index describes the current VOC status in a room relative to the sensor’s recent history.” […] "The VOC Index performs a similar calculation by using a moving average over the past 24 hours (called the “learning time”) as offset. " […]
“Therefore, the VOC Index adapts its gain according to the VOC events of the past 24-hours learning time, leading to different VOC conditions being quantified on the same limited scale: a VOC Index ranging from 1 to 500. In this way, one can use a fixed mapping of the VOC Index to an action the device should execute (for instance, triggering an air purifier when the VOC Index is above 150).”
Thanks, good finding! I didn’t payed too much attention till now.
The attached document describes quite well the voc-index and that i’t not connected to a specific unit. This fits also to the description of zigbee2mqtt for VINDSTRYKA where units for Temp, Humidity and PM25 are explicit mentioned but VOC index has no unit.
Also docs in github are showing a baseline of 100 when VOC conditions are stable.
So I’ll remove the unit in the next days and provide a simple Number as voc-index.
Thanks for reporting and decrease the untested devices in the list! Just pay attention to the upcoming changes for VINDSTRYKA voc-index in the current discussion.
Hi. Today morning my Dirigera gateway lost connection to Openhab, with the following status message:
Status: OFFLINE COMMUNICATION_ERROR
Gateway HTTP Status disconnected due to inactivity.
I was also not able to reinitialize Dirigera Thing by Enable/Disable, stucked in “Initializing” status. Openhab restart helped.
Anyone got this issue?
Or maybe this is standard behavior and there is a way to keep the connection alive?
I’ve noticed that Dirigera F/W was updated few days ago to 2.753.0.
Nothing much seems to happen here. I see very few answers to other questions as well.
Where should I post discussions like this in order to reach the right audience?
Best Regards - Misi
jwiseman
(Mr. Wiseman (OH 4.3.0 Snapshot on Pi4))
67
FYI, the binding is getting tweaked big time by the developer and the OH code reviewers. This has been going on for over a month now from GitHub changes.
Not sure where it stands for being re-released though
First depends on your installed version. Version 0.3 has major stability update from Nov. 2024. Watchdog checks each 15 secs if gateway can be reached and is answering properly. Starting and stopping thing is doing nothing different.
Enabling trace log level would help to see if any supicious is happening during. Maybe you had some exceptions in your trace?
Correct location to dicuss here, last 2 weeks were just extremely busy.
Yes, this is the current behavior. DIRIGERA behaves very instable when performing parallel calls. Maybe they improved but I need to test if 3 parallel OFF calls to different lights are possible in order to switch them out simultaneously. So each call takes approx 250ms and and in a sequential way this behavior matches with your observation.
In future I want to support also the IKEA device sets but I haven’t figured out yet how to support them in openHAB.
This pattern is working for your use case but in case of errors, e.g. if 2 lights are responding and one not, the item will reflect a wrong state.
Please check group item
for each light add a seperate power item
create a group item with member base type Switch
add all items you want to have in that group
You can now send towards the group an OFF command which will be distributed to all group members.
This will not solve your reported delay but you’ll have a clean handling for each single light and all lights in your bedroom.
While searching for possible solution I found info about possible OAuth authentication issue in OH v4.3.4 that I use. This issue impacts general Openhab performance, so I guess it’s nothing to do with DIRIGERA binding itself.
The latest fixes to OAuth will be patched in OH v4.3.5.
Thank you for your thorough response. I wanted to do a lot of things that require much faster response, such as dimming lights when a button is pressed. But the sluggish response through Dirigera makes it hard to use…
Maybe I need to skip the Dirigera and work directly against the various bulbs etc through a Zigbee USB stick or something like that? That should be much faster, right?
But how about the dimming remotes from Ikea, can I connect them to OpenHAB without Dirigera?
Seems so as @Pedro_Liberal stated I personally don’t have Zigbee USB stick.
But I checked now the parallel execution and it seems to work. Looks like Ikea introduced several improvements. I would like to ask you to check the new version from top post so please deinstall and then install again from Marketplace to get the new version.
I can confirm that the lamps in the group now turn off at the same time . This is a big improvement.
It is not fast enough for my dimming though. I do long press to dim the lights, and when I release the button after reaching desired brightness, it continues to change the light for another 1-2 seconds…
. This is a big improvement.