Tell me this, why are you so right and I am so wrong
Removed the resistor (was there before on the old panel) and it works, now just have to get the open to be closed and the closed to be open.
Tell me this, why are you so right and I am so wrong
Removed the resistor (was there before on the old panel) and it works, now just have to get the open to be closed and the closed to be open.
I went through your problems myself... As for the open/closed, it is reversed, my fault... it can be changed in the input configuration.
Bingo....
Should this be set to force refreshes? or really where should this be used? Again thanks!
" Analog inputs - periodical reports:"
Great. There is no need for "periodical reports", Alarm inputs work on their own.
I use one of my analog inputs to measure the voltage of an existing temperature sensor inside an HRV (with an op-amp as buffer, the implant input impedance is not very high...). I could use periodical reports to get it updated, I use polling instead.
Thanks, again keep up the good work, wouldn't be the same here without people like you.
Thanks for the updated driver @christi999 works a treat.
On a separate note, you dont happen to know if there is a trick to getting the external temp sensors (DS18B20) to show a value. When I configure the device, it reads back the internal temp fine, but never gets the external sensor. The external sensor should show up as end point 8 on device 7.
When I do a manual refresh, is see the following output in the log " 2020-06-05 18:49:49.484 [debug] {childRefresh, ep=8}" But i dont seem to get a response.
The inputs seem to configured. I think I am missing something obvious, but cant see it.
Any ideas?
I don't have any, other people said it was working fine... Did you follow the procedure in the documentation (not sure it makes a difference but that's a starting point)?
Yep, all connected and checked.
The sensor is getting power 3.3v, gound and the Signal line.
Implant is working nicely on the network for all the other functions... I will keep trying. Thanks though.
Yea, the number of external sensors is only used to create the right number of child devices. There is no configuration sent to the implant for the external temp sensors except for the periodical reports or the minimum change reports. So the implant should automatically be configured for the external sensors when they are present.
My only interrogation had to do with the proper sequence to follow so they work with the implant, does it matter that the sensor are connected before powering-up? Connected before joining the network?
Also set the periodical reports, if you don't see them in the log there is something wrong on the implant/sensor side.
Probably will not work... maybe put the maximum number of external sensors in the preferences and try to refresh all of them...
I think when I set it up I connected the external sensor before first adding into Hubitat, but also remember adding the external (1) just cause it said external sensor
That seemed to work... so had to reset the device to factory defaults, exclude it, then wire it all up and connect it all, then add it back to the network. and then it worked... Good tip.
Thanks
I updated my hub after seeing your post and got the same result. Version 1.6 is out. I did this quickly but hope it solves all problem. I will check more tomorrow.
Installed 1.6 and my smart implant now works perfectly, thank-you !
Very nice work by the way, your driver works very well
1.6 did the trick!
Thanks for the quick response.
What changed, just curious?
The signature for the zwave "Multi Channel" class changed from V3 to V4. The implant documentation says that you should be using V4, I don't know why it was coded as V3 in the first place (seed design by "boblehest"). Maybe hubitat didn't support it then and was mapping V4 to V3 and in the last update they implemented V4?
Again great job!
Keep up the good work.
I just kept putting it off until now... Please continue the discussion about the driver in this new developers forum thread (the proper place for it):
https://community.hubitat.com/t/release-fibaro-smart-implant-fgbs-222/42983
Thanks
Chris
Thanks muchu999, your update to the main driver fixed my issue with getting the Smart Implant inputs