homebridge-edomoticz Plugin

[deejc]

Did you guys already check out the 'Home' app that comes with the iOS 10 update?
For more info of what i'm talking about see: http://www.apple.com/ios/home/

Are there any possibilities to include these features in a future version?

Check out the first post in this thread and post the json output of the devices and they will get added (if possible)


Sent from my iPhone using Tapatalk

[Marci]

Did you guys already check out the 'Home' app that comes with the iOS 10 update?
For more info of what i'm talking about see: http://www.apple.com/ios/home/

My first experiences are quite good!

Yes, if you read the thread you'll find it discussed frequently, however it only supports native services. All custom services show as unsupported, hence Eve is preferred.

As far as i know you cannot configure a remote server.
On the website Apple mentions you can use an Apple TV as 'server' for remote access (and automation), rumor has it that its also possible to use an iPad if you have one laying around in the house.

You do realise this is standard HomeKit protocol and has been since iOS8...? AppleTV for remote access has been the remote method for 3 years. The iPad is a new addition with iOS10, all discussed in the thread.

Supported device types are (according to Apple):

In my situation I have the following devices linked:
- Fibaro Roller / Shutter -> identified as switch
- Marmitek DS90 Door contact -> identified as switch
- Marmitek MS90 Motion sensor -> identified as switch
- Aeotec Siren -> identified as switch
- Dummy switch representing alarm arm/disarm state -> identified as switch
It would be great if these would be mapped to a better representing device type / icon for better overview, e.g. by looking at the type/icon the device has in Domoticz.
Are there any possibilities to include these features in a future version?

See q&a in the first post. For better device support post JSON for each requested device to the GitHub issues page.

[nfaber]

Did you guys already check out the 'Home' app that comes with the iOS 10 update?
For more info of what i'm talking about see: http://www.apple.com/ios/home/

Are there any possibilities to include these features in a future version?

Check out the first post in this thread and post the json output of the devices and they will get added (if possible)


Sent from my iPhone using Tapatalk

Thanks for pointing that out!

• Sockets (on/off) - Domoticz SwitchTypeVal: 0
• Lamps (on/off) - Domoticz SwitchTypeVal: 0
• Lamps (dimmer) - Domoticz SwitchTypeVal: 7
• Contact Sensors - Domoticz SwitchTypeVal: 2
• Smoke Detectors - Domoticz SwitchTypeVal: 5
• Motion Sensors - Domoticz SwitchTypeVal: 8
• Window Coverings - Domoticz SwitchTypeVal: 3 & 13
• Occupancy Sensor - any SwitchTypeVal: 0 with "Occupied" in it's title

I changed my Fibaro Roller / Shutter devices into 'shutter percentage' mode (SwitchTypeVal=13).
That fixed the icon and allows me to shut it also partially.
One thing that seems a bit buggy is that if the device is 'open' in Domoticz, the iOS app says 'closed'.
In JSON Status='open' as well, so this might be something that is processed wrong by homebridge-edomoticz.

I set my Marmitek door and motion sensors to SwitchTypeVal=2 / SwitchTypeVal=8 respectively.
Now i indeed have the corresponding icons in the Home app (the motion sensor icon is quite weird though).
Im haven't had the time to test the sensors yet, i will do this later.
As long as open/close or motion/no motion states can be seen this is OK for me (sensors also have a tamper state but that is less important).

I would like to have a way to identify the Alarm armed/disarmed switch and Siren.
These do not really match with any of the supported types in homebridge-edomoticz.
In Domoticz these both have SwitchTypeVal=0 and Image="Alarm" / Image="Speaker" such that the icon matches more or less with the function.
Would it be possible to assign types to homebridge devices based on Image property, next to SwitchTypeVal?
To me it is only for visual purposes (make use of all icons in the app), they should keep behaving as generic binary switches.

[Marci]

For a device to be mapped to a native service type in HomeKit, it must specify the minimum required parameters and interact with a service in the way that HomeKit expects. It's not a case of forcing a mapping to get an icon how you want it in HomeKit. If the device cannot comply to homekit's minimum requirement for it's official service type, it will invalidate the HomeKit spec and merely appear as 'unsupported' in iOS10's home app. A straightforward on/off state is not enough data to comply with homekit's security device types. If the HomeKit spec has no siren service, then it will show as unsupported if forced to anything other than a switch, and won't be queriable via Siri.

Icon types are not appropriate for identifying service types within domoticz, and implementing this creates too many combinations to fathom. E.g.: I have multiple different switches and sensors with icon set to alarm in Domoticz, and various audio devices with icon set to speaker, which report temperature, power state and more.

SwitchTypeVal is used for anything switchy. Type and SubType are used to do anything else. If you want us to look at supporting your devices, post the json to GitHub as requested, and we'll let you know either way what is doable for each specific device.

The blinds problem is a known issue as raised by others in the thread and is linked to iOS10's home app interpreting responses differently to the previous HomeKit spec. A fix may appear in time.

Fact is, for convenience of sensor support, iOS10 Home app is the worst app on the market as it is locked entirely to apple's own certified characteristics and will only handle custom services if approved by MFi programme & accompanied by Apple's MFi security chip.
For convenience of accessing switches, it's the best on the market.

If you want flexible sensor support, which allows unlimited sensor types use Eve.

[nfaber]

For a device to be mapped to a native service type in HomeKit, it must specify the minimum required parameters and interact with a service in the way that HomeKit expects. It's not a case of forcing a mapping to get an icon how you want it in HomeKit. If the device cannot comply to homekit's minimum requirement for it's official service type, it will invalidate the HomeKit spec and merely appear as 'unsupported' in iOS10's home app. A straightforward on/off state is not enough data to comply with homekit's security device types. If the HomeKit spec has no siren service, then it will show as unsupported if forced to anything other than a switch, and won't be queriable via Siri.

Icon types are not appropriate for identifying service types within domoticz, and implementing this creates too many combinations to fathom. E.g.: I have multiple different switches and sensors with icon set to alarm in Domoticz, and various audio devices with icon set to speaker, which report temperature, power state and more.

SwitchTypeVal is used for anything switchy. Type and SubType are used to do anything else. If you want us to look at supporting your devices, post the json to GitHub as requested, and we'll let you know either way what is doable for each specific device.

Thanks for pointing this out.
I have no clue how complicated Apple's protocol is, based on your comments i clearly underestimated this.

The blinds problem is a known issue as raised by others in the thread and is linked to iOS10's home app interpreting responses differently to the previous HomeKit spec. A fix may appear in time.

Ok, good to know!
I will keep checking the thread for news about this.

Fact is, for convenience of sensor support, iOS10 Home app is the worst app on the market as it is locked entirely to apple's own certified characteristics and will only handle custom services if approved by MFi programme & accompanied by Apple's MFi security chip.
For convenience of accessing switches, it's the best on the market.

If you want flexible sensor support, which allows unlimited sensor types use Eve.

In my opinion the Home app is very user-friendly, and integration in the bottom overlay menu is a unique benefit.
I tried apps such as Eve and Insteon in the past, but these have too much bells and whistles to my taste and for my family to use it.
It doesn't suprise me that Apple provides little possibilities to integrate with third party hardware though.
Still i'm more than satisfied with the functionality that I got thanks to your work, thanks a million!

[miko1979]

I used the homekit for months right now without having problems. Today i updated domoticz to the latest beta, homekit was still working fine. After that i removed 3 lightbulbs in domoticz, then i tried removing these devices from homekit, after i removed the first bulb inde homekit app, all devices where gone including the bridge. Restarting domoticz or the complete raspberry was not solving this issue.
Theni opened the log:
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdn ... ceRegister>
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:62
let port = this._tcpServer.address().port;
^^^
SyntaxError: Unexpected strict mode reserved word
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:11:25)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
error: Forever detected script exited with code: 1
error: Script restart attempt #7

Any idea what is wrong and how to solve this?


Verzonden vanaf mijn iPad met Tapatalk

[Marci]

Guessing you upgraded homebridge also? Need to upgrade your version of node to 4.32 or better and recompile everything (npm rebuild) to use latest homebridge/hap-nodejs, due to Khaos using the 'let' command.

[miko1979]

Correct, i upgraded homebridge as well.
i tried updating nodes as well, but for whatever reason i was not successful in starting edomitcz. i then decided to start blank ( i have only 5 devices for homekit).

i started upgrading the complete system:
sudo apt-get update && sudo apt-get upgrade

i manually removed the homekit folders in /usr/local/lib/node_modules/
Then i runned to install scripts as on page 1 of this topic.

but installing the homebridge is causing a lot of issues(sudo npm install -g homebridge)
installing homebridge-edomoticz works perfect, also the forever can be installed.

below the complete output of the installation of homebridge.

/usr/bin/homebridge -> /usr/lib/node_modules/homebridge/bin/homebridge

> [email protected] install /usr/lib/node_modules/homebridge/node_modules/mdns
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/6.3.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp"
make: Entering directory '/usr/lib/node_modules/homebridge/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from ../src/mdns.hpp:12:0,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan.h:43:3: error: #error This version of node/NAN/v8 requires a C++11 compiler
In file included from /usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/node.h:42:0,
from ../src/mdns.hpp:11,
from ../src/dns_sd.cpp:1:
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:341:1: error: expected unqualified-id before ‘using’
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:477:1: error: expected unqualified-id before ‘using’
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:871:1: error: expected unqualified-id before ‘using’
In file included from ../node_modules/nan/nan.h:190:0,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_maybe_43_inl.h:13:1: error: expected unqualified-id before ‘using’
../node_modules/nan/nan_maybe_43_inl.h:16:1: error: expected unqualified-id before ‘using’
../node_modules/nan/nan_maybe_43_inl.h:19:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:24:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:31:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:36:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:41:1: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:46:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:51:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:59:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:64:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:69:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:76:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:83:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:91:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:98:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:108:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:114:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:118:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:125:1: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:130:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:135:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:139:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:145:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:150:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:156:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:162:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:168:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:174:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:180:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:186:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:194:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:201:1: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:205:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:209:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:213:8: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:217:8: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_maybe_43_inl.h:237:8: error: ‘MaybeLocal’ does not name a type
In file included from ../node_modules/nan/nan.h:195:0,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_converters.h:14:11: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_converters.h:16:56: error: ‘Maybe’ does not name a type
../node_modules/nan/nan_converters.h:26:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:27:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:28:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:29:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:30:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:31:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:32:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:42:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:43:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:44:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:45:1: error: ‘return_t’ does not name a type
../node_modules/nan/nan_converters.h:46:1: error: ‘return_t’ does not name a type
In file included from ../node_modules/nan/nan_converters.h:59:0,
from ../node_modules/nan/nan.h:195,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_converters_43_inl.h:18:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Boolean>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:19:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Number>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:20:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::String>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:21:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Object>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:22:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Integer>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:23:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Uint32>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:24:1: error: ‘return_t’ in ‘struct Nan::ToFactory<v8::Int32>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:34:1: error: ‘return_t’ in ‘struct Nan::ToFactory<bool>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:35:1: error: ‘return_t’ in ‘struct Nan::ToFactory<double>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:36:1: error: ‘return_t’ in ‘struct Nan::ToFactory<long long int>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:37:1: error: ‘return_t’ in ‘struct Nan::ToFactory<unsigned int>’ does not name a type
../node_modules/nan/nan_converters_43_inl.h:38:1: error: ‘return_t’ in ‘struct Nan::ToFactory<int>’ does not name a type
In file included from ../node_modules/nan/nan.h:196:0,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_new.h: In function ‘v8::Local<T> Nan::To(v8::Local<v8::Integer>) [with T = v8::Integer]’:
../node_modules/nan/nan_new.h:21:32: error: no matching function for call to ‘To(v8::Local<v8::Integer>&)’
../node_modules/nan/nan_new.h:21:32: note: candidate is:
../node_modules/nan/nan_converters.h:53:38: note: template<class T> typename Nan::ToFactory::return_t Nan::To(v8::Local<v8::Value>)
../node_modules/nan/nan_new.h: In function ‘v8::Local<T> Nan::To(v8::Local<v8::Integer>) [with T = v8::Int32]’:
../node_modules/nan/nan_new.h:28:30: error: no matching function for call to ‘To(v8::Local<v8::Integer>&)’
../node_modules/nan/nan_new.h:28:30: note: candidate is:
../node_modules/nan/nan_converters.h:53:38: note: template<class T> typename Nan::ToFactory::return_t Nan::To(v8::Local<v8::Value>)
../node_modules/nan/nan_new.h: In function ‘v8::Local<T> Nan::To(v8::Local<v8::Integer>) [with T = v8::Uint32]’:
../node_modules/nan/nan_new.h:35:31: error: no matching function for call to ‘To(v8::Local<v8::Integer>&)’
../node_modules/nan/nan_new.h:35:31: note: candidate is:
../node_modules/nan/nan_converters.h:53:38: note: template<class T> typename Nan::ToFactory::return_t Nan::To(v8::Local<v8::Value>)
../node_modules/nan/nan_new.h: At global scope:
../node_modules/nan/nan_new.h:43:11: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan_new.h:75:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:141:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:147:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:148:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:160:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:161:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:162:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:163:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:165:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:166:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:182:17: error: ‘return_t’ does not name a type
../node_modules/nan/nan_new.h:183:17: error: ‘return_t’ does not name a type
In file included from ../node_modules/nan/nan_new.h:189:0,
from ../node_modules/nan/nan.h:196,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_implementation_12_inl.h:61:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::Date>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static Nan::FactoryBase<v8::Function>::return_t Nan::Factory<v8::Function>::New(Nan::FunctionCallback, v8::Local<v8::Value>)’:
../node_modules/nan/nan_implementation_12_inl.h:95:46: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static Nan::FactoryBase<v8::FunctionTemplate>::return_t Nan::Factory<v8::FunctionTemplate>::New(Nan::FunctionCallback, v8::Local<v8::Value>, v8::Local<v8::Signature>)’:
../node_modules/nan/nan_implementation_12_inl.h:123:48: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan_implementation_12_inl.h: At global scope:
../node_modules/nan/nan_implementation_12_inl.h:202:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::RegExp>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:221:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::Script>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:227:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::Script>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:259:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:267:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:273:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:280:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:286:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:291:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:352:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::UnboundScript>’ does not name a type
../node_modules/nan/nan_implementation_12_inl.h:359:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::UnboundScript>’ does not name a type
In file included from ../node_modules/nan/nan.h:196:0,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_new.h:293:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:299:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:305:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:311:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:317:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:323:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:329:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::String>’ does not name a type
../node_modules/nan/nan_new.h:335:1: error: ‘return_t’ in ‘struct Nan::Factory<v8::RegExp>’ does not name a type
In file included from ../src/mdns.hpp:12:0,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::Error(const char*)’:
../node_modules/nan/nan.h:655:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::ThrowError(const char*)’:
../node_modules/nan/nan.h:655:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::RangeError(const char*)’:
../node_modules/nan/nan.h:656:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::ThrowRangeError(const char*)’:
../node_modules/nan/nan.h:656:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::ReferenceError(const char*)’:
../node_modules/nan/nan.h:657:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::ThrowReferenceError(const char*)’:
../node_modules/nan/nan.h:657:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::SyntaxError(const char*)’:
../node_modules/nan/nan.h:658:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::ThrowSyntaxError(const char*)’:
../node_modules/nan/nan.h:658:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::TypeError(const char*)’:
../node_modules/nan/nan.h:659:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::ThrowTypeError(const char*)’:
../node_modules/nan/nan.h:659:3: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: At global scope:
../node_modules/nan/nan.h:667:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:689:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:705:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:718:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:735:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:741:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:749:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:756:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:762:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h: In member function ‘void Nan::Callback::SetFunction(const v8::Local<v8::Function>&)’:
../node_modules/nan/nan.h:1398:40: error: ‘Set’ was not declared in this scope
../node_modules/nan/nan.h:1398:40: note: suggested alternative:
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:3067:17: note: ‘v8::Set’
../node_modules/nan/nan.h: In member function ‘void Nan::AsyncWorker::SaveToPersistent(const char*, const v8::Local<v8::Value>&)’:
../node_modules/nan/nan.h:1518:41: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::AsyncWorker::GetFromPersistent(const char*) const’:
../node_modules/nan/nan.h:1536:45: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In member function ‘virtual void Nan::AsyncWorker::HandleErrorCallback()’:
../node_modules/nan/nan.h:1570:58: error: no matching function for call to ‘New(const char*)’
../node_modules/nan/nan.h:1570:58: note: candidates are:
../node_modules/nan/nan_implementation_12_inl.h:395:21: note: template<class T, class M> v8::Local<T> Nan::New(const v8::Persistent<S, M>&)
../node_modules/nan/nan_implementation_12_inl.h:400:21: note: template<class T, class M> v8::Local<T> Nan::New(const Nan::Persistent<T, M>&)
../node_modules/nan/nan_implementation_12_inl.h:405:21: note: template<class T> v8::Local<T> Nan::New(const Nan::Global<T>&)
../node_modules/nan/nan_new.h:201:1: note: template<class T> typename Nan::Factory::return_t Nan::New()
../node_modules/nan/nan_new.h:207:1: note: template<class T, class A0> typename Nan::Factory<T>::return_t Nan::New(A0)
../node_modules/nan/nan_new.h:213:1: note: template<class T, class A0, class A1> typename Nan::Factory<T>::return_t Nan::New(A0, A1)
../node_modules/nan/nan_new.h:219:1: note: template<class T, class A0, class A1, class A2> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2)
../node_modules/nan/nan_new.h:225:1: note: template<class T, class A0, class A1, class A2, class A3> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2, A3)
../node_modules/nan/nan_new.h:237:1: note: template<class T> typename Nan::Factory::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>)
../node_modules/nan/nan_new.h:245:1: note: template<class T, class A2> typename Nan::Factory<T>::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>, A2)
../node_modules/nan/nan.h: In function ‘void Nan::SetMethodAux(T, v8::Local<v8::String>, v8::Local<v8::FunctionTemplate>, ...)’:
../node_modules/nan/nan.h:1872:34: error: there are no arguments to ‘GetFunction’ that depend on a template parameter, so a declaration of ‘GetFunction’ must be available [-fpermissive]
../node_modules/nan/nan.h:1872:34: note: (if you use ‘-fpermissive’, G++ will accept your code, but allowing the use of an undeclared name is deprecated)
../node_modules/nan/nan.h: In function ‘void Nan::SetMethod(HandleType<T>, const char*, Nan::FunctionCallback)’:
../node_modules/nan/nan.h:1884:45: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::SetPrototypeMethod(v8::Local<v8::FunctionTemplate>, const char*, Nan::FunctionCallback)’:
../node_modules/nan/nan.h:1899:45: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, Nan::Sig)’:
../node_modules/nan/nan.h:1924:47: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan.h: In function ‘bool Nan::SetAccessor(v8::Local<v8::Object>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
../node_modules/nan/nan.h:1967:51: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan.h: In function ‘void Nan::SetNamedPropertyHandler(v8::Local<v8::ObjectTemplate>, Nan::PropertyGetterCallback, Nan::PropertySetterCallback, Nan::PropertyQueryCallback, Nan::PropertyDeleterCallback, Nan::PropertyEnumeratorCallback, v8::Local<v8::Value>)’:
../node_modules/nan/nan.h:2026:47: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan.h: In function ‘void Nan::SetIndexedPropertyHandler(v8::Local<v8::ObjectTemplate>, Nan::IndexGetterCallback, Nan::IndexSetterCallback, Nan::IndexQueryCallback, Nan::IndexDeleterCallback, Nan::IndexEnumeratorCallback, v8::Local<v8::Value>)’:
../node_modules/nan/nan.h:2096:47: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan.h: In function ‘void Nan::SetCallHandler(v8::Local<v8::FunctionTemplate>, Nan::FunctionCallback, v8::Local<v8::Value>)’:
../node_modules/nan/nan.h:2151:47: error: ‘NewInstance’ was not declared in this scope
../node_modules/nan/nan.h: In function ‘void Nan::SetCallAsFunctionHandler(v8::Local<v8::ObjectTemplate>, Nan::FunctionCallback, v8::Local<v8::Value>)’:
../node_modules/nan/nan.h:2173:47: error: ‘NewInstance’ was not declared in this scope
In file included from ../src/mdns.hpp:12:0,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan.h: In function ‘void Nan::Export(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE, const char*, Nan::FunctionCallback)’:
../node_modules/nan/nan.h:2200:35: error: no matching function for call to ‘New(const char*&)’
../node_modules/nan/nan.h:2200:35: note: candidates are:
../node_modules/nan/nan_implementation_12_inl.h:395:21: note: template<class T, class M> v8::Local<T> Nan::New(const v8::Persistent<S, M>&)
../node_modules/nan/nan_implementation_12_inl.h:400:21: note: template<class T, class M> v8::Local<T> Nan::New(const Nan::Persistent<T, M>&)
../node_modules/nan/nan_implementation_12_inl.h:405:21: note: template<class T> v8::Local<T> Nan::New(const Nan::Global<T>&)
../node_modules/nan/nan_new.h:201:1: note: template<class T> typename Nan::Factory::return_t Nan::New()
../node_modules/nan/nan_new.h:207:1: note: template<class T, class A0> typename Nan::Factory<T>::return_t Nan::New(A0)
../node_modules/nan/nan_new.h:213:1: note: template<class T, class A0, class A1> typename Nan::Factory<T>::return_t Nan::New(A0, A1)
../node_modules/nan/nan_new.h:219:1: note: template<class T, class A0, class A1, class A2> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2)
../node_modules/nan/nan_new.h:225:1: note: template<class T, class A0, class A1, class A2, class A3> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2, A3)
../node_modules/nan/nan_new.h:237:1: note: template<class T> typename Nan::Factory::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>)
../node_modules/nan/nan_new.h:245:1: note: template<class T, class A2> typename Nan::Factory<T>::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>, A2)
../node_modules/nan/nan.h:2201:47: error: ‘GetFunction’ was not declared in this scope
../node_modules/nan/nan.h:2201:65: error: ‘Set’ was not declared in this scope
../node_modules/nan/nan.h:2201:65: note: suggested alternative:
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:3067:17: note: ‘v8::Set’
../node_modules/nan/nan.h: In constructor ‘Nan::Tap::Tap(v8::Local<v8::Value>)’:
../node_modules/nan/nan.h:2208:30: error: no matching function for call to ‘To(v8::Local<v8::Value>&)’
../node_modules/nan/nan.h:2208:30: note: candidate is:
../node_modules/nan/nan_converters.h:53:38: note: template<class T> typename Nan::ToFactory::return_t Nan::To(v8::Local<v8::Value>)
../node_modules/nan/nan.h: In member function ‘void Nan::Tap::ok(bool, const char*)’:
../node_modules/nan/nan.h:2221:33: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: In member function ‘void Nan::Tap::pass(const char*)’:
../node_modules/nan/nan.h:2227:30: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../node_modules/nan/nan.h: At global scope:
../node_modules/nan/nan.h:2251:10: error: ‘MaybeLocal’ does not name a type
../node_modules/nan/nan.h:2256:40: error: ‘MaybeLocal’ was not declared in this scope
../node_modules/nan/nan.h:2256:40: note: suggested alternative:
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:113:7: note: ‘v8::MaybeLocal’
../node_modules/nan/nan.h:2256:52: error: template argument 1 is invalid
../node_modules/nan/nan.h:2256:54: error: expected unqualified-id before ‘>’ token
../node_modules/nan/nan.h:2265:1: error: ‘MaybeLocal’ does not name a type
In file included from ../src/dns_sd.cpp:5:0:
../src/mdns_utils.hpp: In function ‘v8::Local<v8::Value> node_mdns::stringOrUndefined(const char*)’:
../src/mdns_utils.hpp:50:40: error: no matching function for call to ‘New(const char*&)’
../src/mdns_utils.hpp:50:40: note: candidates are:
../node_modules/nan/nan_implementation_12_inl.h:395:21: note: template<class T, class M> v8::Local<T> Nan::New(const v8::Persistent<S, M>&)
../node_modules/nan/nan_implementation_12_inl.h:400:21: note: template<class T, class M> v8::Local<T> Nan::New(const Nan::Persistent<T, M>&)
../node_modules/nan/nan_implementation_12_inl.h:405:21: note: template<class T> v8::Local<T> Nan::New(const Nan::Global<T>&)
../node_modules/nan/nan_new.h:201:1: note: template<class T> typename Nan::Factory::return_t Nan::New()
../node_modules/nan/nan_new.h:207:1: note: template<class T, class A0> typename Nan::Factory<T>::return_t Nan::New(A0)
../node_modules/nan/nan_new.h:213:1: note: template<class T, class A0, class A1> typename Nan::Factory<T>::return_t Nan::New(A0, A1)
../node_modules/nan/nan_new.h:219:1: note: template<class T, class A0, class A1, class A2> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2)
../node_modules/nan/nan_new.h:225:1: note: template<class T, class A0, class A1, class A2, class A3> typename Nan::Factory<T>::return_t Nan::New(A0, A1, A2, A3)
../node_modules/nan/nan_new.h:237:1: note: template<class T> typename Nan::Factory::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>)
../node_modules/nan/nan_new.h:245:1: note: template<class T, class A2> typename Nan::Factory<T>::return_t Nan::New(Nan::FunctionCallback, v8::Local<v8::Value>, A2)
In file included from ../src/dns_sd.cpp:7:0:
../src/txt_record_ref.hpp: At global scope:
../src/txt_record_ref.hpp:11:36: error: ‘v8::Handle’ has not been declared
../src/txt_record_ref.hpp:11:42: error: expected ‘,’ or ‘...’ before ‘<’ token
../src/txt_record_ref.hpp:16:44: error: ‘v8::Handle’ has not been declared
../src/txt_record_ref.hpp:16:50: error: expected ‘,’ or ‘...’ before ‘<’ token
../src/txt_record_ref.hpp: In static member function ‘static bool node_mdns::TxtRecordRef::HasInstance(int)’:
../src/txt_record_ref.hpp:17:20: error: ‘value’ was not declared in this scope
../src/txt_record_ref.hpp:18:44: error: ‘value’ was not declared in this scope
In file included from ../src/dns_sd.cpp:9:0:
../src/socket_watcher.hpp: At global scope:
../src/socket_watcher.hpp:10:36: error: ‘v8::Handle’ has not been declared
../src/socket_watcher.hpp:10:42: error: expected ‘,’ or ‘...’ before ‘<’ token
../src/dns_sd.cpp: In function ‘void node_mdns::init(v8::Local<v8::Object>)’:
../src/dns_sd.cpp:56:38: error: no matching function for call to ‘node_mdns::TxtRecordRef::Initialize(v8::Local<v8::Object>&)’
../src/dns_sd.cpp:56:38: note: candidate is:
../src/txt_record_ref.hpp:11:21: note: static void node_mdns::TxtRecordRef::Initialize(int)
../src/txt_record_ref.hpp:11:21: note: no known conversion for argument 1 from ‘v8::Local<v8::Object>’ to ‘int’
../src/dns_sd.cpp:58:39: error: no matching function for call to ‘node_mdns::SocketWatcher::Initialize(v8::Local<v8::Object>&)’
../src/dns_sd.cpp:58:39: note: candidate is:
../src/socket_watcher.hpp:10:21: note: static void node_mdns::SocketWatcher::Initialize(int)
../src/socket_watcher.hpp:10:21: note: no known conversion for argument 1 from ‘v8::Local<v8::Object>’ to ‘int’
../src/dns_sd.cpp: In function ‘void node_mdns::defineFunction(v8::Local<v8::Object>, const char*, Nan::FunctionCallback)’:
../src/dns_sd.cpp:94:5: error: ‘Set’ is not a member of ‘Nan’
../src/dns_sd.cpp:94:5: note: suggested alternatives:
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:3067:17: note: ‘v8::Set’
/usr/lib/node_modules/homebridge/node_modules/mdns/.node-gyp/6.3.1/include/node/v8.h:3067:17: note: ‘v8::Set’
../src/dns_sd.cpp:94:37: error: ‘Nan::FactoryBase<v8::Boolean>::return_t’ has no member named ‘ToLocalChecked’
../src/dns_sd.cpp:95:13: error: ‘GetFunction’ is not a member of ‘Nan’
../src/dns_sd.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE node_mdns::buildException(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/dns_sd.cpp:107:57: error: no matching function for call to ‘To(v8::Local<v8::Value>)’
../src/dns_sd.cpp:107:57: note: candidate is:
../node_modules/nan/nan_converters.h:53:38: note: template<class T> typename Nan::ToFactory::return_t Nan::To(v8::Local<v8::Value>)
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::Error(const char*)’:
../node_modules/nan/nan.h:655:3: warning: control reaches end of non-void function [-Wreturn-type]
dns_sd_bindings.target.mk:140: recipe for target 'Release/obj.target/dns_sd_bindings/src/dns_sd.o' failed
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1
make: Leaving directory '/usr/lib/node_modules/homebridge/node_modules/mdns/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Linux 4.1.19-v7+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/homebridge/node_modules/mdns
gyp ERR! node -v v6.3.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
/usr/lib
└── (empty)

npm ERR! Linux 4.1.19-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge"
npm ERR! node v6.3.1
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/pi/npm-debug.log
npm ERR! code 1

[Marci]

Hmmm. You don't have a c++ compiler installed.

Run...

Code: Select all

sudo apt-get install build-essential

Then...

Code: Select all

sudo npm install -g homebridge --unsafe-perm

If it still doesn't work, post the output of...

Code: Select all

gcc-v

[Marci]

Upgrading the whole system may have upgraded you to node 6.6 which has issues with mdns. See steps in first post for removing and replacing node with node6.31, then issue..

Code: Select all

sudo npm rebuild

...within your homebridge folder.

[energie]

Correct, i upgraded homebridge as well.
i tried updating nodes as well, but for whatever reason i was not successful in starting edomitcz. i then decided to start blank ( i have only 5 devices for homekit).

i started upgrading the complete system:
sudo apt-get update && sudo apt-get upgrade

i manually removed the homekit folders in /usr/local/lib/node_modules/
Then i runned to install scripts as on page 1 of this topic.

but installing the homebridge is causing a lot of issues(sudo npm install -g homebridge)
installing homebridge-edomoticz works perfect, also the forever can be installed.

below the complete output of the installation of homebridge.

<cut>

I have been facing the same issue. I'm new to Homekit / Homebridge so I was a bit puzzled at first.

The root cause is that NodeJS (starting from a certain version - probably 4 - have not further looked in to this) and node-gyp / certain node modules require a compiler that is compatible with C++11. It so happens to be that Domoticz Raspberry PI SD Card images are/where based on Debian (7) Wheezy. This version is still offered with a pre-installed Domoticz version of 3530. If you so happen to be a user who's running Domoticz for over a year, like myself, than you're probably running Wheezy. And Wheezy doesn't support C++11 out-of-the-box. Internally the compilers are named gcc and g++. Within Wheezy the latest supported version is 4.6. The version of gcc/g++ that supports C++11 is version 4.9.This version is available on Debian (8) Jessie.

Luckily enough there is a workaround to install gcc/g++ version 4.9 on Wheezy. Follow the instructions provided here: http://stackoverflow.com/a/29729834/4181822

After completing those instructions you will now have both version 4.6 (still the system default) and 4.9 installed. To make version 4.9 the system default (which actually is required) execute these commands:

Code: Select all

sudo rm /usr/bin/gcc
sudo rm /usr/bin/g++

sudo ln -s /usr/bin/gcc-4.9 /usr/bin/gcc
sudo ln -s /usr/bin/g++-4.9 /usr/bin/g++

[miko1979]

Thanks Energie!! that solved the issue. After that th ehomebrdige was still not visible in homekit, removing the files from the persist folder and a restart of homebrdige solved the issue! thansk again.

[Marci]

Cheers for the detail @energie - will add that into wheezy destructions in first post...!

[TheRamon]

For anyone that was having issues with dimmers on the mqtt-integration branch lately, there was a variable missing that caused a crash. Have just added it in the latest version! Please update

[rwijbenga]

How can I update to the new branch ?

I have used the NPM install to get started.

Or should I wait for the NPM version to be updated with all the new goodies such as webcam support...

[deejc]

if anyone is interested, Amazon got EVE Weather today for £14.97 for prime members

Elgato Eve Weather, Wireless Outdoor Sensor with Apple HomeKit technology, white

https://www.amazon.co.uk/Elgato-Weather ... B01KHLWAHM

[simon_rb]

Hi all,

My homebridge keeps crashing at night when I turn "The House" off.. Using MQTT branch.

Cheers

Code: Select all

pi@raspberrypi:~$ sudo systemctl status homebridge -l
● homebridge.service - HomeBridge Service
   Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
   Active: failed (Result: exit-code) since Thu 2016-10-06 23:35:03 BST; 10h ago
  Process: 29054 ExecStart=/usr/bin/homebridge (code=exited, status=1/FAILURE)
 Main PID: 29054 (code=exited, status=1/FAILURE)

Oct 06 23:35:03 raspberrypi homebridge[29054]: Layer Decrypt fail!
Oct 06 23:35:03 raspberrypi homebridge[29054]: Verify Fail
Oct 06 23:35:03 raspberrypi homebridge[29054]: Layer Decrypt fail!
Oct 06 23:35:03 raspberrypi homebridge[29054]: Verify Fail
Oct 06 23:35:03 raspberrypi homebridge[29054]: Layer Decrypt fail!
Oct 06 23:35:03 raspberrypi homebridge[29054]: undefined:1
Oct 06 23:35:03 raspberrypi homebridge[29054]: {"characteristics":[{"aid":2,"iid":12,"ev":true},{"aid":2,"iid":15,"ev":true},{"aid":3,"iid":11,"ev":true},{"aid":3,"iid":14,"ev":true},{"aid":4,"iid":11,"ev":true},{"aid":4,"iid":14,"ev":true},{"aid":5,"iid":11,"ev":true},{"aid":5,"iid":14,"ev":true},{"aid":6,"iid":11,"ev":true},{"aid":6,"iid":14,"ev":true},{"aid":7,"iid":11,"ev":true},{"aid":7,"iid":14,"ev":true},{"aid":8,"iid":11,"ev":true},{"aid":8,"iid":14,"ev":true},{"aid":9,"iid":11,"ev":true},{"aid":9,"iid":14,"ev":true},{"aid":10,"iid":11,"ev":true},{"aid":10,"iid":14,"ev":true},{"aid":11,"iid":11,"ev":true},{"aid":11,"iid":14,"ev":true},{"aid":12,"iid":11,"ev":true},{"aid":12,"iid":14,"ev":true},{"aid":13,"iid":13,"ev":true},{"aid":13,"iid":16,"ev":true},{"aid":14,"iid":11,"ev":true},{"aid":14,"iid":14,"ev":true},{"aid":15,"iid":12,"ev":true},{"aid":15,"iid":15,"ev":true},{"aid":16,"iid":11,"ev":true},{"aid":16,"iid":14,"ev":t
Oct 06 23:35:03 raspberrypi homebridge[29054]: SyntaxError: Unexpected token
Oct 06 23:35:03 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Oct 06 23:35:03 raspberrypi systemd[1]: Unit homebridge.service entered failed state.

[TheRamon]

How can I update to the new branch ?

I have used the NPM install to get started.

Or should I wait for the NPM version to be updated with all the new goodies such as webcam support...

Yeah, I guess npm version will be updated soon! Hang on tight.

Hi all,

My homebridge keeps crashing at night when I turn "The House" off.. Using MQTT branch.

Cheers

Oh wow, not quite sure what that is. You're on the MQTT branch, did you update to the latest? The plugin would crash when using dimmers on the last few releases. Other than that, I'm not sure!

[rwijbenga]

Ok, then I will wait a bit longer...

But I now also have the midnight crash:

Code: Select all

homebridge.service - HomeBridge Service
   Loaded: loaded (/lib/systemd/system/homebridge.service; enabled)
   Active: failed (Result: exit-code) since Fri 2016-10-07 05:17:57 CEST; 8h ago
  Process: 817 ExecStart=/usr/bin/homebridge (code=exited, status=1/FAILURE)
 Main PID: 817 (code=exited, status=1/FAILURE)

Oct 07 05:17:57 raspberrypi homebridge[817]: at SaxLtx.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:105:26)
Oct 07 05:17:57 raspberrypi homebridge[817]: at StreamParser.write (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:124:17)
Oct 07 05:17:57 raspberrypi homebridge[817]: at Connection.onData (/usr/local/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:310:17)
Oct 07 05:17:57 raspberrypi homebridge[817]: at emitOne (events.js:101:20)
Oct 07 05:17:57 raspberrypi homebridge[817]: at Socket.emit (events.js:188:7)
Oct 07 05:17:57 raspberrypi homebridge[817]: at readableAddChunk (_stream_readable.js:176:18)
Oct 07 05:17:57 raspberrypi homebridge[817]: at Socket.Readable.push (_stream_readable.js:134:10)
Oct 07 05:17:57 raspberrypi homebridge[817]: at TCP.onread (net.js:543:20)
Oct 07 05:17:57 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE
Oct 07 05:17:57 raspberrypi systemd[1]: Unit homebridge.service entered failed state.

In my case the problems came after upgrading to the latest beta of domoticz. V3.5733

Hope this helps finding a fix....

[simon_rb]

I've not updated to latest beta of domoticz, I'm on the latest stable. I had no issues with dimmers other than it sending an on command then the dimmer value which I know can't be changed. I'll update to latest MQTT branch and see what happens tonight.


Sent from my iPhone using Tapatalk