tnesheim

I have a Fibaro doorsensor (v2.5) where I use both the ordinary input(IN) and the tamper button(TMP) as inputs. The IN is quite simple, I connect to the terminal block. For the TMP I have done some solderwork, and this have worked fine for a very long time. However, at some point(just identified the problem, but do not know for how log it has lasted) the TMP signal seems to be cancelled/reset by the state of the IN. This did not use to happen before, and the two inputs(IN and TMP) independently worked fine. Now they seem to be entangled somehow...in a way that renders the TMP-input not usable (the IN works fine). I have looked at the datasheet https://manuals.fibaro.com/content/m...EN-A-v1.01.pdf and apparently there are two ways the TMP works, throug associations and register settings. But, I'm not sure which "knobs to turn" to restore the old functionality?

And BTW there are difference between VDs and scenes in terms of doing these calls...

I have never needed to use credentials that way, so sorry, I do not know. This is however an example of a functioning POST in a scene and you can hopefully take it from here: local http = net.HTTPClient() http:request(("http://127.0.0.1:11111/api/devices/1037/action/setThermostatSetpoint"), { options = { method = 'POST', headers = { ['Accept'] = 'application/json', ['Content-Type'] = 'application/json' }, data = '{"args":[1,21]}' }, success = function(response) local result = response.data; if response.status == 200 then fibaro:debug(response.status) fibaro:debug(response.data) else fibaro:debug(response.status) fibaro:debug(response.data) end end, error = function(err) fibaro:debug('[ERROR] ' .. err) end })

Hi @SmartHomeEddy I see that you have the MCO MH9, and it works fine. I also see that it measure temperature, RH and VOC. Can these values also be read by the controler(HC3/HC2) through the z-wave?

Hi Looks like you are using the «script» feature of the VD and not the LUA. I have used LUA only. Right now I only have my phone, please remind me in a week or so, then I’m back at my computer, and I’ll send you some examples. In the meantime do some Googleing for «API fibaro lua» etc...this will hopefully give you some examples... If you search for posts created by me in this forum you’ll find some examples for communicating with Homey, but this can be used as a starting point. Please note that there are differenced between VD and scenes both in syntaks and capabilities...

Sorry, that kind of route denotation I have not seen before. My have been simpler, and it was always possible to see/guess the route. I can assume you have several humor in your mesh network. Try to «fix network». In my HC2 I usually do this on the source node, and after a try og two the jumps have usually disappeared.

? guess this thing could have driven me into insanity, so good thing going to the mountains refreshing the mind. Filtering the Zniffer on HomeID makes the radio traffic much more relaced...some lines every now and then, silence for 20s, some messages and so one. I can though see the result of my elimination approach cutting the power breakers...I probably need to do a mesh optimisation for some of the devices since I can see several indirect jumps that was not there before. Anyway, case closed. Thanks for the support!

Back from vinter holidays.... I tried the elimination method...and I had no luck to "silence" the chatty devices. However, I noe remember that my neighbour is also doing home automation(with at Homey). I guess that the main controller always is Node 1....and my Zniffer would not make a difference between my or my neighbours controller? Any way to see the difference on the ACKs or similar?

My device with NodeID 18 is a mystery. To me it seems that there is a burst every 60s consisting of three Meter Reports and 4-5 Multilevel Sensor Reports. Also, my device with NodeID 15 used to be routed through 18. Therefore I think that this device must be a powered device capable of doing routing, and I would guess that no battery powered unit do Meter Reports? So, could this ghost device be a device I can see in my HC2 GUI but(but lists the wrong NodeID) or a invisible device in the HC2 GUI but present in the Z-wave radio database only?

The ghost devices present in the Z-wave radio but not as a device in the HC2 GUI is most likely devices that have failed in the delete og exclude process. I found one Aeon Multisensor(NodeID 15) that I was able to exclude and one of the ghostdevices disappeared. Fibaro Support could however not help me...apparently not possible to do something with the z-wave database. But I also had a feeling that the operator did not quite understand the nature of the issue. I can also se that I have a few other ghost devices as well, though not that chatty. The best would be to get rid of them but since there is no really efficient method but the elimination and/or signal strength search I´m not sure it´s worthwhile.

Hi I've submitted a request to Fibaro Support to see what they can do/suggest... I also remembered I have one Fibaro Multisensor in my z-wave-sparebox that might not be excluded, AND still have a battery! I will try to exclude this device first. If not, I'll do the hunt for the ghost device using zniffers signal strength reading. Anyway, this doing the exercises to quiet down the radio traffic and reduce CPU-loads are highly recommended. I have a noticable improvement on the scene response!. I therefore think my HC2 still should be able to do the job for many years to come.

Hi No, the device is not there:-(

Screen shot from Zniffer:

I tried to set nodeID=18 or 15 and no output. I then tried to insert a nodeID where I know there is a corresponding deviceID and it reported lots of info. So, I therefore think I have some kind of ghost device...it reports, I have a nodeID but no deviceID....

Thanks for your reply! Should I paste this code into a scene? Or do I need to modify first?