Hi! Following this as I would like to see this implemented too. EU Neo Coolcam Plug works fine but impossible to set any configuration parameters.
I get:
No signature of method: static com.hubitat.hub.dao.DeviceDao.getState() is applicable for argument types: (null) values: [null] Possible solutions: getState(long), getData(long), getClass(), getAt(java.lang.String)
I'm not versed in the ways of groovy, but pulling the 1.2.6 from your Github and doing rote "physicaldevice->hubitat" changes gets the the same result. How do I track down where this is getting thrown from? (I see a few fooGet() calls w/o arguments, but they look like just wrapper functions, and commenting them out doesn't change anything...)
Are you sure you're pasting it into the driver section and not the app section?
I've not sure if the handler will work, but it will at least stop those errors...
put the following on line 178:
setDataValue("newModel", "true")
change line 235 to:
return cmds
change line 901 to:
return true
find:
physicalgraph
replace with:
hubitat
find:
state?.newModel ?
replace with:
getDataValue("newModel") == "true" ?
It was easier to just port it than to try and explain how to fix it...
I don't have your model so I can't test it, but it's cleanly ported so it should work...
I might have used the wrong deviceType code so post what's shown in the Data section.
I just realized that the original code had a workaround for an old issue and that workaround breaks things in Hubitat 2.1.7 and above so I just removed it.
Both models should now work with the version I just posted, assuming I specified the correct deviceType.
Also a thank you from me Kevin. Having it all working too....
Recently got 4 Neo Coolcam Power Plugs (labeled Z-Wave Plus) with the purpose to build my Z-Wave mesh. The problem is the Plugs do not work as supposed at all.
In general ON/OFF commands are executed on "random" basis. In majority of the cases when pressing On/Off in Hubitat App nothing happens. In few occasions it works for a minute or so, and then stops.
With may initial attempt I have included all four plugs, but later excluded them and gave the Hubitat one week to rest (well, I was traveling). Last night included only two plugs - one next to Hubitat, and another 10+ meters away in the same room. In the very beginning, 10-15 minutes, it look like it's fine, and then the behavior returned.
During the inclusion plugs are recognized as Device, and later introduced the driver provided by @krlaframboise in post 23. Have executed Z-Wave repair procedure as well. There is label on the box of the plug SKU: ZN139698 - haven't found anything like NAS- ... or whatever.
Before on my Z-Wave network had only one Eurotronic Spirit (Z-Wave Plus) and Coolcam door/window sensor. Both was working great, very responsive and no delays - some time after including the Plugs all stops working - excluding Plugs ... all back to normal.
A direction and any help will be really appreciated.
NEO has been unresponsive so I don't have the new model, but it sounds like the new one has even more issues than the original so you're probably better off returning them...
That being said, reducing the reporting frequency of the plugs might help if you don't have a strong mesh in place.
That's not what I meant, the reason it appeared as device when it was joined was that the new model isn't supported by the built-in driver, but you can still control it and the on/off states update correctly with that driver.
I've seen some complaints on the ST forum about the new model randomly turning on/off on its own and randomly disconnecting which requires them to unplug it and plug it back in.
Both of those issues are hardware related and can't be fixed in the driver, but I don't have the new model so I'm not sure how common those problems really are.
I get the impression that this user's mesh isn't well established and if the other devices are able to connect to the hub directly then routing commands through flaky repeaters that randomly drop offline is much worse than not having those repeaters.
Another issue is that the new model's parameters don't match the built-in settings so the driver might be setting the threshold related parameters to low values which can also have a pretty big impact on a weaker mesh, especially if there are 4 of them doing it.
You can easily check that by enabling debug logging and watching the logs and using the custom driver I posted should solve that issue if they increase those thresholds/intervals.
There are other plugs in the same price range that are reliable which is why I said they're probably better off returning them, but I'll admit that most other plugs are slightly larger and I'm not sure what's available outside of the US.
Just don't replace it with the Dome model that looks the same because unless they've released new firmware within the last couple of years, an electrical tester plugged into it shows open neutral and I've had 2 randomly display a white LED and stop responding until they're unplugged and plugged back in.
1 Like
I don't know where you are in the world, but if you are in the US and want a plug that just works, without costing that much more, the Zooz Zen 15 are excellent plugs that handle up to 15 amps @ 110~120v (instead of just 13 amps for the Neo Coolcam) and work perfectly out of the box with HE.
They're on sale for $32.95 USD right now. They offer power monitoring, and the features are far better than the Neo Coolcam.
1 Like
- Getting Neo Plugs is in fact my first step to built Z-Wave mesh. Currently Z-wave devices connected to Hubitat are only one Eurotronic Spirit TRV and one Neo Door/Window sensor. Plan is to have 10 TRVs (Eurotronic Spirit - just waiting in the box to be installed), and to link Heating System Controller by "bridging" basement with upstairs using Z-Wave repeaters
- Purchased from Aliexpress, and on the web-page is referred NAS-WR01ZE. Thanks pointing to check there.
- Located in Bulgaria and for EU plugs option is Amazon.de - unfortunately Zooz Zen EU version not available there.
UPDATE: Haven't touched the plugs for almost a day, and they just became very responsive for 10-15 minutes or so. after that again become unresponsive. The TRV, I guess it is routed via Neo Plug is responding quickly and no any issues - same with Neo Door/Window sensor.
I just went back through some of the PMs and posts about this issue on the SmartThings forum and a few users were able to get it to stop dropping offline by moving the device closer to the hub.
I recommend moving the plug into the same room as the hub for a few days and if the problem shown in your screenshot doesn't happen again then you'll know it was a range issue.
I start suspecting as well it is range problem. Placed one of the plugs exactly next to Hubitat - less than 50 cm, and it works fine. Another two placed in same room, but 5 to 10 meters away - and thats what you see in the logs.
I am having the impression that something wrong with radio module, and when plugs few meters away simply hardly picking signal.
If one of those plugs will be staying somewhat close to the hub then move it there and perform a z-wave repair.
That might prevent the others from dropping off, but these devices sound really buggy so you're still probably better off replacing them with something more reliable...
Was the issue with Neo Coolcam Power Plug ever resolved.
I just purchased 5 of them because they had a built in device driver for them.
But getting very inconsistent results,
One won't join to HE at all (easily with other non HE Hub)
Three are reporting energy consumption nicely but the On/OFF control does not work unless the Generic Zwave Smart Plug driver is used, in which case they work great with on/off but no energy reporting 
And One that does everything using the Neo Coolcam Power Plug Driver.
