MiOS Binding reporting problem during backup

Plugins & Plugin Development openHAB MiOS Binding
#1

Howdy,

Just noticed this in my openhab.log last night:

2015-02-03 03:00:01.105 [WARN ] [t.i.s.MapTransformationService] - Could not find a mapping for '5' in the file 'miosZWaveStatusIn.map'.

Here’s corresponding entries in mios.log (trace mode) of that same time:

2015-02-03 03:00:01.104 [DEBUG] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: BOUND {mios="unit:nightmare,system:/TimeStamp"}, value=2015-02-03T03:00:01, bound 1 time(s)
2015-02-03 03:00:01.105 [TRACE] [.b.m.i.MiosBindingProviderImpl] - getItemNamesForProperty: MATCH property 'unit:nightmare,system:/ZWaveStatus' against BindingConfig.toProperty 'unit:nightmare,system:/ZWaveStatus'
2015-02-03 03:00:01.105 [TRACE] [.b.m.i.MiosBindingProviderImpl] - getItemNamesForProperty: MATCH property 'unit:nightmare,system:/ZWaveStatus' against BindingConfig.toProperty 'unit:nightmare,system:/ZWaveStatus'
2015-02-03 03:00:01.105 [DEBUG] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: Updating (Incremental) itemName 'SystemZWaveStatus' with value '5'
2015-02-03 03:00:01.105 [TRACE] [b.m.i.config.MiosBindingConfig] - createState: Converted '' to 'org.openhab.core.library.types.StringType', bound to 'class org.openhab.core.library.items.StringItem'
2015-02-03 03:00:01.105 [TRACE] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: transformation performed, from '5' to ''
2015-02-03 03:00:01.105 [DEBUG] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: Updating (Incremental) itemName 'SystemZWaveStatusString' with value ''
2015-02-03 03:00:01.105 [DEBUG] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: BOUND {mios="unit:nightmare,system:/ZWaveStatus"}, value=, bound 2 time(s)
2015-02-03 03:00:01.105 [TRACE] [.o.b.mios.internal.MiosBinding] - internalReceiveUpdate: itemName 'ZWaveDeviceStatus', newState 'PENDING', class 'class org.openhab.core.library.types.StringType'
2015-02-03 03:00:01.105 [TRACE] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: NOT BOUND {mios="unit:nightmare,system:/Mode"}, value=1
2015-02-03 03:00:01.105 [TRACE] [.b.m.i.MiosBindingProviderImpl] - getItemNamesForProperty: MATCH property 'unit:nightmare,system:/LocalTime' against BindingConfig.toProperty 'unit:nightmare,system:/LocalTime'
2015-02-03 03:00:01.105 [TRACE] [b.m.i.config.MiosBindingConfig] - createState: Converted '2015-02-03 03:00:01 N' to 'org.openhab.core.library.types.StringType', bound to 'class org.openhab.core.library.items.StringItem'
2015-02-03 03:00:01.105 [TRACE] [b.m.i.config.MiosBindingConfig] - transformIn: Converted value '2015-02-03 03:00:01 N' from StringType to more scoped type 'class org.openhab.core.library.types.StringType'
2015-02-03 03:00:01.105 [TRACE] [.o.b.mios.internal.MiosBinding] - internalPropertyUpdate: transformation performed, from '2015-02-03 03:00:01 N' to '2015-02-03 03:00:01 N'

It’s repeated about 25 times all right in quick succession (less than 100ms apart) when I’m doing a backup of the vera. Looks pretty harmless (everything is still working), but wanted to pass it along in case it was something worth investigating.

Gerry

#2

Thanks Gerry!

I found the full list of status’s here:
http://wiki.micasaverde.com/index.php/ZWave_Status

just waiting until my other change is approved, and then I’ll submit this one as a separate PR. It’ll require the examples/transform files to be reloaded, since I’m patching miosZWaveStatusIn.map.

For reference, the content will become:

0=Not Set 1=OK 2=Quitting 3=Waiting to Quit 4=No Dongle 5=Running Init/Configure Scripts 6=Failure -=Your guess is as good as mine!

#3

Since it had no overlapping files with my existing/open PR, I went ahead and filed PR #2077 to get it included.

#4

Great! I cut/pasted the new transform in and we’ll see how that goes tonight.

Gerry