Peter11

6 hours ago, Joshua Pressnell said:

You will need to edit the underlying homebridge configuration files to include the setup that the qmotion package requires.  They should provide an example of what options are needed.  Just be sure to leave the rest of the file formatting alone.  If you get something super screwed up, I can always help out.

Well I gave it a try, but not knowledgable enough to make it through.  Installing the plugin gives me the following error:

npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.

It appears that I need to create my own package.json file?  But that's way beyond my abilities.  

If anyone has installed the qmotion plugin for homebridge and has some advice, would be much appreciated.  Thanks

3 hours ago, Joshua Pressnell said:

Give it a try and let us know how it works!  Worst case, it should be pretty easy to revert back out if you don't like how it behaves.

Will do.  I'm going to try using this package

https://www.npmjs.com/package/qmotion

I purchased your software and pi device (I'm the guy that's emailed you a bit about the thermostat issues).  Anyway, I'm a bit of a novice and don't want to screw things up so I'll try to proceed with caution.   Not sure if I need to edit any files and to what extent.  

Does anyone have an experience using one of the Qmotion plugins for homebridge available at npm?

https://www.npmjs.com/search?q=qmotion

I have Qmotion shades with Qsync and I would like to be able to pull in to Homekit if possible.  I've read from some of the previous discussion how this can be tricky.