07.07.2024, 09:09 (This post was last modified: 07.07.2024, 09:34 by arturfra.)
Hi,
i can't control my umidity sensors because home kit wants "scale" datatypes instead my sensors want "byte floating", how could i resolve the issue?? TNX in advance
i can't control my umidity sensors because home kit wants "scale" datatypes instead my sensors want "byte floating", how could i resolve the issue?? TNX in advance
Hi,
You need to create an event script for conversion using a virtual object.
i can't control my umidity sensors because home kit wants "scale" datatypes instead my sensors want "byte floating", how could i resolve the issue?? TNX in advance
Hi,
You need to create an event script for conversion using a virtual object.
i can't control my umidity sensors because home kit wants "scale" datatypes instead my sensors want "byte floating", how could i resolve the issue?? TNX in advance
Hi,
You need to create an event script for conversion using a virtual object.
tnx for reply, could you post an example ??
Try something like this:
Consider 1/1/1 the umidity value and 32/0/0 the virtual object for home kit
Event script on 1/1/1
Value = event.getvalue()
grp.update('32/0/0',(math.modf(Value)),dt.scale)
07.07.2024, 13:08 (This post was last modified: 07.07.2024, 13:31 by arturfra.)
(07.07.2024, 11:57)CristianAgata Wrote:
(07.07.2024, 11:05)arturfra Wrote:
(07.07.2024, 10:45)CristianAgata Wrote:
(07.07.2024, 09:09)arturfra Wrote: Hi,
i can't control my umidity sensors because home kit wants "scale" datatypes instead my sensors want "byte floating", how could i resolve the issue?? TNX in advance
Hi,
You need to create an event script for conversion using a virtual object.
tnx for reply, could you post an example ??
Try something like this:
Consider 1/1/1 the umidity value and 32/0/0 the virtual object for home kit
Event script on 1/1/1
Value = event.getvalue()
grp.update('32/0/0',(math.modf(Value)),dt.scale)
tnx indeed ! It works...
for reading the values OK but now i've to write the desidered humidity value and i've to convert from scale to floating byte, the opposite.. how i should go forward ? Tnx
i solved:
Value = event.getvalue()
grp.update('2/0/9',(math.modf(Value)),dt.float16)
After pairing Homekit-app with Apple Homekit, Apple Homekit writes that this bridge is not certified to use with Apple Homekit. Not that it matter - it works perfectly well. Just curious if this is a bug in my setup or it's the way it supposed to be.
do you plan to add door but with toggle function. most of our installation are made with only knx delayed output (pulse) for control, and a contactor on input device. It is the most common use for controlling easily a door. this function is on other controller like jeedom, has, confortclick... should be great to have it also (only to variable control toggle and feedback)
-----------
FRANCE SMARTHOME & SMARTBUILDING INTEGRATION
SE ECO EXPERT
Hi.
I've set up my phone (Android) with the Google Home app, and with the connection in the LM app (old) I can control every object without being on the WiFi. But when I set up my girlfriends iPhone with the Apple Home Kit and the same LM app the Apple Home objects says "No repsons" and are NOT controllable as soon as I turn off the WiFi.
Should this be a feature or is it purhaps just Apple that handles it this way.
When WiFi is off, I am still able (via my GFs iPhone) to use the Mosaic app on the LM app, and control the object, but again; all the object in the Apple Home app is not controllable.
Hi, I'm trying to integrate the LM into Homekit, but I can't pair it. I add an accessory, scan the QR code, it says connecting, and after a few seconds I get an error: "Accessory not found." What could be the problem? I have version 20240426. Do I need to update/add a package?
08.09.2025, 16:41 (This post was last modified: 08.09.2025, 19:45 by EjvindHald.)
Hi Daniel & Co
I have been using Homekit for several years, and switching to LM implementation is quite tempting, as it is very easy to setup. However, before doing that I have observations and requests, which I hope you will consider to add.
Identification of an entity via serial number
In the LM Homekit app I add a description, so I later can recognize it. Example could be Living Room Ceiling Spot, Kitchen Ceiling Spot and Children Ceiling Spot. When these are in the iPhone Homekit app, I move the items to the proper room, and change the name to
"Ceiling Spot" due to limitation of text lenght in Homekit. At that point it would be great to have a identification back to the original item via the serial number in Homekit. The applies to many types and not only light in the ceiling. You are already populating serial by a number which I can see via the LM Storage Viewer. However, other non certificed integrations like openHAB or Homebridge is using strings in serial number which is great. I suggest to use the description excluding spaces in the LM Homekit app as a serial number.
Security System
The Security System has 4 modes, and LM supports all these. However, it is possible to only select some of these modes, and then fewer modes are available in the iPhone Home app for selection. This is supported by mqttthing, and it works great. See link https://github.com/arachnetech/homebridg...ity-system where it is called "restrictTargetState". I hope you will consider to add this as well.
Air Purifier
LM has the air purifier, and this is only implemented by very few solutions. LM has all attributes except 3 related to the filter, which is supported in the iPhone Home app. You can read more on the implementation of this on the link https://github.com/arachnetech/homebridg...r-purifier and I am using FilterChangeIndication, FilterLifeLevel and ResetFilterIndication. I hope you will consider to add these.
The Homebridge mqttthing is open source, so I hope you can find inspiration for the actual code in the repo, I have linked to.