I was tired of relying on the Home assistant to control my Fenetex motorized screens (433mhz motors). They came with a DD7006 P-Box that allows app/and local control through the motion blinds integration on Home Assistant as well as google home and Alexa but nothing else. The MFG sent the API info with the blessing to build an app or Driver, so that's what I did (with lots of help from AI, as I'm not a developer)
If anyone can use this feel free, If you have any issues I can try to help. If you find any issues or better way to do anything I'm open to making changes if anyone has any suggestions or requests I will do my best to make them happen.
Thank you Jcongdon01 for testing with DD7002B Hub confirmed working
Uni-directional motor note
If your motors are Uni-Directional you will be unable to get position data from your blinds as your motor(s) don't send that information back to the hub, this is a limitation with the motor(s). Open and Closed commands work but I am unsure if set location/position commands work accurately (my theory is they will as long as you only use Hubitat to move them, but if you use a remote or the app to move them Hubitat will have no way of knowing where they are and will loose track of them.
v30.1 is up on Github, posted 04-10-2026 after some testing
Thank you for putting this together as I have the exact same setup. I was able to work through all the install steps and from what I can see have no issues with the key, was able to retrieve the two children however when I try to close them I get no response. I do see the close commands in the log file.
I do see a warning for a truncated access code being sent but no errors in the controller.
In each child I do see an error MissingMethodExceptionNoStack: No signature of method: user_driver_connector_Screen_Child_828.startPositionChange() is applicable for argument types: (java.lang.String) values:[close] (method startPositionChange)
@jcongdon01 I didn't implement startPositionChange (It's built into the Hubitat Windowshade's capability so I don't know how to remove it wasn't high on my list as the open and closed button did everything I needed. If you can get me some logs from the parent device I can try to see what's going on and why your not getting any movement my guess is it chould be a networking (Hubitat pulls the devices using one Http, but commands are sent through multicast so there could be something going on where the multicast is being blocked.
The Truncated access code is if you don't include the "-"'s mine is setup as 8digits-4digits-2digits ex 12345678-1234-12 if you are leaving out the "-"'s the connector relay won't accept commands without the correct access code to create the correct token
It looks like it's receiving the multicast info from the connector hub. can you verify the model of the hub (is it the DD7006 P-Box) If it is what is the branding i'll try to lookup and see If I can find the specs maybe Different Branded uses different firmware/commands)
@jcongdon01 from what I can tell both hubs should use the same ports and commands. I had the AI tailer it a little more to detect the hub version. Found a couple errors try the updated code posted below
@jcongdon01 I may have found the issue, it apears from what I have been able to find online the 7002B requires the full Token and the new 7006 uses only the first 16 Bytes
While we test this one make sure you change the offline detection to 0 we don't need the logs filling up with warnings (and honestly I'm not satisfied with how it works right now so disabling is probably the best for now anyways)
Thank you for those logs, sorry it's taking so long it's a slow process when I don't have the device to test. It looks like the other driver was truncating the token to 32 characters and the 70002B is expecting the entire 64 characters, this version should correct that
Hmm on the preferences try changing hub detection from auto to 7002b I'm not sure why it's truncating the token it should be sending the whole thing. I'll take a look at the code in the morning and see what I can figure out
Sorry for the confusion I got ahead of myself. I am trying to make it so we can use 1 driver for both Hub versions (mine DD7006 requires the truncated token, and yours DD7002B requires the full token) I'm working on a new version for you to try.
I'll upload trial v5 in the morning I did some basic tests here with the my dd7006 and the switch between the 2 boxes seems to work now so we can use this 1 driver for either
Trial v5 is up on github, select your Hub type in the preferences (I don't think Auto-detect works I think it defaults to the DD7706, but If you select DD7702B I hope this one works
The logs are looking a lot better. I configured as a 7002b and turned off the 2 minute offline warning. l am stil unable to control the children as they are reporting an access token error?
