- Platform information:
- Hardware: AMD 64
- OS: Ubuntu 18.04.03
- Java Runtime Environment: Zulu 8
- openHAB version: 2.4.0 stable (openhabian/repo install) / 2.5.0.M3 .deb package
- Issue of the topic: Can hardly get MiOS bridge binding to work
- Please post configurations (if applicable):
- Items configuration related to the issue
- Sitemap configuration related to the issue
- Rules code related to the issue
- Services configuration related to the issue
- If logs where generated please post these here using code fences:
I’m tearing my hair out trying to get my Vera controller into openHAB, I’m getting my Hue controller and Sonos stuff in without a hitch.
I have two done two separate installs but still can’t get it sorted.
I’m using the PaperUI and can install bindings for everything else and can also install the MiOS binding but can’t see it (seems to be standard).
I have enabled “Include legacy 1.x Bindings” and “Access Remote Repository” and “Simple mode” under “Item Linking”.
Sonos and Hue, hunky dory but not MiOS.
Tried following the https://www.openhab.org/addons/bindings/mios1/ Config but I’m getting lost a bit through.
Configuration / MiOS Unit Configuration.
/etc/openhab2/services/mios.cfg is present and there I set the IP of my Vera controller.
But the reference to openhab.cfg seems old afaikt.
ref:Where is the configuration file?
Openhab.cfg is not used in OpenHAB2/PaperUI.
Not a problem, /etc/openhab2/transform/ is populated with files, assuming from the MiOS binding install.
de.map miosDimmerCommand.map miosMSwitch5.map miosStatusIn.map miosTStatSetpointCoolCommand.map miosWeatherConditionGroupIn.map en.map miosLockCommand.map miosMSwitch6.map miosSwitchIn.map miosTStatSetpointHeatCommand.map miosZWaveStatusIn.map miosArmedCommand.map miosMSwitch1.map miosMSwitch7.map miosSwitchOut.map miosUPnPRenderingControlMuteCommand.map readme.txt miosContactIn.map miosMSwitch2.map miosMSwitch8.map miosTStatFanOperatingModeCommand.map miosUPnPRenderingControlVolumeCommand.map miosContactOut.map miosMSwitch3.map miosSceneActiveIn.map miosTStatModeStatusCommand.map miosUPnPTransportStatePlayModeCommand.map miosDeviceStatusUI.map miosMSwitch4.map miosShutterCommand.map miosTStatSetpointCommand.map miosUnSwitchIn.map
Here is where I’m starting to get lost.
The first part give me some info and examples of the bindings, sure.
I’m using the https://github.com/openhab/openhab1-addons/tree/master/bundles/binding/org.openhab.binding.mios/examples/scripts scripts with a small mod. Port 49451 that the miosLoad.sh (again, I’m assuming it’s age that is showing here, the scripts are 5 years old) doesn’t work but I have to use port 3480 instead to get the config read out from the Vera unit.
miosTransform.sh and everything works fine, I get my house.items file and copy it to /etc/openhab2/items/ and there is where I got lost.
PaperUI is not showing anything at all and I can’t get any switches or anything MiOS related showing here.
I’m assuming it shouldn’t since the bride binding is a legacy 1.x binding. Is that correct?
Am I forced to other GUI:s besides PaperUI when using legacy bindings?
I can get switches working via basicui but that includes loads of manual work configuring all of the switches, layout and everything and going through all that work for every single one of them is not something I’m wishing to do. If that is the case I will probably give up on OpenHAB and look elsewhere, it looked somewhat more promising then Home Assistant up until this… =/
All the forum posts I have found regarding this is also either old (2+ years) or not as comprehensive as I need to get it sorted. Some of them allude to getting things working in paperui but not stated clearly.