-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Act as humidifier #8
Comments
Now that the plugin has been updated, what do I put in the config file as ‘type’ to get the Humidifier Service? ?? |
I have no idea...I was hoping someone else would know actually! |
So you don't have to type anything. It worked for me but humidifier is pretty buggy and not very useful right now in my opinion. I can see only "set to" without number so I don't know what is actual speed in Home app until I tap on device. I moved back to fan. |
@boganov where does this go? I don’t have anything in either the main Homebridge config or the humidifier config that says “type” for the humidifier... |
@boganov Never mind, figured it out. I didn’t realize the plugin had been updated. Now my issue is that the new update won’t work - I keep getting the “typeerror miio.device is not a constructor” error message. I rolled back to 0.14.1 and that seems to have fixed it, although the device type is still a fan. I already have another fan in the same room so I’d prefer this to display as a humidifier. So, you have the newest update working? How may I ask did you do that? |
@boganov Please try it and let me know if functionality has improved when using the Home app |
@fenway062213 Yep, seems like miio also updates with this plugin, had the same issue. Well, I'm not sure what to do in your case. I simply switch between fan and humidifier with type:"Fan" line in config and it works for me now. Probably deleting cachedAccessories may help, the file is in .homebridge/accessories folder. Don't know where is it in Linux since I use Windows machine as homebridge server. Warning: If you have many devices in homebridge (especially from aqara) this may force you to setup everything again, but maybe this is only Windows or simply my newbie problem and in your case everything will be fine. |
@leoneleone Tried your commit, not much changed for me, only "set to" changed to "rising to". I can't see current value: Edit: Oops, "Set to" is for Auto mode, "Rising to" is for Humidify mode. So nothing really changed in this. Probably it is working better and as it should but I prefer to see what current speed is, so will return to Fan right now. |
@boganov Thanks for your help...for some reason I just can’t get past getting the new update installed. I keep getting the same “not a constructor” error message and having to roll back to the older version. I’m running Homebridge on a Mac with High Sierra. You’re using Windows, right? Maybe it’s a Mac specific problem... |
@fenway062213 Downgrade miio version to fix your ‘not a constructor’ problem |
@leoneleone that’s what I ended up doing...I’d like to be able to update the plugin though, since I’d prefer my humidifier to act as a humidifier in the app and not a fan...for now I’m back on 0.14.1. |
@fenway062213 @boganov |
@leoneleone I did do that...unfortunately, since the latest update isn’t working for me, I had to revert back to 0.14.1, where it won’t display as a humidifier either way, right? Just wanted to make sure I wasn’t missing anything... |
@fenway062213
@boganov |
Yep, I have exactly the same config for this platform as tutorial says, nothing special. If I remove "type": "Fan" it acts as humidifier but since I don't like it I keep using it as a fan. |
@boganov @fenway062213 |
@leoneleone thanks again for the help with this. I just want to make sure I’m getting this right. So, running 0.14.1, this is what my Homebridge config looks like for the humidifier: There is no “type” section, and yet the device is still showing as a fan...am I missing something obvious? (Sorry if I am...) |
@fenway062213 @boganov @acc-ua |
@leoneleone |
@boganov @fenway062213 @acc-ua |
@leoneleone thanks again for the help. I went ahead and did that, and the humidifier is still showing as a fan. I also tried deleting both the accessories and the persist folders, deleting Homebridge, and reinstalling, and again it’s displaying as a fan. Very strange... Edited to add: I definitely feel like I’m missing a step here. So, the way it should work as i understand it, is that running 0.14.1, and not having the “type: fan” line included in the json, means that it should show up as a humidifier and not a fan. And no other steps are needed at all? I can see that you updated some files a few days ago. I haven’t touched those at all...is there anything I should be doing with them? Downloading and saving them somewhere on my computer? Again, sorry if I’m being dense... |
@fenway062213 i'm quite new in a theme of npm and other package managers. But may be the main problem that NPM still install old version of plugin? |
Hi @donatelloth, thanks for chiming in! Sorry, as you can probably see above I’m new to this stuff too...so when you say that you just copied the files physically, which files did you copy - from where, and to where? Thanks again... |
@fenway062213 for me these steps were the solution:
May be this is the real direct and dumb approach but it helped for me |
@donatelloth That worked!! Thank you very much!! I feel so silly...I definitely downloaded the repo, and could have sworn I’d installed it, but apparently, I did not... Such a minor thing but it was bugging the crap out of me, and it’s way better not having two “fans” int the same room. @boganov and @leoneleone, thanks as well for helping with this issue too. |
Hello again everyone...I'm back yet again and have the same exact problem. Long story short, I recently moved into a new home, and got a new Mac mini to act as my Homebridge server (among other things). I set it up from a Time Machine backup of my old Mac mini, so I could give that one to family. Seemed simple at first... Somewhere along the way of getting Homebridge up and running, I'm encountering the same issue - my humidifier will only show up in the Home app as a fan. I've reread through this thread and tried following all the same steps again, but I think moving has turned my brain to mush. So, if you kind people could just bear with me one more time... I have downloaded the repo from the link provided by @donatelloth above, and copied its contents into the humidifier folder in /usr/local/lib/node_modules. I'm running [email protected] and [email protected]. My Homebridge config.json has no "type" line, but I've also experienced with added a "type: humidifier" line, both to no avail. Whenever I add Homebridge to the Home app, the humidifier shows as a fan, which is super annoying since I already have a fan in the room that it's in... So, I hate to bug you guys yet again, but am I missing something obvious again this time?? Again, the recent move has done me in... Thank you, as always, for any help and suggestions you might have! |
Wanted to add that this is the error message I'm now getting... /usr/local/lib/node_modules/miio/lib/createDevice.js:7 Error: Address to device is required Edited to add that this error message occurs when I start up Homebridge after copying @donatelloth instructions above, exactly (ie, copying the files from the downloaded repo into the usr/local/lib/node_modules plugin folder). Those instructions worked before but now I'm getting this darn error message. I then go and sudo npm install -g homebridge-xiaomi-humidifier and the error message goes away, and Homebridge starts normally, but the device shows up as a fan. |
Anyone know of a way to get it to act as a humidifier instead of a fan now that Homekit supports humidifiers?
The text was updated successfully, but these errors were encountered: