OZW Fibaro Problem Topic is solved

For Z-Wave related questions in Domoticz

Moderator: leecollings

Post Reply
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

OZW Fibaro Problem

Post by emme »

Ciao,

I've readded all devices to my new HomeID Zwave network due to a problem that caused me to hardreset the zwave stick

all devices have been resetted and reincluded...

BUT.. I have a strange issue with fibaro FGK10x door sensors and FGMS001 multi sensor

parameters are setted ok... but in the devicetab I can see the device options (sensors, general etc etc), but no burglar devices... none for all these kind of device....
ticked Accept new hardware
I removes the zwcfg_0x123456.xml
soft reset
hail network
refresh node info
...nothing was sucessful and I'm still having no tamper device :(

does anyone knows what I can do or is aware about a change in the description files? (I did not see nothing in the OpeZwave changelog)
ciao
M
The most dangerous phrase in any language is:
"We always done this way"
Gravityz
Posts: 652
Joined: Wednesday 16 December 2015 19:13
Target OS: NAS (Synology & others)
Domoticz version: 2025.1
Location: Netherlands
Contact:

Re: OZW Fibaro Problem

Post by Gravityz »

and if you do astop/start of the zwave stick instead of a soft reset.



setup
hardware
select openzwave USB(in case you have a aeotec gen5 stick)
deselect enabled
update
select enabled
update
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

Re: OZW Fibaro Problem

Post by emme »

no luck :(
it reloads all the command_classes (except this one... but I think is the positioning sensor of the FGMS001)
2017-03-28 11:09:35.987 OpenZWave: Value_Added: Unhandled Label: Angle Position, Unit:
I see that the FGK-10x devs have no group Association and even if I try to add dev.1 (controller) to group 1 (Lifeline) the value is not saved... (group 1 still empty)

I cannot understand if the problem is related to the new .xml file for the fgk10x or something goes wrong with the stick

I'll try to connect it to the laptop and use zensys util and see what's wrong (at least if the burglar feature is still readable) :(
I'm starting believing it's a stick related problem
The most dangerous phrase in any language is:
"We always done this way"
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

Re: OZW Fibaro Problem

Post by emme »

...controller soft reset... new devices added...

these are the FGK-10x

Code: Select all

2017-03-28 11:59:28.797 OpenZWave: New Node added. HomeID: 3550092153, NodeID: 34 (0x22)
2017-03-28 11:59:28.797 OpenZWave: Value_Added: Node: 34 (0x22), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-28 11:59:28.798 OpenZWave: Value_Added: Node: 34 (0x22), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2017-03-28 11:59:28.799 OpenZWave: New Node added. HomeID: 3550092153, NodeID: 35 (0x23)
2017-03-28 11:59:28.799 OpenZWave: Value_Added: Node: 35 (0x23), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-28 11:59:28.800 OpenZWave: Value_Added: Node: 35 (0x23), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2017-03-28 11:59:28.801 OpenZWave: New Node added. HomeID: 3550092153, NodeID: 36 (0x24)
2017-03-28 11:59:28.801 OpenZWave: Value_Added: Node: 36 (0x24), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-28 11:59:28.802 OpenZWave: Value_Added: Node: 36 (0x24), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2017-03-28 11:59:28.803 OpenZWave: New Node added. HomeID: 3550092153, NodeID: 37 (0x25)
2017-03-28 11:59:28.803 OpenZWave: Value_Added: Node: 37 (0x25), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-28 11:59:28.804 OpenZWave: Value_Added: Node: 37 (0x25), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2017-03-28 11:59:28.805 OpenZWave: New Node added. HomeID: 3550092153, NodeID: 38 (0x26)
2017-03-28 11:59:28.805 OpenZWave: Value_Added: Node: 38 (0x26), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-28 11:59:28.806 OpenZWave: Value_Added: Node: 38 (0x26), CommandClass: BATTERY, Label: Battery Level, Instance: 1
no clue of burglar... neither og general access or alarm level :( :(
The most dangerous phrase in any language is:
"We always done this way"
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

Re: OZW Fibaro Problem

Post by emme »

problem looks to be fixed with b7195 (before I was unable to pair secure)

but I had to reinclude all my devices in security mode... otherwise I would not have all classes
The most dangerous phrase in any language is:
"We always done this way"
Gravityz
Posts: 652
Joined: Wednesday 16 December 2015 19:13
Target OS: NAS (Synology & others)
Domoticz version: 2025.1
Location: Netherlands
Contact:

Re: OZW Fibaro Problem

Post by Gravityz »

never knew the fgms001 had an angle sensor
i only have this message with the seismic sensor
emme wrote:no luck :(
it reloads all the command_classes (except this one... but I think is the positioning sensor of the FGMS001)
2017-03-28 11:09:35.987 OpenZWave: Value_Added: Unhandled Label: Angle Position, Unit:
I see that the FGK-10x devs have no group Association and even if I try to add dev.1 (controller) to group 1 (Lifeline) the value is not saved... (group 1 still empty)

I cannot understand if the problem is related to the new .xml file for the fgk10x or something goes wrong with the stick

I'll try to connect it to the laptop and use zensys util and see what's wrong (at least if the burglar feature is still readable) :(
I'm starting believing it's a stick related problem
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest