Sensor_temperature_air, 49/1/1, C: reports 5 degrees too high, calibration does not work (whatever I set as value for calibration, the setting will snap back to either 1 oder 255), insanely high threshold (3-112-1-41) of 1310976 and upper limit (3-112-1-49) of 18350336, and not possible to change them. Sensor_sun_ultraviolet, 49/1/27, no unit: always 0 indoors AND outdoors. This * sensor is the second most important to me for automation to determine how bright the light bulbs should illuminate. Not sure how accurate that is, but it seems to do something. 3 with some light, 127 with a flashlight in front of it. Sensor_illuminance, 49/1/3, Lux: reports 0 in a dark room. This is somewhat interesting to display in the bathroom. Sensor_humidity_air, 49/1/5, RH: reports in deltas of 1, not sure how accurate the reported values are. Sensor_battery_level, 128/1/0, %: always 100 when on USB power, no batteries were included. If that does not work, all is lost with this sensor. Motion sensing is the most important part for me.
#Homeseer update multisensor 6 how to#
Is is a bug in zwave2mqtt, is there a mapping missing somewhere? If I cannot do anything about it, what would you propose how to use such reports in home assistant to still get a state change for motion sensor entity? T09:35:14.998Z z2m:Zwave zwave node 3: changed: 113-1-7:Unknown:Unknown -> Unknownīottomline you get a state change from unknown to unknown, which is not helpful at all to detect the motion. 11:35:14.997 Detail, Node003, Notification: ValueChanged
11:35:14.997 Detail, Node003, Changes to this value are not verified 11:35:14.996 Detail, Node003, Refreshed Value: old value=0, new value=0, type=list 11:35:14.996 Info, Node003, Received Notification report (>v1): Type: Unknown (7) Event: Unknown (0) Status: true, Param Length: 0 11:35:14.996 Warning, NotificationCCTypes::GetAlarmType - Unknown AlarmType 7 11:35:14.995 Warning, NotificationCCTypes::GetEventForAlarmType - Unknown AlarmType/Event 7/d 11:35:14.995 Warning, NotificationCCTypes::GetAlarmNotificationTypes - Unknown Alarm Type 7 11:35:14.672 Info, Node003, ApplicationCommandHandler - Unhandled Command Class 0x20 Sensor_alarm_home_security, 113/1/7, no unit: always reports "unknown", sends a report when motion is detected, so I assume it is the PIR motion detector.
Seems to have no function at all, at least I don't see any immediate reports on this one, but maybe it is the tamper sensor that works differently? I thought it was about vibration sensing. In the end I had to look at what zwave2mqtt detected, and what was sent to MQTT.īut I am not at all sure that what is detected is right:Ĭomment: PIR is configured to “Basic Set” not “Binary Sensor Report”, if this makes a difference.īinary_sensor_contact, 48/1/0, boolean, always reports "false", but only together with other sensor values. There are a lot of quirks when you look at the sensor readings and settings detected by zwave2mqtt and what is promoted to Home Assistant for auto discovery. OpenZWave 1.6.974 binary addon for Node.JS. Using Aeotec Multisensor 6 with Firmware 1.13 paired with Aeotec Zstick Gen 5