Fgk 10x door sensor battery level reporting

ok chris…thanks for info
i will get back to you soon with latest binding logs

these are some logs with my current binding:

12:05:59.235 [DEBUG] [.b.z.i.c.ZWaveBatteryConverter:60   ] - NODE 78: Generating poll message for BATTERY endpoint 0
12:05:59.236 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:137  ] - NODE 78: Creating new message for application command BATTERY_GET
12:05:59.237 [DEBUG] [o.b.z.i.protocol.SerialMessage:111  ] - NODE 78: Creating empty message of class = SendData (0x13), type = Request (0x00)
12:05:59.239 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:241  ] - NODE 78: Putting message SendData in wakeup queue.

12:06:46.915 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:06:46.917 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class WAKE_UP (0x84)
12:06:46.918 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:136  ] - NODE 78: Received Wake Up Request
12:06:46.919 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:182  ] - NODE 78: Received WAKE_UP_NOTIFICATION
12:06:46.920 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:411  ] - NODE 78: Is awake with 1 messages in the wake-up queue.
12:06:46.922 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveWakeUpEvent: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveWakeUpCommandClass$ZWaveWakeUpEvent@12dcb1c
12:06:46.926 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:06:46.933 [DEBUG] [WaveController$ZWaveSendThread:1277 ] - NODE 78: Sending REQUEST Message = Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 80 02 , callbackid = 34
12:06:46.952 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39   ] - NODE 78: Sent Data successfully placed on stack.
12:06:47.039 [DEBUG] [b.z.i.p.s.SendDataMessageClass:75   ] - NODE 78: SendData Request. CallBack ID = 34, Status = Transmission complete and ACK received(0)
12:06:47.092 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:06:47.094 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class BATTERY (0x80)
12:06:47.096 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:81   ] - NODE 78: Received Battery Request
12:06:47.098 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:96   ] - NODE 78: Battery report value = 94
12:06:47.100 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveCommandClassValueEvent: org.openhab.binding.zwave.internal.protocol.event.ZWaveCommandClassValueEvent@fdc453
12:06:47.104 [DEBUG] [.z.internal.ZWaveActiveBinding:460  ] - NODE 78: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 94
12:06:47.107 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:06:47.114 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveTransactionCompletedEvent: ZWaveTransactionCompletedEvent [completedMessage=Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 80 02 , callbackid = 34, state=true]
12:06:47.116 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:06:47.117 [DEBUG] [WaveController$ZWaveSendThread:1349 ] - NODE 78: Response processed for callback id 34 after 184ms/5123ms.
12:06:48.116 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:506  ] - NODE 78: No more messages, go back to sleep
12:06:48.118 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:202  ] - NODE 78: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
12:06:48.119 [DEBUG] [o.b.z.i.protocol.SerialMessage:111  ] - NODE 78: Creating empty message of class = SendData (0x13), type = Request (0x00)
12:06:48.126 [DEBUG] [WaveController$ZWaveSendThread:1277 ] - NODE 78: Sending REQUEST Message = Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 84 08 , callbackid = 35
12:06:49.148 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39   ] - NODE 78: Sent Data successfully placed on stack.
12:06:49.193 [DEBUG] [b.z.i.p.s.SendDataMessageClass:75   ] - NODE 78: SendData Request. CallBack ID = 35, Status = Transmission complete and ACK received(0)
12:06:49.198 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveTransactionCompletedEvent: ZWaveTransactionCompletedEvent [completedMessage=Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 84 08 , callbackid = 35, state=true]
12:06:49.201 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:372  ] - NODE 78: Went to sleep
12:06:49.202 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:435  ] - NODE 78: Is sleeping
12:06:49.203 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:06:49.204 [DEBUG] [WaveController$ZWaveSendThread:1349 ] - NODE 78: Response processed for callback id 35 after 1077ms/5123ms.
12:07:59.263 [DEBUG] [.b.z.i.c.ZWaveBatteryConverter:60   ] - NODE 78: Generating poll message for BATTERY endpoint 0
12:07:59.264 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:137  ] - NODE 78: Creating new message for application command BATTERY_GET
12:07:59.266 [DEBUG] [o.b.z.i.protocol.SerialMessage:111  ] - NODE 78: Creating empty message of class = SendData (0x13), type = Request (0x00)
12:07:59.268 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:241  ] - NODE 78: Putting message SendData in wakeup queue.
12:08:47.142 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:08:47.143 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class WAKE_UP (0x84)
12:08:47.144 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:136  ] - NODE 78: Received Wake Up Request
12:08:47.145 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:182  ] - NODE 78: Received WAKE_UP_NOTIFICATION
12:08:47.146 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:411  ] - NODE 78: Is awake with 1 messages in the wake-up queue.
12:08:47.148 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveWakeUpEvent: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveWakeUpCommandClass$ZWaveWakeUpEvent@1a1075b
12:08:47.150 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:08:47.156 [DEBUG] [WaveController$ZWaveSendThread:1277 ] - NODE 78: Sending REQUEST Message = Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 80 02 , callbackid = 44
12:08:47.174 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39   ] - NODE 78: Sent Data successfully placed on stack.
12:08:49.224 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:08:49.226 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class BATTERY (0x80)
12:08:49.227 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:81   ] - NODE 78: Received Battery Request
12:08:49.228 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:96   ] - NODE 78: Battery report value = 94
12:08:49.230 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveCommandClassValueEvent: org.openhab.binding.zwave.internal.protocol.event.ZWaveCommandClassValueEvent@191ce69
12:08:49.233 [DEBUG] [.z.internal.ZWaveActiveBinding:460  ] - NODE 78: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 94
12:08:49.235 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:08:49.253 [DEBUG] [b.z.i.p.s.SendDataMessageClass:75   ] - NODE 78: SendData Request. CallBack ID = 44, Status = Transmission complete and ACK received(0)
12:08:52.158 [ERROR] [WaveController$ZWaveSendThread:1330 ] - NODE 78: Timeout while sending message. Requeueing - 2 attempts left!
12:08:52.159 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:435  ] - NODE 78: Is sleeping
12:08:52.160 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:241  ] - NODE 78: Putting message SendData in wakeup queue.
12:09:59.289 [DEBUG] [.b.z.i.c.ZWaveBatteryConverter:60   ] - NODE 78: Generating poll message for BATTERY endpoint 0
12:09:59.290 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:137  ] - NODE 78: Creating new message for application command BATTERY_GET
12:09:59.292 [DEBUG] [o.b.z.i.protocol.SerialMessage:111  ] - NODE 78: Creating empty message of class = SendData (0x13), type = Request (0x00)
12:09:59.295 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:237  ] - NODE 78: Message already on the wake-up queue. Removing original.
12:09:59.297 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:241  ] - NODE 78: Putting message SendData in wakeup queue.



12:10:44.600 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:10:44.602 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class WAKE_UP (0x84)
12:10:44.603 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:136  ] - NODE 78: Received Wake Up Request
12:10:44.605 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:182  ] - NODE 78: Received WAKE_UP_NOTIFICATION
12:10:44.606 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:411  ] - NODE 78: Is awake with 1 messages in the wake-up queue.
12:10:44.608 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveWakeUpEvent: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveWakeUpCommandClass$ZWaveWakeUpEvent@1705826
12:10:44.611 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:10:44.617 [DEBUG] [WaveController$ZWaveSendThread:1277 ] - NODE 78: Sending REQUEST Message = Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 80 02 , callbackid = 50
12:10:44.635 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39   ] - NODE 78: Sent Data successfully placed on stack.
12:10:44.655 [DEBUG] [b.z.i.p.s.SendDataMessageClass:75   ] - NODE 78: SendData Request. CallBack ID = 50, Status = Transmission complete and ACK received(0)
12:10:44.674 [DEBUG] [ApplicationCommandMessageClass:39   ] - NODE 78: Application Command Request (ALIVE:DONE)
12:10:44.676 [DEBUG] [ApplicationCommandMessageClass:138  ] - NODE 78: Incoming command class BATTERY (0x80)
12:10:44.678 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:81   ] - NODE 78: Received Battery Request
12:10:44.679 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:96   ] - NODE 78: Battery report value = 94
12:10:44.681 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveCommandClassValueEvent: org.openhab.binding.zwave.internal.protocol.event.ZWaveCommandClassValueEvent@8d2da7
12:10:44.684 [DEBUG] [.z.internal.ZWaveActiveBinding:460  ] - NODE 78: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 94
12:10:44.687 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:10:44.698 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveTransactionCompletedEvent: ZWaveTransactionCompletedEvent [completedMessage=Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 80 02 , callbackid = 50, state=true]
12:10:44.701 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:10:44.703 [DEBUG] [WaveController$ZWaveSendThread:1349 ] - NODE 78: Response processed for callback id 50 after 84ms/5123ms.
12:10:45.701 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:506  ] - NODE 78: No more messages, go back to sleep
12:10:45.702 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:202  ] - NODE 78: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
12:10:45.704 [DEBUG] [o.b.z.i.protocol.SerialMessage:111  ] - NODE 78: Creating empty message of class = SendData (0x13), type = Request (0x00)
12:10:45.711 [DEBUG] [WaveController$ZWaveSendThread:1277 ] - NODE 78: Sending REQUEST Message = Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 84 08 , callbackid = 51
12:10:46.730 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39   ] - NODE 78: Sent Data successfully placed on stack.
12:10:46.747 [DEBUG] [b.z.i.p.s.SendDataMessageClass:75   ] - NODE 78: SendData Request. CallBack ID = 51, Status = Transmission complete and ACK received(0)
12:10:46.752 [DEBUG] [b.z.i.protocol.ZWaveController:616  ] - NODE 78: Notifying event listeners: ZWaveTransactionCompletedEvent: ZWaveTransactionCompletedEvent [completedMessage=Message: class = SendData (0x13), type = Request (0x00), payload = 4E 02 84 08 , callbackid = 51, state=true]
12:10:46.756 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:372  ] - NODE 78: Went to sleep
12:10:46.757 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:435  ] - NODE 78: Is sleeping
12:10:46.758 [DEBUG] [b.z.i.protocol.ZWaveController:627  ] - NODE 78: Processing event ourselves
12:10:46.760 [DEBUG] [WaveController$ZWaveSendThread:1349 ] - NODE 78: Response processed for callback id 51 after 1048ms/5123ms.

Please can I ask you to use the latest binding - either 1.8.3, or 1.9.0. Currently I can’t process these logs - sorry. I think you are also filtering the logs to only show lines with NODE 78 - this removes some logging that is needed.

Also, when you post the logs, please format using the </> button so they are presented better (I have edited your posts to do this). Thanks :slight_smile:

My I ask what binding are you talkin about? The zwave? I’d like also to check my fgk battery level .
Thanks.

Yes - the zwave binding is required to communicate with zwave devices ;).

Right, I was thinking maybe there is another special binding for the alarm setup. I have already 6 zwave devices on my network.
So to check the fgk battery status what do I need to do?
One more thing, please tell me, I would like that when my fgk is open to trigger a FGS 223 and the question is can I do this from habmin using group associates or do I need to create a rule that will handl this?
Thank you.

Take a look at the examples - it shows how to configure a battery item.

Yes - you should be able to configure an association in the FGK101 to send a command to the switch to turn it on without OH. However, you might find it’s more convenient to use a rule as it might be more flexible…

Thanks man I’ll giving a try.

I have the same problem waking up the contact to display the battery status.
I have 1.8.3 binding.
In Habmin the contact is grey so it is idle. do i need to manually set the wake up period to 3600?
For a moment i saw the battery status 92% but than disappeared and i excluded the contact and re included in the network but no battery status.

Thanks for the answer.

Battery level reporting worked fine for me in openHAB1 with

Number FGK101_Battery "FGK101 Battery: [%d %%]" { zwave="x:command=BATTERY" }

In theory, the binding should set this for you, but you should check it in HABmin to make sure it was set. If it’s set, then you shouldn’t need to wake up the device - it will wake up automatically periodically and the binding should initialise the device.

The device will show grey each time you restart the binding - even if it was previously green.

Battery status is only updated periodically - it may not happen for a few hours. Note that if you exclude and re-include, then you will have a new node id (I’m not sure why you should need to do this though - if the device works, then I would avoid excluding and re-including it).

Yes, excluding and re including the devices has a different if no. I did this because of the battery status, I thought if I’ll do that the devices will show the battery status :confused:
I saw in habmin the the refresh interval was set like 19356673 or so and I set it manually to 3600. Right now I’ll wai 1hour to see if it’s updating or not.

Update: Checking right now in Habmin the wake up interval it displays again a strange value: 16777215
Why is this?
And another thing will be that some times opening and closing the contact its not updating in OH! if is closed its just staying closed even i open the contact :frowning:

Update 2: every time i restart OH at FGK wake up interval is 16777215

Thanks

Probably the device is not configured properly. What associations do you have? IF the associations are not configured, then the device will not report its state to the controller.

When you change the wakeup, it won’t change on the device unless you first wake the device up. Otherwise it won’t be transferred, and when you restart OH, it will have the same value.

What association are you speaking about? in Habmin there’s no association made. The thing is that the contact reports correctly lets say 3 or 4 consecutive times and 5th time it will not update the state.

How do i wake the device up? pressing 3 times on the hidden button on the back?
Update: pressing 3 times on the back button i managed to wake up the contact and now i see the the battery status too! yeeeeyyyy :slight_smile: but there is something wrong with the physical battery: this morning was 92% and since than now i see 89%! is not too much consumed? the specs says that the battery will keep you for 2 years but if in a few hours i used already 3% this means in less than a month the battery will be dead?
Thanks.

A device has association groups. These groups are used to tell the device to send updates to the controller (or other devices) when something changes. If I rmember correctly, the FGK101 has 3 groups.

This is likely to be a problem then.

Then associations are likely set :confused:. If the updates are not reliable, then possibly the device is at the extremes of its range?

Yes - I forget how it’s done for this device - it should say in the manual, but normally it’s pressing a button 3 times, or for a fixed time…

Battery monitoring is pretty unreliable so I wouldn’t take one day to mean anything - check it over a period of time… The issue is that most battery monitors simply use voltage which is a bad indicator of life - it will change based on temperature for instance. I find the battery on these devices last one to two years… If you are messing around with it a lot, then it might also go down quickly for a while, but once it’s all configured it should be pretty static.

My FGK101 is outside of our house (in the cold German weather) and wakup is set to 21600 (= 6 hours).
It’s working now with the same battery since almost a year …

Hi guys, what up? :slight_smile: I read my comm above and I remembered how much I was struggling to make this contact work correctly …
I come now again with the same contact trouble. I installed a new front door and I had to unmourned the contact. Right now I use openHABian and I’m trying once again to make this tricky thing work with a ds18b20. I see the contact open/close ok but the battery status and the temp there’s no way to se the battery status or the temp value :frowning:
I tried to exclude include reset, everything but no way to make it work. I Think there must be something wrong in the procedure of excluding/ including the device because every time the contact has the same node id! Does anyone know which of the 2 buttons of this contact is the tmp button? The on on the inside or the one inside the case? I tried different procedures and still not working proper!
Appreciate all the help and thanks in advance.

This thread is 3 years old. Please start a new one. Thanks

Why? I think it’s k here, the comm is on topic and there are not so much comments to read … so what’s the point to make a new thread?

Because OH has changed so much in 3 years
The point is there: How to ask a good question / Help Us Help You