Qivicon software is fundamentally the same system as openHAB - they are both running ESH under the hood (at least for the newer products - older products used a different system). This is why it is possible to use the ZigBee Binding on the QHB - Iām not sure if it is possible out of the box due to the PID issues, but I will see if I can find some time to test this as I have a few different QHBs here sitting in boxesā¦
Iām aware of that. My point focusses on the hardware strategy they differ (or better which is bundled on qivicon side). And is the common ESH base a reason not to integrate qivicon2 as hardware hub to OH?
No - I didnāt say it was did I? The bindings here should run on QHB as I said. I was merely commenting on your point that openHAB and Qivicon are not similar products when clearly they are running very similar server software.
Ok, just missunderstanding You never said so, Iām just trying to understand why a binding for qivicon seems to make less sense to others than to me
I donāt think anyone said it was a good, bad, or other, idea to have a binding to connect to a Qivicon systemā¦
However, personally I donāt see the need given itās a very similar system - itās like saying āletās have a binding for openHABā. Effectively you would have two instances of ESH running which can be easily connected together with MQTT if thatās what you wanted to do.
Hi Chris,
after playing a bit with the HUE motion sensor some wishes regarding the LED indicator and the battery level have arisen
LED indicator
When paired to a HUE bridge, the LED on the sensor is configured to just blink in case of battery is low or empty (orange==low, red==almost empty, steady red==no connection to coordinator).
When connected to the Zigbee binding, the LED flashes every time when motion is detected.
This is somehow distracting/annoying.
It seems, that Philips has some attribute in the basic cluster
0x0000/0x0033* config.ledindication
which likely is intended to set the āLED modeā.
Battery level
Currently, there is no battery level channel. From some post in another forum:
https://developers.meethue.com/content/philips-hue-motion-sensor-and-zigbee-attributes
I got, that Philips has implemented the power cluster, so probably reading the
u8BatteryPercentageRemaining
could be possible to fill a battery channel.
Here is the list somebody has sniffed from the communication of the sensor with the HUE bridge:
From your sniffer, you should see that the Hue bridge sets up bindings to the bridge for the following clusters on endpoint 02:
- 0x0000 (Basic)
- 0x0001 (Power)
- 0x0400 (Illuminance Measurement)
- 0x0402 (Temperature Measurement)
- 0x0406 (Occupancy Sensing)
Then, it sets up attribute reporting for the following attributes:
- 0x0000/0x0032* config.usertest
- 0x0000/0x0033* config.ledindication
- 0x0001/0x0021 config.battery
- 0x0400/0x0000 state.lightlevel
- 0x0402/0x0000 state.temperature
- 0x0406/0x0000 state.presence
- 0x0406/0x0030* config.sensitivity
*) these are manufacturer specific attributes.
So would it be possible to make the LED configurable, or switch it off completely, or initialize it just similar to Philips (just blink if battery is weak)?
Is a battery channel possible (useful for all battery powered nodes)?
Since this is a custom attribute, thereās no nice way to do this right now. One of the things I will be working on over the next month or two is to add device definitions into the binding so we can define custom functionality like this. This is something that is currently on my todo list, but it will be a month or so away. Hopefully you can live with it till then (or find a piece of sticky tape to cover it over ).
The battery level channel is implemented already in the binding, but if I remember correctly, this attribute is not implemented in the Hue (but it was a while ago when I implemented this so I might be wrong - either way, it didnāt provide the information when I checked it in early December when this was implemented).
Iām currently working on the Tradfri motion sensor which does implement this attribute so I will double check it works there and then have another look at the Hue implementation. Iāll do this in the next day or so.
Sure
As always - youāre already on it
Thanks a lot for all your dedication!
Actually, can you raise an issue for the LED parameter and either reference your post above, or (preferably) paste the info into the issue - then I wonāt forget this when I implement the device definitions, and Iāll easily be able to find the info
Thanks - and just for completeness and visibility in case anyone has any comments -:
On 2.3.0.201801211741, my Centralite outlet is reporting powerā¦ wahoo! Values are updating about every 3s.
Hi, Iām a noob trying to get a cc2531 to connect to a hue bulb.
I have tried everything.
Can you look at my log file?
I think? the issue is āUnhandled ZToolPacket type 0x45cbā? Just a noob guess.
Thanks!
23:12:26.495 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ManagementPermitJoiningRespon
ESS]
23:13:26.463 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 01 45 CB 00 8F)
23:13:26.467 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
F, checksum=8F, error=false
23:13:26.469 [DEBUG] [ee.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45cb
400_MHZ], macCapabilities=[FULL_FUNCTION_DEVICE, MAINS_POWER, RECEIVER_ON_WHEN_IDLE, ALTERNATIVE_PAN
pleDescriptorListAvailable=false]]
23:11:45.562 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- ZB_GET_DEVICE_INFO_RSP (FE 09 66
23:11:45.575 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - 3556D79E8ACBCF90: ClusterMatcher star
23:11:45.580 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsyste
00 00 00 03 00 02 30 1F 03 00 00 00 05, checksum=05, error=false)
23:11:45.730 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
23:11:45.734 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> ZB_GET_DEVICE_INFO (Packet: subsy
07 26, checksum=26, error=false)
23:11:45.738 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 07 45 83 00 00 00
23:11:45.744 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
0 00 00 00 10 C1 10, checksum=10, error=false
23:11:45.753 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32771, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 10 C1]
23:11:45.759 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: PowerDescriptorResponse [0/0
AddrOfInterest=0, powerDescriptor=RECEIVER_ON_IDLE, [MAINS], MAINS, FULL]
23:11:45.766 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Power Descriptor returned PowerDes
, status=SUCCESS, nwkAddrOfInterest=0, powerDescriptor=RECEIVER_ON_IDLE, [MAINS], MAINS, FULL]
23:11:45.772 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Discovery request POWER_DESCRIPTOR
23:11:45.774 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ActiveEndpointsRequest [0/0 -
23:11:45.780 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress
=5, addressMode=DEVICE, radius=31, sequence=3, payload=00 00 00]
23:11:45.865 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 0E 45 FF 00 00 00
23:11:45.868 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
00 00 03 80 00 00 00 00 00 00 00 10 C1 E6, checksum=E6, error=false
23:11:45.880 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32771, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 10 C1]
23:11:45.891 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: PowerDescriptorResponse [0/0
AddrOfInterest=0, powerDescriptor=RECEIVER_ON_IDLE, [MAINS], MAINS, FULL]
23:11:45.898 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- ZB_GET_DEVICE_INFO_RSP (FE 09 66
23:11:45.907 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - 3556D79E8ACBCF90: ClusterMatcher addi
23:11:45.911 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsyste
00 00 00 05 00 03 30 1F 03 00 00 00 02, checksum=02, error=false)
23:11:46.055 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
23:11:46.058 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 07 45 85 00 00 00
23:11:46.060 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
0 00 00 00 01 01 C7, checksum=C7, error=false
23:11:46.065 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32773, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 01 01]
23:11:46.075 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ActiveEndpointsResponse [0/0
AddrOfInterest=0, activeEpList=[1]]
23:11:46.085 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Active Endpoints returned ActiveEn
, status=SUCCESS, nwkAddrOfInterest=0, activeEpList=[1]]
23:11:46.088 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Scheduling endpoint discovery
23:11:46.091 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 0E 45 FF 00 00 00
23:11:46.093 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Discovery request ACTIVE_ENDPOINTS
23:11:46.094 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Starting endpoint discovery
23:11:46.108 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: SimpleDescriptorRequest [0/0
endpoint=1]
23:11:46.097 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
00 00 05 80 00 00 00 00 00 00 00 01 01 31, checksum=31, error=false
23:11:46.121 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32773, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 01 01]
23:11:46.119 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Ending node discovery
23:11:46.122 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ActiveEndpointsResponse [0/0
AddrOfInterest=0, activeEpList=[1]]
23:11:46.123 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress
=4, addressMode=DEVICE, radius=31, sequence=4, payload=00 00 00 01]
23:11:46.145 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsyste
00 00 00 04 00 04 30 1F 04 00 00 00 01 01, checksum=01, error=false)
23:11:46.313 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
23:11:46.318 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 0E 45 84 00 00 00
23:11:46.320 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
00 00 00 00 08 01 04 01 00 00 00 00 00 C3, checksum=C3, error=false
23:11:46.324 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32772, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 08 01 04 01 00 00 00 00 00]
23:11:46.333 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: SimpleDescriptorResponse [0/0
kAddrOfInterest=0, length=8, simpleDescriptor=SimpleDescriptor [endpoint=1, profileId=0104, deviceId
sterList=[]]]
23:11:46.344 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Simple Descriptor returned Simpl
NULL, status=SUCCESS, nwkAddrOfInterest=0, length=8, simpleDescriptor=SimpleDescriptor [endpoint=1,
lusterList=[], outputClusterList=[]]]
23:11:46.348 [DEBUG] [m.zsmartsystems.zigbee.ZigBeeEndpoint] - 0/1: Setting input clusters []
23:11:46.353 [DEBUG] [m.zsmartsystems.zigbee.ZigBeeEndpoint] - 0/1: Setting output clusters []
23:11:46.359 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 15 45 FF 00 00 00
00 27)
23:11:46.362 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0: Discovery has completed all endpoi
23:11:46.365 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
00 00 04 80 00 00 00 00 00 00 00 08 01 04 01 00 00 00 00 00 27, checksum=27, error=false
23:11:46.368 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - 00124B000E896936: Node 0 is added to
23:11:46.374 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32772, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 08 01 04 01 00 00 00 00 00]
23:11:46.382 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: SimpleDescriptorResponse [0/0
kAddrOfInterest=0, length=8, simpleDescriptor=SimpleDescriptor [endpoint=1, profileId=0104, deviceId
sterList=[]]]
23:11:46.422 [DEBUG] [rnal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: done.
23:11:46.425 [DEBUG] [gbee.internal.ZigBeeNetworkDiscoverer] - 0/1: Ending endpoint discovery
23:12:26.135 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coord
23:12:26.139 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - Permit join to 65532/0 for 60 seconds
23:12:26.147 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementPermitJoiningReques
tion=60, tcSignificance=true]
23:12:26.153 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress
ster=54, addressMode=DEVICE, radius=31, sequence=5, payload=00 3C 01]
23:12:26.159 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsyste
FF 00 00 36 00 05 30 1F 03 00 3C 01 09, checksum=09, error=false)
23:12:26.306 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
23:12:26.309 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementPermitJoiningReques
=60, tcSignificance=true]
23:12:26.311 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress
=54, addressMode=DEVICE, radius=31, sequence=6, payload=00 3C 01]
23:12:26.313 [DEBUG] [531.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsyste
00 00 00 36 00 06 30 1F 03 00 3C 01 09, checksum=09, error=false)
23:12:26.473 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
23:12:26.476 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 03 45 B6 00 00 00
23:12:26.478 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
0 00 F0, checksum=F0, error=false
23:12:26.484 [DEBUG] [ee.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45b6
23:12:26.487 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 0A 45 FF 00 00 00
23:12:26.489 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
00 00 36 80 00 00 00 00 00 06, checksum=06, error=false
23:12:26.492 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress
=32822, addressMode=null, radius=0, sequence=0, payload=00 00]
23:12:26.495 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ManagementPermitJoiningRespon
ESS]
23:13:26.463 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 01 45 CB 00 8F)
23:13:26.467 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem
F, checksum=8F, error=false
23:13:26.469 [DEBUG] [ee.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45cbe
Thereās nothing obviously wrong that I can see from the log - itās just not joining. Have you completely reset the bulb?
My ST motion sensors wonāt join although they are in join mode. When I hold reset while connecting the battery, they sort of join, but only show the temperature channel.
Properties:
zigbee_logicaltype END_DEVICE
zigbee_powerlevel FULL
modelId motionv4
zigbee_networkaddress 5241
zigbee_powersource MAINS
zigbee_zclversion 1
zigbee_routes []
zigbee_lastupdate 2018-01-23T12:58:01Z
vendor SmartThings
zigbee_powermode RECEIVER_ON_IDLE
zigbee_permitjoining false
zigbee_powersources [MAINS]
zigbee_neighbors []
zigbee_devices []
Has the Hue bulb been used before? If it has, you might need to reset it for which you need the Hue dimmer remote.
It canāt āsort of joinā - it looks like itās joined okā¦
Thereās not much I can say without seeing a log. I can guess that maybe some request failed somewhere and it didnāt detect all the attributes it wanted to provide the other channel. At the moment these sort of requests arenāt retried so it isnāt as tolerant to errors as it should be (Iāll look at this in future).
If you restart, it should again detect the features and should work. Otherwise, Iāll need to see a log - maybe your device is different than the one I used for testing.
I tried restarting already, no new channels. I have a log, but it was too big for the forum. Iāll open an issue on github. I have this sensor: https://www.bestbuy.com/site/samsung-smartthings-motion-sensor-white/4481806.p?skuId=4481806
Ok, thanks. Iāll take a look once you post itā¦
Nope. Brand new out the box. Just turn them on during discovery mode correct?