If you read the error message (first line in the screenshot), you'll see you tried to paste the camera driver code into a new app window, not into a new driver window.
I strongly suggest install Hubitat Package Manager, and then use that to install this (and any other app/driver). It avoids this type of error and makes adding/updating custom code much trivial as clicking 'install'.
That's correct, I attempted to import using the App. It has New App on the upper left on my previous screen shot. I installed the Hubitat package manager and reboot my hub. I am getting the same error on line 73.
I am getting this Wyze error when I try to access the Wyze Hub in Apps.
--- Error: A device with the same device network ID exists, Please use a different DNI
I checked the error log and the following is shown.
---app:132
2022-10-21 08:55:42.162 AM
error
java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI on line 735 (method pageMenu)
Thanks for the Code I have been looking for something just like this for my Wyze Cams - One issue is anyone getting this error when I click on the wYZe Hub - in Hubitat any ideas?
" Unexpected Error - " error: Device Type "WyzeHub Camera" in name space "jakelehner" not found
It looks like you are missing the code for the "WyzeHub Camera" driver. You need to add all the drivers included in the package for the devices you have.
I'm guessing you installed this manually; if so, you need to also install all the drivers in the drivers folder on Github (using the "Drivers Code" on Hubitat).
However, I strongly suggest you use [RELEASE] Hubitat Package Manager (HPM) -- HubitatCommunity (HPM) to install this (and most other custom apps/drivers). It makes it far easier to install things and avoid mistakes. AND it has the benefit of helping you keep things up to date.
@jakelehner hasn't been around for a few months, and there are 3 pull requests waiting on github (one of them mine). I hope by tagging him that he responds.
Hi all. Apologies for the lack of response. I haven’t really been using my Wyze stuff on account of having so many problems keeping the connection alive. Glad to see the conversation continue in my absence.
Half the time I can’t even log in to the mobile app without resetting my home IP or getting on VPN.
I’m not even using the integration at this point, and others on here don’t seem to have that problem. So I’m guessing it has something to do with having so many devices hitting their servers it trips their rate limit. Pretty silly to punish customers for owning a lot of your product.
I digress … at this point I am more than happy to give over ownership of the repo, or at minimum add some contributors so other folks are able to approve PRs. @fieldsjm any feedback on the matter?
Transferring ownership would require some effort to update package manager and maybe reconsider the folder structure. So maybe just start with contributors for now?
Sorry to hear the frustration. I only have cameras so I don't mind continuing to support that piece as a contributor and happy to help anyone debug when I can. Just not sure how much I can help develop/debug without additional devices on hand.
FWIW, my system is fairly stable but again I'm only refreshing 8 cameras periodically with limited commands so you are probably using a lot more bandwidth. For me, the issue isn't necessarily connection but random unscheduling of refresh so I created some rules to send periodic refreshes outside the integration.
How many devices do you have? I have three v3 cams and the floodlight, and while I've read some other threads (from Apr 2021) about their rate limit, I've not apparently hit it.
Follow-up: Since IFTTT has been fairly inconsistent, I have come up with a solution that has worked flawlessly for about a month now. I bought an inexpensive Wyze Outdoor Plug and set it up normally. I then added it to Hubitat via the WyzeHub integration. I can then assign trigger rules inside of the Wyze app to turn the Wyze Floodlight light on and off accordingly. At $10 on sale the outdoor plug was the cheapest solution to my problem and the dual plugs allow me to control both of my outdoor floodlight lights. A very stable work-around.
I believe the BR30 bulbs are brand new and I picked some up on black friday. The current drivers appear to work 80%. The feature I think that is NOT working is dimming. I can set the level to 100, but I cannot dim it at all from hubitat. I can dim it from alexa, as I am using the skill for that outside of hubitat, so it is possible - just curious if you were aware (@jakelehner) and what the problem might be? Logs say this when rule is fired off to set the color to warm white and dim to 3%:
org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'null' with class 'null' to class 'float'. Try 'java.lang.Float' instead on line 436 (method setColor)
groovy.lang.MissingMethodException: No signature of method: java.lang.Integer.min() is applicable for argument types: (java.lang.Integer) values: [100] Possible solutions: min(int, int), find(), max(int, int), is(java.lang.Object), minus(java.lang.Character), div(java.lang.Number) on line 160 (method setLevel)