search

openhab / org.openhab.binding.zwave

openHAB binding for Z-Wave
Eclipse Public License 2.0
171 stars 202 forks source link

[snapshot] Can't change to customer function: binary report #17

Closed thopiekar closed 8 years ago

thopiekar commented 8 years ago

When trying to change my DCH-Z510's operation mode to "binary report", I get a "HTTP Error -1" popping up and nothing changes. It doesn't matter which UI (Paper UI and HABmin2) I use. I readded (excluded, resetted the DCH-Z510 and included it again), without any changes.

2016-08-08 09:48:52.402 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Timeout while sending message. Requeueing - 1 attempts left!
2016-08-08 09:48:52.403 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 17: Got an error while sending data. Resending message.
2016-08-08 09:48:52.414 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_ack changed from 167 to 168
2016-08-08 09:48:52.424 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_sof changed from 333 to 334
2016-08-08 09:48:52.439 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_sof changed from 334 to 335
2016-08-08 09:48:54.648 [INFO ] [marthome.event.ItemStateChangedEvent] - ipp_printer_Drucker_Airprint__waitingJobs changed from NULL to 0
2016-08-08 09:48:57.406 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Timeout while sending message. Requeueing - 0 attempts left!
2016-08-08 09:48:57.407 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 17: Got an error while sending data. Resending message.
2016-08-08 09:48:57.418 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_ack changed from 168 to 169
2016-08-08 09:48:57.438 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_sof changed from 335 to 336
2016-08-08 09:48:57.449 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_8d1481bf_serial_sof changed from 336 to 337
2016-08-08 09:49:02.411 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=17, callback=122, payload=11 02 25 02
thopiekar commented 8 years ago

Ok, no problem. Will move the logs into a separate directory in the /logs. Have to turn on OH2 soon to turn down my roller shutter. Will call the directory simply "zwave" I think.

In the mean time, good luck on your other tasks 😉

cdjackson commented 8 years ago

What devices are node 17 and 18. It looks like a database problem for them.

thopiekar commented 8 years ago

Z-Wave Node 18: FGRM222 Roller Shutter and Z-Wave Node 17: DCH-Z510 Siren

thopiekar commented 8 years ago

By the way, node 17 is the device, whose parameter 7 I want to change to: sensor binary report.

cdjackson commented 8 years ago

I can guess that the siren might not support GET requests on the switch class - that might be the problem there. However the FGRM looks like it should respond to the parameter request.

For the siren, can you open the XML file (node17.xml) and change the following -:

  <commandClass>SWITCH_BINARY</commandClass>
  <binarySwitchCommandClass>
    <version>1</version>
    <instances>1</instances>
    <versionSupported>1</versionSupported>
    <isGetSupported>false</isGetSupported>
  </binarySwitchCommandClass>
</entry>

note that the needs to be changed to false.

The other interesting this, which might explain your initial problem of not being able to set the config is that the device apparently doesn’t report that it supports the configuration command class. Let’s look at that next!

For the FGRM, you have a newer version than is in the database, and it possibly has different parameters. Can you have a scout around the internet and see if you can find a manual for version 25.25.

Cheers Chris

thopiekar commented 8 years ago

Couldn't find any manual for firmware 25.25. Only (updated?) manuals mentioning 25.25 for other devices by Fibaro, like RGBW controller.

Looks like I have to mail Fibaro for this...

For the siren I changed the file, removed all logs and restarted OH2, retried, shut OH2 down after 5min and moved the logs to zwave_2.

cdjackson commented 8 years ago

I think it might be this -:

http://manuals.fibaro.com/content/manuals/en/FGR-222/FGR-222-EN-A-v1.00.pdf http://manuals.fibaro.com/content/manuals/en/FGR-222/FGR-222-EN-A-v1.00.pdf

This is listed as version 2.5, but I’ve seen in another Fibaro device (I forget which - the flood sensor I think) that they had version 2.2, but the version returned from the device was version 22.22. I wonder if this is some new ploy by Fibaro (no idea why).

Anyway… This manual doesn’t have a parameter 1, so if this is the device you have (it’s the most recent on the Fibaro website) then that would explain your problem…

On 5 Sep 2016, at 22:41, Thomas Karl Pietrowski notifications@github.com wrote:

Couldn't find any manual for firmware 25.25. Only (updated?) manuals mentioning 25.25 for other devices by Fibaro, like RGBW controller.

http://manuals.zwaveeurope.com/make.php?lang=en&type=&sku=FIB_FGRM-222 http://manuals.zwaveeurope.com/make.php?lang=en&type=&sku=FIB_FGRM-222 Looks like I have to mail Fibaro for this... For the siren I changed the file, removed all logs and restarted OH2, retried, shut OH2 down after 5min and moved the logs to zwave_2.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openhab/org.openhab.binding.zwave/issues/17#issuecomment-244814142, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_kQ5PevFByIUrbZ9RGt-8h_Fz6KS1wks5qnIyZgaJpZM4Je4aV.

cdjackson commented 8 years ago

I’ve created a new device in the database and copied this from the old version.

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/413#parameters http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/413#parameters

Can you please take a look through this and compare it to the manual for this version to see what needs to be added and deleted. If it needs to add any parameters, then it would be great if you can add them (if you have an account - if not, please create one and I’ll give you edit access). Anything that needs to be deleted will need to be done by me, so just let me know what parameters, if any, need to be deleted.

thopiekar commented 8 years ago

No need to add/remove any parameter here, but I had to correct ranges. Not only for the bools (0...1), but for other parameters. Reviewed all the parameters and compared with the manual. Hope everything is fine now :wink:

thopiekar commented 8 years ago

Hey Chris,

I excluded the siren, made a factory reset and reincluded it to my network. Still can't change any parameter, but I can turn on the siren, but not off. So I tried to apply what you've mentioned at https://github.com/openhab/org.openhab.binding.zwave/issues/17#issuecomment-244811522 but there is no SWITCH_BINARY anymore.

cdjackson commented 8 years ago

You mean swithc_binary is not in the XML file?

Can you provide a log showing you changing a parameter then waking up the device so that the exchange happens.

thopiekar commented 8 years ago

Of course. The log only says:

17.09.16 12:41          2016-09-17 10:41:35.154 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'zwave_device_f9088262_node25_switch_binary' to handler for channel 'zwave:device:f9088262:node25:switch_binary', because no handler is assigned. Maybe the binding is not installed or not propertly initialized.
17.09.16 12:41          2016-09-17 10:41:37.180 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'ON' for item 'zwave_device_f9088262_node25_switch_binary' to handler for channel 'zwave:device:f9088262:node25:switch_binary', because no handler is assigned. Maybe the binding is not installed or not propertly initialized.
17.09.16 12:41          2016-09-17 10:41:37.186 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'zwave_device_f9088262_node25_switch_binary' to handler for channel 'zwave:device:f9088262:node25:switch_binary', because no handler is assigned. Maybe the binding is not installed or not propertly initialized.
17.09.16 12:41          2016-09-17 10:41:39.161 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'OFF' for item 'zwave_device_f9088262_node25_switch_binary' to handler for channel 'zwave:device:f9088262:node25:switch_binary', because no handler is assigned. Maybe the binding is not installed or not propertly initialized.
17.09.16 12:41          2016-09-17 10:41:39.168 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'zwave_device_f9088262_node25_switch_binary' to handler for channel 'zwave:device:f9088262:node25:switch_binary', because no handler is assigned. Maybe the binding is not installed or not propertly initialized.

but I'll make a update to my snapshot and reset DEBUG on the zwave binding.

cdjackson commented 8 years ago

Not sure why that is! Maybe there’s an exception during startup or something - or maybe there’s some old configuration and this channel is no longer correctly specified?

thopiekar commented 8 years ago

Do you think it is worth to begin a new setup from the latest beta? :confused:

cdjackson commented 8 years ago

It shouldn’t be needed, but on the other hand, it would ensure that we know exactly what condition everything is in so yes, maybe its a good idea.

thopiekar commented 8 years ago

Guess what.. It works.. Simply everything, but turning off the siren.. (changing the parameters works at least)

And the log also looks promising:

2016-09-17 13:06:04.393 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 25: Node configuration report, parameter = 7, value = 0, size = 1
2016-09-17 13:06:04.408 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
2016-09-17 13:06:04.410 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@11014bc
2016-09-17 13:06:04.413 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Update CONFIGURATION 7/1 to 0
2016-09-17 13:06:04.421 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Config about to update 4 parameters...
2016-09-17 13:06:04.424 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_31_1
2016-09-17 13:06:04.426 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_31_1 len=3
2016-09-17 13:06:04.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_31_1 - id = '31'
2016-09-17 13:06:04.445 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_29_1
2016-09-17 13:06:04.453 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_29_1 len=3
2016-09-17 13:06:04.454 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_29_1 - id = '29'
2016-09-17 13:06:04.458 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010
2016-09-17 13:06:04.464 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010 len=4
2016-09-17 13:06:04.465 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010 - id = '7'
2016-09-17 13:06:04.467 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010 - size = '1'
2016-09-17 13:06:04.470 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010 - bitmask = '00000010'
2016-09-17 13:06:04.471 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing config_7_1_00000010 - dec = '16'
2016-09-17 13:06:04.474 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Sub-parameter config_7_1_00000010 is 00000000
2016-09-17 13:06:04.477 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Pre-processing  00000000>>00000010
2016-09-17 13:06:04.481 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Post-processing 00000000>>00000010
2016-09-17 13:06:04.486 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Sub-parameter setting config_7_1_00000010 is 00000000 [0]
2016-09-17 13:06:04.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Processing binding_pollperiod
2016-09-17 13:06:04.508 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - UPDATE_DATABASE: Transaction complete (SendData:Request) success(true)
2016-09-17 13:06:04.527 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - checking initialisation queue. Queue size 0.
2016-09-17 13:06:04.536 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2016-09-17 13:06:04.540 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-09-17 13:06:04.544 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 25: Response processed after 356ms/4716ms.
2016-09-17 13:06:18.489 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Configuration update received
2016-09-17 13:06:18.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Configuration update group_1 to [node_1_0]
2016-09-17 13:06:20.802 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 25: Transaction not completed: node address inconsistent.  lastSent=25, incoming=255
2016-09-17 13:06:51.132 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 25: Transaction not completed: node address inconsistent.  lastSent=25, incoming=255
2016-09-17 13:06:51.557 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 25: Transaction not completed: node address inconsistent.  lastSent=25, incoming=255
2016-09-17 13:08:39.087 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Command received zwave:device:a831d790:node25:switch_binary --> ON
2016-09-17 13:08:39.088 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 25: Creating new message for application command SWITCH_BINARY_SET
2016-09-17 13:08:39.098 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 25: Sending REQUEST Message = 01 0A 00 13 19 03 25 01 FF 25 43 41 
2016-09-17 13:08:39.117 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Sent Data successfully placed on stack.
2016-09-17 13:08:39.186 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: SendData Request. CallBack ID = 67, Status = Transmission complete and ACK received(0)
2016-09-17 13:08:39.190 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - UPDATE_DATABASE: Transaction complete (SendData:Request) success(true)
2016-09-17 13:08:39.209 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - checking initialisation queue. Queue size 0.
2016-09-17 13:08:39.220 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2016-09-17 13:08:39.228 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-09-17 13:08:39.231 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 25: Response processed after 127ms/4716ms.
2016-09-17 13:08:39.886 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Command received zwave:device:a831d790:node25:switch_binary --> OFF
2016-09-17 13:08:39.887 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 25: Creating new message for application command SWITCH_BINARY_SET
2016-09-17 13:08:39.921 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 25: Sending REQUEST Message = 01 0A 00 13 19 03 25 01 00 25 44 B9 
2016-09-17 13:08:39.941 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Sent Data successfully placed on stack.
2016-09-17 13:08:39.998 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: SendData Request. CallBack ID = 68, Status = Transmission complete and ACK received(0)
2016-09-17 13:08:40.020 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - UPDATE_DATABASE: Transaction complete (SendData:Request) success(true)
2016-09-17 13:08:40.021 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - checking initialisation queue. Queue size 0.
2016-09-17 13:08:40.022 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2016-09-17 13:08:40.025 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-09-17 13:08:40.030 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 25: Response processed after 105ms/4716ms.
2016-09-17 13:09:10.351 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 25: Transaction not completed: node address inconsistent.  lastSent=25, incoming=255
2016-09-17 13:09:10.813 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 25: Transaction not completed: node address inconsistent.  lastSent=25, incoming=255

The only interesting thing is that node25.xml is missing.

cdjackson commented 8 years ago

I would guess that the siren might not allow the OFF command unless security is enabled - but that’s a guess.

If you can get a full log from startup I’ll take a look at why the XML isn’t being generated.

At least we’re getting somewhere ;)

thopiekar commented 8 years ago

Here they are. Unplugged the speaker of the siren and while it is blinking I see on HABmin: "Node is not communicating with controller" in the list of things.

no_zwave_node25_logs.zip

thopiekar commented 8 years ago

Restarted OH2 and since a while it stays at: "Node initialising: UPDATE_DATABASE"

thopiekar commented 8 years ago

no_zwave_node25_logs_1.zip

cdjackson commented 8 years ago

Yep - also see that in the log. Not sure why but I’ll take a look as this stage shouldn’t get stuck for any significant time.

thopiekar commented 8 years ago

Btw. the siren is still blinking.

cdjackson commented 8 years ago

I don’t know what it means if the siren blinks.

There’s an exception in the update_database stage, so I’ll try and fix that now.

thopiekar commented 8 years ago

Ok, thanks :+1:

I'll need to update to the snapshot tomorrow, isn't it?

cdjackson commented 8 years ago

I’ll create the fix now (I’ve found the bug) and will regenerate the binding - probably ready to go in about an hour if you update then.

thopiekar commented 8 years ago

Ok, great! No need to update to a snapshot?

cdjackson commented 8 years ago

Ref PR #108

cdjackson commented 8 years ago

Yes - you’ll need the latest snapshot, but as the nightly builds don’t work I need to trigger them manually which I’ll do as soon as the tests have run and the PR is merged. Once it’s then built, you should be able to use the snapshot (I think!)

On 17 Sep 2016, at 15:01, Thomas Karl Pietrowski notifications@github.com wrote:

Ok, great! No need to update to a snapshot?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openhab/org.openhab.binding.zwave/issues/17#issuecomment-247772952, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_kQwTq4JtTTpBXHBB3EeVvb1MyG3P8ks5qq_K_gaJpZM4Je4aV.

thopiekar commented 8 years ago

:ok_hand:

cdjackson commented 8 years ago

Ok - this has finally built (after a test failure in another binding!).

thopiekar commented 8 years ago

It works! :heart_eyes:

cdjackson commented 8 years ago

:)

Great stuff.