Thank you everyone, I’ll add these fingerprints to the driver and update some catch-all parts.
1 Like
This is an info log, just turn off info logging if you don’t want these in your logs.
1 Like
Hi Markus,
Can you please add this device to the driver as well?
fingerprint model:“TS011F”, manufacturer:"_TZ3000_00mk2xzy", profileId:“0104”, endpointId:“0B”, inClusters:“0000,0003,0004,0005,0006”, outClusters:“0019,000A”, application:“42”
It’s an Outlet from LIDL.
Also not sure if this is a bug or intended, while the on and off commands are working the toggle command does not. Nothing happens when I try the toggle command. Physically the outlet doesn’t toggle and the status doesn’t update.
Finally I noticed something a bit unexpected with the logs. When I send the on and off commands as expected I see this appearing in the info log. However when the physical button on the outlet is pressed nothing shows up in the info log. It does show up in the list of events and the state is updated correctly.
Not a big deal, but my expectation based on other devices and drivers was that there would be info level logs for status changes.
Hello, which driver is allowing control of the USB ports? I have Markus’s latest generic outlet(w/ presence) and don’t see USB control
Thanks
Hey Markus, Very excited for the new oh-lalabs product.
Anyway using the generic driver for tuya valve & my xbee, I’m getting the "hubaction delay"errors below
sys:12021-01-28 08:06:13.131 pm Unable to execute hubAction:delay 2000 sent from Valve zig 3.0, invalid or unspecified protocol.
app:41732021-01-28 07:51:41.072 pm infoDelay Over: Off: Plug Washing Light → delayed: 0:03:00 (cancelable)
sys:12021-01-28 07:50:05.119 pm Unable to execute hubAction:delay 2000 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.
app:41732021-01-28 07:48:40.973 pm infoAction: Off: Plug Washing Light → delayed: 0:03:00 (cancelable)
app:41732021-01-28 07:48:09.884 pm infoAction: Cancel Delayed Actions
sys:12021-01-28 07:41:19.048 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:41:19.046 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:40:52.139 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:40:52.135 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:12:57.064 pm Unable to execute hubAction:delay 2000 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:12:19.057 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:12:19.055 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:11:52.074 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:11:52.068 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.
sys:12021-01-28 07:06:13.100 pm Unable to execute hubAction:delay 2000 sent from Valve zig 3.0, invalid or unspecified protocol.
I use this driver for Xbee3 devices to able to have presence. When I mentioned the driver on the site I found it on, I was informed the driver is no longer maintained or whatever. The driver I have installed seems to work fine, is this the same as the driver in Package manager or should I use this driver from this site?
1 Like
Welcome to the community! The drivers are the same. Markus is not currently doing much to maintain them because we are not able to update our hubs. But, he does what he can to help where he is able.
2 Likes
Thank you for the welcome and info, I look forward to seeing what you guys come up with for your own platform. If I’m not mistaken, that’s the plan to release your own Hub/Controller? Can’t update your hubs wow its like that, Crazy.
1 Like
yes, we are blocked form updating. As for those issues you’re having, they are related to changes I can’t check since they are in a newer FW than what I can run. I have some changes that may fix parts of it, I’ll see if I push something new in a few days if I get some time, just very hard at work coordinating all our other internal projects.
5 Likes
This has been discussed previously. @markus’ ethical considerations dissuade him from pursuing this course of action. FWIW, I think he is correct.
2 Likes
Yeah I’m not trying to discuss Marcus’s … was asking for my own knowledge but thanks
That wasn’t apparent to me from your post, because you quoted @markus indicating they are blocked from updating with “if you wanted to, couldn’t you just get a new HE …”.
Given the context, it seemed a reasonable presumption that your response was directed to @markus indicating, “yes, we are blocked from updating”.
@aaiyar is a moderator here and he was instructed to shut down these comments. He was only doing what was asked of him. Please take care as tone is easily misunderstood through text. I’m going to assume that was the case here.
That being said, I realize that it’s disheartening to hear what’s happened and our group was very devastated by this outcome. But, we have moved on. We would like everyone to heal from this and share our excitement for what is up and coming.
Markus is working very hard with our crew to get things right. Although we appreciate everyone’s concern about the situation, we’re not dwelling on it. We ask that everyone do the same. I know his absence is felt, but like any of us, we have to balance our time accordingly. The decision was made to prioritize development. Markus will update drivers as he can until someone can more actively support the drivers.
So, Let’s keep this thread on track. I do not anticipate having to step in again. Post for assistance and someone will try to get you some answers.
And I’d also like to say thank you. We do appreciate your ongoing support. Let’s focus our energy on the positive.
8 Likes
Hello,
I really don’t know conetst of this situation. I’m “only” using few great drivers from Oh-La Labs 
so don’t get me wrong but… is it possible to add auto off function in this driver? I’m using it with Aqara LLKZMK11LM
any chance to add CT (and/or RGBW) to the dimmer driver? Would be happy to donate to the cause…
Picked up a few Tradfri outlets today, pairing went smoothly except one (device TypeId: 233) picked the built in driver during pairing, slightly different fingerprint.
Switched it over and seems to be working fine.
COPY AND PASTE THIS ROW TO THE DEVELOPER: fingerprint model:“TRADFRI control outlet”, manufacturer:“IKEA of Sweden”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006,0008,1000”, outClusters:“0005,0019,0020,1000”, application:“20”
Hello, I used a Generic Zigbee Drivers for Aqara SSM-U02 switch (no neutral) and it works but in the logs I get a message:
Unhandled Event IGNORE THIS - description:catchall: 0000 0005 00 00 0040 00 A29D 00 00 0000 00 00 B00000 | msgMap:[raw:catchall: 0000 0005 00 00 0040 00 A29D 00 00 0000 00 00 B00000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A29D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[B0, 00, 00]]
Any idea? thx
fingerprint model:“lumi.switch.l0agl1”, manufacturer:“LUMI”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0002,0003,0004,0005,0006,0009”, outClusters:“000A,0019”, application:“16”
Your answer is in the message, IGNORE THIS, which means it’s an event from a capability that is of no use or is not available on the “it’s your fault stupid-atat elevation” hub." Whatever it is, “it’s all your fault for doing whatever you did-Signed Tech Support”
Seriously tho, it’s nothing to worry about. Many have asked Markus and he said it won’t harm anything, just an unparsed message
1 Like
Zigbee device fingerprints
Driver: Zigbee - Generic Outlet (with Presence)
Company: innr
Model :SP 224
Country :USA
fingerprint model:“SP 224”, manufacturer:“innr”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006,0008,0B05,1000,FC82”, outClusters:“000A,0019”, application:“10”
Driver: Zigbee - Generic Switch (with Presence)
Company: Leviton
Model :DG15S
Country :USA
fingerprint model:“DG15S”, manufacturer:“Leviton”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006,0B05”, outClusters:“0019”, application:“01”
Hi - I read this thread and saw the ‘difficulty maintaining this driver due to Hubitat policy…’ post.
That said - recently I began using Smart Outlets from eWeLink. They seem to sell on Amazon under many names including - Seedan, CMARS. However - I’ve bought all 3 and they all show manufacturer as ‘eWeLink’.
Due to a bug (lack of feature?) in the hubitat Generic Driver, my outlets were showing errors in Watchdog if they didn’t get used. I was told this was due to a Refresh problem. Using your driver solved that!
But it introduced a new issue - when I write rules, and select a presence device as a rule component, I have to dig through the list of presence detectors to find the presence devices necessary. What I mean is I don’t need the ‘Presence’ part of your driver.
In addition - the outlet driver from you gives 2 other weaknesses - no Identify (or Flash it is sometimes called) and no Toggle. Both features exist in the generic Hubitat driver.
First - the fingerprint I got when running Generic Device Toolkit:
fingerprint model:“SA-003-Zigbee”, manufacturer:“eWeLink”, profileId:“C05E”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006”, outClusters:“0000”, application:“05”
Is there any chance you can add the two capabilities I mentioned? or do you suggest I customize the existing version you made for myself? Thank you @Markus for your time and this excellent driver!