Hi @kkossev ,
It seems this error is causing my SONOFF SNZB-06P to be shown as UNKNOWN.
Any ideas why the driver is unable to load profile (v4 mmwave) from JSON?
Hi @user5504 ,
Please click on the 'Load Standard Profiles from GitHub' button first :
Do you see any errors in the live logs?
I believe the driver should automatically load the default JSON file upon initial installation... Do you have Hub security enabled, or is Internet access blocked?
1 Like
Hi, I don't think it is an internet issue.
Driver is able to download the library from GitHub according to the logs.
Try rebooting the hub, will the error go away?
1 Like
Nope, the problem persists after rebooting and clicking "Load Standard Profile from Git Hub".
Not sure if this is relevant, my hub and drivers have not been updated in a long time ~2 years.
Tried using your driver today and failed multiple times despite installing and reinstalling via HPM.
After that I also updated HPM and Hubitat Platform version. Still does not work after reinstalling the driver.
See the screenshot below.
Platform Version
2.4.4.155
Hardware Version
C-7
Sorry mate, I don't have many more ideas at the moment what could be wrong ... I have seen this type of exception "error converting JSON: expecting a ....." to happen immediately after the hub reboot - seems like the HE local file storage system needs time to initialize after the drivers are already loaded and running ... or something similar. So that's why there is a rather complex JSON load->parse retry mechanism that hits after a hub reboot.
I suppose you get the same error when you click on the "Load Standard Profiles From Local Storage" button?
2 Likes
Actually, there is a workaround - use the latest 'hardcoded' version of this driver :
Install this driver version 3.5.2 manually; it supports Sonoff SNZB-06P.
The driver name is 'Tuya Zigbee mmWave Sensor ver 3.5.2', so both the old and new drivers can coexist.
2 Likes
Yes, the same error happens when clicking on "load from local storage"
The workaround works perfect for me. I'll keep you updated if the new driver somehow works again.
Cheers!
1 Like
Suspected bug - The file downloads successfully but then fails to parse. The driver is downloading 115,210 characters just fine, but the JSON parser chokes on a specific character in the file — that version string "v.4.1.3 - WENZHI_MTD285_ZB profile improvements" contains something that breaks the parser.
Successfully downloaded deviceProfilesV4_mmWave.json from GitHub, 115210 characters in 214ms
Could not parse JSON metadata: expecting a ',' or a ']'...
2026-04-21 11:28:00.787 AM
info
Radar1 ? Failed to download standard profiles from GitHub
dev:472026-04-21 11:28:00.714 AM
info
Radar1 ensureProfilesLoaded: failed to load device profiles (loadProfilesFromJSON() failed)
dev:472026-04-21 11:28:00.713 AM
warn
Radar1 startCooldownTimer: starting cooldown timer for 30000 ms to prevent multiple profile loading attempts
dev:472026-04-21 11:28:00.690 AM
warn
Radar1 loadProfilesFromJSON: lastReadFileError = status code: 404, reason phrase: Not Found for deviceProfilesV4_mmWave.json g_OneTimeProfileLoadAttempted=true
dev:472026-04-21 11:28:00.690 AM
warn
Radar1 loadProfilesFromJSON: readFile returned null for deviceProfilesV4_mmWave.json
dev:472026-04-21 11:28:00.688 AM
error
Radar1 Connection Exception: status code: 404, reason phrase: Not Found
dev:472026-04-21 11:28:00.613 AM
debug
Radar1 getProfilesFilename: using STANDARD JSON: deviceProfilesV4_mmWave.json (lastJSONSource=null)
dev:472026-04-21 11:28:00.612 AM
debug
Radar1 ensureProfilesLoaded: loading device profiles...(isEmpty=true, g_profilesLoaded=false)
dev:472026-04-21 11:28:00.572 AM
info
Radar1 updateFromGitHub: ? Could not parse JSON metadata: expecting a ',' or a ']', but got
dev:472026-04-21 11:28:00.568 AM
warn
Radar1 updateFromGitHub: Could not parse JSON metadata: expecting a ',' or a ']', but got
dev:472026-04-21 11:28:00.523 AM
info
Radar1 Successfully downloaded deviceProfilesV4_mmWave.json from GitHub, 115210 characters in 214ms
dev:472026-04-21 11:28:00.520 AM
debug
Radar1 updateFromGitHub: Response status: 200
dev:472026-04-21 11:28:00.309 AM
debug
Radar1 updateFromGitHub: HTTP params: [uri:https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Zigbee%20mmWave%20Sensor/deviceProfilesV4_mmWave.json]
dev:472026-04-21 11:28:00.308 AM
info
Radar1 updateFromGitHub: downloading deviceProfilesV4_mmWave.json from https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Zigbee%20mmWave%20Sensor/deviceProfilesV4_mmWave.json
2 Likes
Hi @sigfreund ,
Thank you for the report!
Yes, there was a bug in the latest standard JSON file (a missing comma). Now it should be fixed - please click on the "Load Standard Profiles From Git Hub" button and let me know if your device is detected and working now.
1 Like
Working great now. Thanks for all your work and support.
2 Likes
Is this the right driver for the device " WenzhiIoT Smart Motion Sensor Zigbee 5.8 GHz Radar MmWave Presence Sensor Movement Body Motion Detection with illuminance Tuya Smart Life Home Assistant"
Yes
2 Likes
Hi @kkossev,
I’ve not been able to see any profiles in preferences of the driver for a while. I tried to load it from github, local storage. I tried to repair the device, reintstal the driver, tried almost everything. Am I missing something somewhere?
These are the logs:
Running device _TZE200_holel4dk
Driver version 4.2.1
Did you check out the first post of this thread? Krassimir posted an update there late last year about the future of this effort.
1 Like
Hi @kejin ,
The logs are showing that the ‘device profiles’ are loaded successfully to your hub local storage…. What do you see if you go to the Preferences tab, ‘Device Profiles’?