@christi999 Is the precision you get from the Smart Implant SensorMultilevelGet(sensorType:15, scale:0) always 2?
Sensor @ endpoint 3 has value 20.98 - ep=3 null SensorMultilevelReport(precision:2, scale:0, sensorType:15, sensorValue:[8, 50], size:2, scaledSensorValue:20.98) }
I ask because I'm testing a Fibaro RGBW Controller 2 I wrote to read input voltage but it always seems to return a precision of 1
Does Fibaro send out firmware updates?
From what I have seen, yes. This is not something that can be configured. In the case of the Fibaro RGBW controller 2, the manual even specifies that precision is 1.
The last time I checked, a couple of years ago, Fibaro devices could only be updated through a Fibaro Hub. They would not release the files otherwise.
Thanks, I missed it in the manual 
Oh well, I'll order the Fibaro Smart Implant.
The voltage is 1.39 from multimeter and the RGBW controller 2 just truncates it to 1.3, that's not precise enough for what I need.
When I looked at the implant's reports a few years back, the reported voltage was jumping by .02 or .03 volts between reports, not quite a full 2 decimals but better than 1...
So, 5 months now since adding the weekly auto reboot. No Hub and especially NO Implant issues!
Was even able to replace one of the 5 temperature sensors, reboot the Implant, and it accepted the replacement. Of course it scrambled the sensor mapping, but I'd already setup a remapping rule to assign the values to the correct virtual devices.
@christi999 - Should the child inputs have an option for description text logging? I'm in the Hubitat beta group and I can only see debug logging available whereas for the Hubitat driver there's both description text and debug logging preferences available. Thanks.
That option didn't exist in the hub when I coded the driver. I guess I could add it at some point if it's really needed?
It's fine, it was just an observation. I had a failure of a rule last night and was turning on logging for everything involved to recreate the circumstances and diagnose. I noticed that the option wasn't there, but as I'm on beta I wasn't sure if something in the page layout had affected it.
Okay guys, this shouldn't be that hard. I have specific needs that the IMPLANT looks like it would have solved, but I'm getting NO JOY out of this.
Using Hubitat C7 and smart implant. Hubitat is latest firmware.
There is 1ft between the hubitat and implant.
I've installed the HPM and installed the Christi999 driver set.
Hubitat does not report anything in the logs regarding any device, only that the add device process times out.
I factory reset the implant, and still nothing.
Any idea on how I can get this to work?
Regards,
Marc
I've never had any issue with inclusion on the Smart Implants. I use both this driver by @christi999 and the Hubitat one. The last three I installed a few months back went fine and were included at a distance from the hub. I always skip security when prompted so maybe your timeout is when using S2? The hub matched mine with this driver rather than the Hubitat one.
This nugget is from old devices with probes and I can't remember what I did my my two current ones as it's been a while but....
I know when you put on the probes you had to reset the so the firmware recognized you attached a peripheral before it could be recognized.
I should clarify, I do not get any request for security mode.
I only get the running, timeouts and stops.
sys:12025-01-29 05:10:27.560 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 05:09:27.376 PMinfoZ-Wave Discovery Running
sys:12025-01-29 05:07:10.364 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 05:06:29.480 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 05:05:29.349 PMinfoZ-Wave Discovery Running
sys:12025-01-29 05:04:52.667 PMinfoZ-Wave exclusion stopped
sys:12025-01-29 05:04:25.177 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 05:04:22.722 PMwarnZ-Wave Network responded with Busy message.
sys:12025-01-29 05:04:22.695 PMinfoZ-Wave Exclude Started for 30 Seconds
sys:12025-01-29 05:04:21.149 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 05:03:25.048 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:54:58.226 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:54:40.927 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 04:54:14.465 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:54:04.455 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:53:40.909 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:53:31.029 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:52:50.167 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 04:51:50.037 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:50:37.717 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 04:50:04.705 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:49:37.589 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:49:35.343 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:47:44.307 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 04:46:44.289 PMinfoZ-Wave Discovery Running
sys:12025-01-29 04:32:51.232 PMwarnZ-Wave Inclusion timed out, status:7
sys:12025-01-29 04:32:43.110 PMinfoZ-Wave Discovery Stopped
sys:12025-01-29 04:31:51.013 PMinfoZ-Wave Discovery Running
Could the device have the wrong frequency band or be defective.
Also, since this is more of a Z-wave issue rather than the driver, maybe you would get more insight in another forum section, the "help" section maybe.
As @christi999 says it sounds like a device or inclusion issue rather than a driver problem. If the device is the correct region, try shutting down the hub, then unplugging for 39 secs to reset the Z Wave. You’ll also want to be sure that the failed pairings have left no ghosts in the Z Wave details page as those must be removed if present.
Grrrr, I did not think to check the frequency band the implant uses. Are they all EU band?
It showed up as a generic device... got this in the log when it tried to configure..
java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 0 on line 194 (method updated)
seeming like this stuff is not ready for prime time. May try a few other things, but I really needed the analog input on this in the US frequencies bands.
Any suggestions for that?
Marc
All of mine ar US band and functioning fine.
They're available for different regions. The box or device should be marked.
@christi999
Just a heads up. I'm testing the latest beta and these errors now arrive many a minute.
Something has changed in the build that affects this but I have no idea what.
dev:20342025-01-30 15:04:59.733
error
java.lang.NullPointerException: Cannot invoke method toFloat() on null object on line 443 (method parse)
Out of interest, what are the benefits/downsides of this driver over the default one now?
Ive been wanting to automate disconnecting inputs and outputs, which obviously cant be done in the Hubitat version, but in this version I could add a virtual switch which sets the preference as needed and sends the configure command... Thanks and cant believe I didnt find this until recently!!
Download the Hubitat app
