Closed danholt-international closed 4 years ago
I don't remember why I limited it. If you can test it I set the max value to 100000 that is direct sunlight. Install it from github and not from npm, it is not yet published on npm.
Hi!
No chance today to test… I am on a business trip. Please if possible load the update onto npm and I can arrange that one of our employees can update our homebridge and test it.
Regards
Daniel
Am 15.08.2019 um 10:48 schrieb ilcato notifications@github.com:
I don't remember why I limited it. If you can test it I set the max value to 100000 that is direct sunlight. Install it from github and not from npm, it is not yet published on npm.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ilcato/homebridge-Fibaro-HC2/issues/167?email_source=notifications&email_token=AMOQVBUGIIXA5LWV7RR2XELQEUJ43A5CNFSM4ILTUXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LHLUY#issuecomment-521565651, or mute the thread https://github.com/notifications/unsubscribe-auth/AMOQVBW7ICEPXFWMKEJ42C3QEUJ43ANCNFSM4ILTUXSQ.
You can install it with:
npm install -g https://github.com/ilcato/homebridge-Fibaro-HC2.git
npm ERR! code 128 npm ERR! Command failed: git clone --mirror -q https://github.com/ilcato/homebridge-Fibaro-HC2.git /root/.npm/_cacache/tmp/git-clone-ba590fc7/.git npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-ba590fc7/.git' npm ERR!
npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-08-15T11_19_34_457Z-debug.log
are you executing the command with root rights?
yes
Am 15.08.2019 um 14:55 schrieb ilcato notifications@github.com:
are you executing the command with root rights?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ilcato/homebridge-Fibaro-HC2/issues/167?email_source=notifications&email_token=AMOQVBSQV2KSXG5URKCL5BTQEVG5NA5CNFSM4ILTUXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LXI4A#issuecomment-521630832, or mute the thread https://github.com/notifications/unsubscribe-auth/AMOQVBT3VG2DDYAHJ3ZBF5DQEVG5NANCNFSM4ILTUXSQ.
run the sudo -s
command and then npm install -g https://github.com/ilcato/homebridge-Fibaro-HC2.git
same issue, sorry Will wait for the next official update.
Regards
Daniel
Am 15.08.2019 um 15:01 schrieb ilcato notifications@github.com:
run the sudo -s command and then npm install -g https://github.com/ilcato/homebridge-Fibaro-HC2.git
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ilcato/homebridge-Fibaro-HC2/issues/167?email_source=notifications&email_token=AMOQVBUDAHYR5D7BUYLGWUTQEVHTDA5CNFSM4ILTUXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LXVMY#issuecomment-521632435, or mute the thread https://github.com/notifications/unsubscribe-auth/AMOQVBRNXUDQASB26BQZE7DQEVHTDANCNFSM4ILTUXSQ.
Hi!
Any idea when you will publish the next official update release?
Am 15.08.2019 um 14:55 schrieb ilcato notifications@github.com:
are you executing the command with root rights?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ilcato/homebridge-Fibaro-HC2/issues/167?email_source=notifications&email_token=AMOQVBSQV2KSXG5URKCL5BTQEVG5NA5CNFSM4ILTUXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4LXI4A#issuecomment-521630832, or mute the thread https://github.com/notifications/unsubscribe-auth/AMOQVBT3VG2DDYAHJ3ZBF5DQEVG5NANCNFSM4ILTUXSQ.
Tonight
published
Still 10.000 Lux max in Home App 🙁
Did you restart homebridge? I’m out of home till next week, cannot test directly.
yes, i restarted homebridge. Maybe this is of interest too: The only sensor available in Home App to create an automation is motion. The LUX are not available and no temperature is available to use for an automation. Not sure if this is a HomeKit restriction or not. But great would be to create an automation that can be triggered by a specific LUX value für example.
@danholt-international, I fear that the old limit (10000) is stored on the homebridge local database. Are you able to test it on a fresh installation or to remove the accessories folder ? Regarding the opportunity to use a lux sensor as a trigger I think its a limit of the Home app. Other apps are able to use it.
Deleting the accessories folder made my day 😉 LUX values are correct now and also above the 10.000lux limit. GREAT! Had to rearrange all my devices in HomeKit because of the deletion of the accessories folder ... maybe there is some other solution to readjust the accessories in HomeBridge as any user who already has a motion sensor already in use, will run into the same problem when updating.
A fibaro motion sensor that reports more than 10.000 Lux in the Fibaro Home Center App stucks in HomeKit at 10.000lux. So in HomeKit the displayed value is 10.000lx permanently as long as the sensor senses values abobe
I am not sure if this is an issue of HomeKit Home App or an issue of the homebridge PlugIn.