There should not be any difference between heating and auto mode so that's why the control is binary.
We've only implemented most common features because we don't have the actual device to test the integration. Which other features are you missing?
03.10.2024, 13:51 (This post was last modified: 07.10.2024, 08:12 by hepa.)
(03.10.2024, 13:31)admin Wrote: There should not be any difference between heating and auto mode so that's why the control is binary.
We've only implemented most common features because we don't have the actual device to test the integration. Which other features are you missing?
That is not correct unfortunately. The auto mode is controlled by week timers and what not, the only functional mode on this heater is "Manual", where the heater is working after the given setpoint, so this is absolutely necessary for basic operation.
What we would like for our implementation is KeypadLockout and DisplayAutoOffActivation.
EDIT: As it is now, we have no way of setting the panel heater back to manual when the user changes to auto, neither any way to block local user input.
Hello Community. Has anyone tried this sensor with LM? I would like to know in order to implement it in a project. I have a bare board CC2531 from TI with firmware (Z-Stack_Home_1.2 20211115/20211116) CC2531_DEFAULT_20211115 from github
SE hardware has special modifications and our zigbee apps are also different. Due to hw none compatibility we do not share our app as SE users like you might want to use it and have issues.
Contact SE support for both topics.
SE hardware has special modifications and our zigbee apps are also different. Due to hw none compatibility we do not share our app as SE users like you might want to use it and have issues.
Contact SE support for both topics.
ok thanks but I also have Lmachine on our company, not only SL HL
-----------
FRANCE SMARTHOME & SMARTBUILDING INTEGRATION
SE ECO EXPERT
I've tested several zigbee thermostats and none of them work properly.
The last one I tested complies with the Zigbee 3.0 standard but doesn't work either.
Can you integrate one?
I'm looking for a thermostat with an outdoor temperature sensor.
the last file
Vir (33)Vimar - WheelThermostat_v1.0 - device information
I have 1 Tradfri bulb that works just as expected, both value status and onoff status. All good. Also RGB (and perfect RGB-status, thanks to admin!)
So when I got that one working, I bought a bunch of Philip Hue bulbs, thought they would for sure work. Except that they dont... I have four different kinds, and neither of them give status. If I go to "Control & status" on the zigbee page and click "Read" on device status, then the group adresses are updated correctly. But not from me sending on/off or brightness value.
I don't quite understand what I'm doing wrong, since I'm sure "everyone" has these bulbs... They are all listed here: https://kb.logicmachine.net/misc/zigbee-devices/ (except that manufacturer is "Signify Netherlands B.V." and not Philips, but I guess that goes for all of them). And the Tradfri works perfect...
Drop the device information from the zigbee app. If manufacture is different then it is a new device for us. All my Philips are Philips as manufacture.
(11.11.2024, 11:30)Daniel Wrote: Drop the device information from the zigbee app. If manufacture is different then it is a new device for us. All my Philips are Philips as manufacture.
Trying to integrate GU10 RGB Lights from EMOS (Legrand). Device is being detected as "TuYa - LED Strip Controller (RGB/CCT)". Everything seems works fine except one thing. Once lamp is added to LM/Apple Home, I am unable to set it to full brightness as it was before pairing. It do reacts on brightness control in Apple Home or from LM zigbee interface but it is not so bright as I would like to (as before pairing). Why?
(11.11.2024, 11:30)Daniel Wrote: Drop the device information from the zigbee app. If manufacture is different then it is a new device for us. All my Philips are Philips as manufacture.
Hi Daniel!
Is the change of manufacturer name the reason that my status GA's are not updating? If so, can I assume this will be fixed in the next app version sometime?