tag:blogger.com,1999:blog-8025834647965791999.post5210693290968910235..comments2023-03-21T20:18:38.661+11:00Comments on The Millhouse Group Blog: Green Millhouse: OK Google, turn on the living room air conditionerJohnhttp://www.blogger.com/profile/01728894916174854514noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8025834647965791999.post-27320844951101024342018-12-21T04:23:07.117+11:002018-12-21T04:23:07.117+11:00Maybe the issues tab is not enabled by default whe...Maybe the issues tab is not enabled by default when forking some project. However you can enable it in the settings - there should be a tab next to the "code" "pr" etc. tabs where you can change that. The only thing I am currently thinking about is whether it makes sense to track the issues there. The other option would be to use the issues from the original addon repo, although the broadlink binding is currently not merged there, so it might confuse people and also makes finding issues harder. Either way - issue tracking would be nice :)<br /><br />Regarding the "mapping": I just thought about it again. The current problem seems to be that one needs to configure an item, although I guess openHAB does not expects items to be configured with config options. However openHAB offers a "bridge" thing (https://www.openhab.org/docs/concepts/things.html#bridges) which could be used to set up the broadlink device and after that one could create other things for the devices to be controlled by the broadlink device. Those things can have config options for inserting the codes and a switch channel to link an item to it. Will probably need some work and restructuring, though.clelhttps://www.blogger.com/profile/02896257191034738422noreply@blogger.comtag:blogger.com,1999:blog-8025834647965791999.post-39439334783128803262018-12-20T14:01:43.053+11:002018-12-20T14:01:43.053+11:00Hi - thanks for the comments. I'd actually ass...Hi - thanks for the comments. I'd actually assumed that the missing "issues" tab was because my binding's repo is a fork of the OpenHAB addons repo - I'll have a hunt to see if it can be enabled. It makes sense to use it if at all possible, the thread over in the OpenHAB forum is getting pretty crazy!<br /><br />Re: the rule approach - I completely agree, and I think this is probably an abuse of the rules system. But I could not figure out any other way to (as you say) "map" the commands to a switch. The documentation suggests some application of a regex transform should be possible, but I was unable to get anything I tried to work. Johnhttps://www.blogger.com/profile/01728894916174854514noreply@blogger.comtag:blogger.com,1999:blog-8025834647965791999.post-18171979968967101912018-12-19T22:50:05.189+11:002018-12-19T22:50:05.189+11:00First of all, many thanks for taking over the deve...First of all, many thanks for taking over the development for the binding, publishing it to GitHub and your continuous improvements! I am really looking forward to see this integrated in openHAB. By the way: you can create PRs for their repo with [WIP] in the title and continue working as usual. This has the benefit that there are automated checks and builds for every commit you make. After you feel that the binding is ready for review you can simply remove the [WIP].<br /><br />I was on your GitHub page, unfortunately the issue option seems to be disabled, so I cannot create any issues there.<br /><br />Regarding this post: I don't like the described rule approach much. I mean - it works, but it is not that easy and intuitive to use. I thought it might be possible to directly use a switch item, although that will require some rethinking on how to "map" the broadlink commands to the switch.clelhttps://www.blogger.com/profile/02896257191034738422noreply@blogger.comtag:blogger.com,1999:blog-8025834647965791999.post-12416022332695159272018-12-07T21:01:34.284+11:002018-12-07T21:01:34.284+11:00Quick comment, you do not need the `;` at the end ...Quick comment, you do not need the `;` at the end of Xtend code lines. Except for return<br />Your rule could be made a bit simpler:<br /><br />rule "Translate Living Room ON/OFF to aircon state"<br />when<br /> Item AC_LIVING_ONOFF changed <br />then<br /> var daikinState = "DAIKIN_AIRCON_OFF"<br /> if (AC_LIVING_ONOFF.state == ON) daikinState = "DAIKIN_AIRCON_ON"<br /> RM3_MINI.sendCommand(daikinState)<br />end<br /><br />This way if the item changed to OFF or NULL (Reboot,reset...), the aircon defaults to OFF<br /><br />OR<br /><br />rule "Translate Living Room ON/OFF to aircon state"<br />when<br /> Item AC_LIVING_ONOFF changed <br />then<br /> if (AC_LIVING_ONOFF.state == NULL) return; // Do nothing<br /> RM3_MINI.sendCommand("DAIKIN_AIRCON_" + AC_LIVING_ONOFF.state.toString)<br />endvzorglubhttps://www.blogger.com/profile/10346523331152129026noreply@blogger.com