I would bet support would not be ignoring you, it probably comes down to priorities. Hubitat is not a big company and yet they have been getting a lot of improvements out there.
@bobbyD might be able to know better who the ZigBee expert is within Hubitat. It would probably be best if the Expressif engineer could be put directly into contact with someone so they can determine where the real difficulty is happening. Especially if you can provide him with the contact information (maybe you can create an introduction email between you all when the time comes, for level setting as well).
Thought I would give this a try on a C7.
Set the"esp_zb_secur_link_key_exchange_required_set(false);". Did full flash erase, build compile flash.
Hub sees the device quicker and once out of approx 15 pairings it worked. Once it did it worked with device rebooted hub rebooted etc.
Made no changes, unpaired. Reboot device reboot hub and will not pair at all.
Not the most scientific way to do it but does seem to point to something other than lack of version 3 support.
Surely if that were the case it would never pair as they would be speaking different dialects?
@marktheknife
1-
I have a defective hub which the support promissed to replace.
I have a long conversation of PMs. They just started ignoring me after Jun 2024.
I gave up.
2-
I have many threads asking for help here. None of them was answered seriously by any Hubitat official. All I get is answers from "ambassador" titled people like you.
I have a different approach to problems. I like being direct. And that is not welcome here by the staff and ambassadors. They (you) don't approve any negative comments about the staff/product of Hubitat.
Maybe my way is not the best, but I don't like losing time.
Anyway, I learned living with that and I am not expecting help from staff.
I am just trying to be helpful to the community.
I got my solution. Just passing the info from Espressif staff...
You appear to be putting words in my mouth. And I disagree with your characterization of what I’ve said to you in the past. Perhaps you were referring to other ambassadors. Doesn’t really matter. You have your opinion and I have mine.
Interesting. I am not using the Arduino tools but rather the native dev environment.
Far as I can tell everything is up to date correctly configured, builds burns etc fine no error messages.
Then when you try and connect it fails miserably.
Guessing there must be some fundamental difference somewhere!
have you read what I wrote above on post 100
quoting:
I am working on this subject with an engineer from Espressif named Jan Procházka
After taking captures from the Zigbee network , he suggested disabling key exchange on the Zigbee library using the code:
"esp_zb_secur_link_key_exchange_required_set(false);"
with that workaround , the problem is solved and now I can use the esp32-c6 module with my Hubitat C8 hub and it is stable.
@snell
as you see, you have added @bobbyD on your post to take their attention but no response from them.
Now I have other feedback to share but I can't get a response from Hubitat developers/support.
Anyway, let me write the current situation with esp32 zigbee support on Arduino:
Basic examples below are working fine on Hubitat with generic devices
On/Off light
Dimmable light
Temperature sensor
RGB light does not work (color part), because on Arduino side only RGB setting is developed and on Hubitat side the drivers are only supporting HSL. Either HSL should be developed on Arduino, or we should find a RGB driver on Hubitat
There is an "Occupancy Sensor" template along Arduino examples which is known to be working with Home Assistant. However, it did not work with generic "motion sensor" drivers on Hubitat. I am not sure if an occupancy sensor is equivalent to a motion sensor. So I need some guidance here. Which driver should I test it with ? And is there a troubleshooting method for that ? (Maybe @kkossev could help...)
On Arduino side , there is no combined temperature & motion sensor endpoint. So if we have 2 sensors connected to an esp32, (or a single sensor with both capabilities) we have to add 2 endpoints to the sketch's Zigbee core. But when I do that, while pairing only the first endpoint is defined on Hubitat. How should we add both capabilities to the esp32 device in that case ?
As you see, I am trying to get esp32 zigbee working with Hubitat. But I have no ways to get in touch with Hubitat developers/support other than this community forum.
I'd appreciate any help.
For the RGB light, Hubitat does have an HSV to RGB conversion here is a thread referencing it. I have not used it myself. You could always look at altering an existing ZigBee driver to add RGB support. Their ZigBee RGBW bulb code is here (already mentioned above it turns out).
@kkossev might know about the later two points. Hubitat also has sample code for an environment sensor but it does not include motion. I have had temperature and motion sensors in the past (most of my old ZigBee motion sensors also provided temperature). It sounds more and more like you might want to create a custom Hubitat driver as well.
I don't understand how that RGB->HSV conversion and/or the "ZigBee RGBW bulb code " will help me.
When I look at the code I see a setcolor() function but I don't see when it is called.
So I can't guess which part of the code is setting the color on the endpoint device.
Besides, in the code there are commands like: "he cmd 0x${device.deviceNetworkId} 0x${device.endpointId} 0x0300 0x06 {${hexHue} ${hexSat} ${intTo16bitUnsignedHex(rate / 100)}}","delay 200",
But I don't see an example of setting R,G,B values on Endpoint device.
How can I find the correct command to use with RGB values if I can calculate them from HSV ?
I thought you were looking for a method to convert what Hubitat understands to the Arduino code for RGB, so I tried to provide some references.
The setColor() function would be called as a command. The ZigBee RGBW bulb code example shows that the device has the ColorControl capability (and others) and that capability will provide the commands setColor, setHue, and setSaturation.
The ZigBee standard for color control (cluster 0x0300) only allows for HSV (HSL and HSV - Wikipedia) and does not natively handle RGB. So the values must be converted. If they are offering RGB in the Arduino code (it is the one most people are familiar with), they must be converting it to match the ZigBee standard for sending/receiving.
