Domoticz

Hi.
I'm trying to add FBMS to my Domoticz. No success.
New system RB Pi B plus. And Razzbery 2 z wave.
It was added but not recognized as a Fibaro device.
Similar situation with Wall plug from Fibaro.
What I did wrong?

I've ch checked another z wave device. It is the same..


Node is in all cases is 0x0000
Type the same

Tomek

TomekM512 wrote: ↑Thursday 05 April 2018 19:29 Node is in all cases is 0x0000
Type the same

IDs zeroed usually means inclusion was not done correctly.

I had this problem with some chinese PIRs from Neo-coolcam: I have a z-stick gen5 controller that can be unplugged & used standalone for inclusions, but these devices could not be correctly included this way: Had to keep controller plugged &include from Domoticz, with the device close to controller (was not a problem with a battery powered one that can be unmounted easily, could have been with an AC one already mounted!).

Z-wave inclusions can also be easily messed-up if not done at a few tens of cm from controller and device kept close for a minute or 2, to be sure parameters are setup correctly. If you do not stay close during all this process, you can experience problems like unrecognised device or being misconfigured (leading to device misbehaving or communication problems).

Reason: Inclusions are done with reduced radio power to avoid including devices in the neighborhood and, for secure inclusions, to limit the risk having symmetric crypto key exchanged at this step being intercepted.

After this step, z-wave is quite rock-solid.

Do you think it is possible that Fibaro *.xml files are not updated?
Is there any better way to update them automatically rather than edit them?

During inclusion process I keep devices really close to Rb PI. Or maybe I wait to short. I always abort it after 1 min of waiting. Actually they appears with 0x0000. But removing nodes from network is always with success after few seconds.

Tomek

Interesting... Im also having a problem with one of my Fibaro sensors. Also showing as 0x0000

TomekM512 wrote: ↑Friday 06 April 2018 10:08 Do you think it is possible that Fibaro *.xml files are not updated?
Is there any better way to update them automatically rather than edit them?

Even an unsupported device (no xml) will show it's IDs, because this is these IDs that are used to choose the right xml file for the right device, using manufacturer_specific.xml file that does the link, under config root.

So this is IMO not your problem.

Theses configs are updated when domoticz (and it's open-zwave subsystem) is updated. If you need to add/update support for a device, you can check ozw github. For instance, you can check if there was something modified for your fibaro device here:

https://github.com/OpenZWave/open-zwave ... fig/fibaro

Otherwise, if this is not an inclusion problem, this may be a device problem (inventory data, thus IDs, missing?).

Hi

I've checked everything.
manufacturer_specific.xml - updated

I still have 0x0000 ID. I see following process:


2018-04-09 20:13:30.040 New sensors allowed for 5 minutes...
2018-04-09 20:13:30.042 OpenZWave: Node Include command initiated...
2018-04-09 20:13:44.974 OpenZWave: New Node added. HomeID: 1431655722, NodeID: 9 (0x09)
2018-04-09 20:13:44.977 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2018-04-09 20:13:44.977 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2018-04-09 20:13:44.977 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2018-04-09 20:13:44.978 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0


Any idea?

BTW
Don't you think that zwcfg_0x55555555.xml has strange name? Owner root


Tomek

TomekM512 wrote: ↑Monday 09 April 2018 20:21 I've checked everything.
manufacturer_specific.xml - updated

I still have 0x0000 ID. I see following process:

Hello,

As I told you, even a module with no entry in manufacturer_specific.xml (& linking to a device description xml matching device IDs pair), you should be able to see non-zero IDs because all device identification & driving by open-zave depends on this.

So either you have a problem with your controller, but if you have other devices included & running OK that's unlikely. Or a problem with motion sensor (these IDs are inventory data flashed with the firmware during manufacturing & there may have been something faulty with the device or the manufacturing process).

If nothing works, return the device to seller.

May maybe not say this but get yourself a usb zwave controller else...

admin wrote: ↑Friday 13 April 2018 2:21 May maybe not say this but get yourself a usb zwave controller else...

What does this mean ?

I paid for Razzbery 75$ so i need to stay with this for some time.
Finally solved that, info from manufacturer:
You got one of 5rd generation RaZberry that was powered off during self-test process. We apologize, that happens from time to time too. But hopefully this is easy to solve.

Now i have another problem, disappearing nodes after restart.

Tomek