Event errors about habapp

[spacemanspiff2007]

The issue arrises because the switch has the value 0 and 1 instead of ON or OFF.

Invalid value for SwitchItem HSM200LightControlStatus4: 1

Unfortunately I am unfamiliar with the MiOS binding, but I found something with transformations in the documentation.
Have you set it up accordingly? Hope this helps.

BTW, I'm not saying there is anything wrong with your great library, my OH installation has grown over the years, and there is some weird convoluted stuff in there.

No problem, I'd happily fix any bugs or discuss problems/issues.

[NickWaterton]

Interesting. These items were actually set up by an automated mios configuration script (part of the mios setup). It also installs a bunch of standard mios maps in the transforms directory. Seeing as they worked in OH I never bothered manually editing them . Anyone that uses the mios binding probably has a similar set up, as it is very complicated to set up by hand - hence the automated script. As I say this was way back in the day though. So, do I fix these in the item definition, or do we update HABApp to support 0/1 as valid values for switches? Nick Waterton P.Eng Sent from my iPhone On Sep 28, 2019, at 11:56 AM, spacemanspiff2007 <[email protected]> wrote:  The issue arrises because the switch has the value 0 and 1 instead of ON or OFF. Invalid value for SwitchItem HSM200LightControlStatus4: 1 Unfortunately I am unfamiliar with the MiOS binding, but I found something with transformations in the documentation<https://www.openhab.org/addons/bindings/mios1/#transformations-2>. Have you set it up accordingly? Hope this helps. BTW, I'm not saying there is anything wrong with your great library, my OH installation has grown over the years, and there is some weird convoluted stuff in there. No problem, I'd happily fix any bugs or discuss problems/issues. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#75?email_source=notifications&email_token=ACYJIZ5XORWFAPC2A76RWULQL55BZA5CNFSM4I3OPT32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD724TGY#issuecomment-536201627>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACYJIZYTTEQYZ3H6XJFNHCTQL55BZANCNFSM4I3OPT3Q>. Unsubscribe from GE's commercial electronic messages: http://sc.ge.com/*casl-unsubscribe Désabonner des messages électroniques commerciaux de GE: http://sc.ge.com/*lcap-desabonnement

[spacemanspiff2007]

My understanding is that you just need to create the transformation file (miosSwitchIn.map) and it should work.

1=ON
0=OFF

[NickWaterton]

The file miosSwitchIn.map does exist in the transforms directory, its contents are:

1=ON
0=OFF
true=ON
false=OFF
TRUE=ON
FALSE=OFF
yes=ON
no=OFF
YES=ON
NO=OFF

Also interestingly I don't actually use any of those items anywhere - as i say, they were created by a script, that just maps all the Vera configurations to OH items.

I'll try adding {,in:<inTransform>} see if that fixes it.

UPDATE:,
OK, added ,in:MAP(miosSwitchIn.map),out:MAP(miosSwitchOut.map) to the items, I'll see if the error go away.

[NickWaterton]

OK, adding that seems to have fixed the issue, no more errors when I trigger the devices (that I don't use anyway).

[spacemanspiff2007]

Okay, thanks for the feedback!