-
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
Installation support needed #8
Comments
Hi There, Thanks for your interest |
Hi I installed the whole system again. But now I struggle with the following problem.
GatewayID.h:89:2: error: ‘BeeeOn::GatewayID::operator uint64_t() const’ cannot be overloaded with ‘BeeeOn::GatewayID::operator long long unsigned int() const’
operator uint64_t() const
^~~~~~~~
GatewayID.h:84:2: note: previous declaration ‘BeeeOn::GatewayID::operator long long unsigned int() const’
operator unsigned long long() const
^~~~~~~~
|
Hi, to solve this error you have to edit file base/src/model/GatewayID.h. In this file comment lines 89-92. I have built the BeeeOn Gateway application on many various platforms but I have never seen this error. Thank you for your report |
Hi,
i quoted 2 lines out and it ran uptown 98%
+
|
|
Was in the output of cmake command written "IQRF support is disabled"? |
I don't know really what's wrong. And this leads to new problemshome/pi/Desktop/Beeeon/gateway-master/src/zwave/OZWNetwork.cpp:910:3: error: ‘CommandClasses’ has not been declared |
For the RPi I would recommend you to enable udev, Belkin Wemo, Vektiva, Bluetooth, Bluetooth Avaibility, Bluetooth Low Energy Smart, Philips Hue, Mosquitto, Testing Center, IQRF and Sonoff. For the ZWave, IQRF and Jablotron you need special dongles. And also for the Bluetooth you need dongle if your RPi does not have Bluetooth module. For the first configuration when the IQRF was disabled I found bug which cause the problem. But if you enable IQRF there should not be any problem. As soon as possible I will fix the bug. Thank you for your observations. |
I try this config now.
|
From this output I do not know what happened. Maybe the easiest way is to delete line 121 from the file src/CMakeLists.txt. |
Removing line 121 solved the prob. |
Could you please so kind to tell me how I can generate the certs? |
Try this config. You also have to disable all services which you disabled in CMakeLists.txt. [application] |
Hi, you can run the software both with or without certificates, depends on your intentions. We are used to identify each gateway by an ID and that ID can be specified directly via this setting:
or from certificate's common name. You can generate certificate by using script tools/gateway-gencert.sh. If you have your certificate authority, you can use it here. Otherwise, you can generate a self-signed certificate (default setting when you do not provide any other options). Steps:
Note that you should edit the lines 1-8 of tools/gateway-gencert.sh for yourself. For testing and playing, no certificates are necessary. |
thanks. BeeeOn::DeviceStatusFetcher 12:19:08.784 8509 [Error] Invalid access: write: Bad file descriptor |
BeeeOn::DIDaemon::UnhandledErrorHandler 11:59:25.411 8314 [Error] Null pointer BeeeOn::DeviceStatusFetcher 12:19:08.784 8509 [Error] Invalid access: write: Bad file descriptor These error messages should not have any big inpact I think. But this message: It looks that the discovering process of devices on Jablotron network found some device but the device is probably not supported by BeeeOn Gateway. |
That are bad news. I brought the Bigclown Radio dongle and thought that is the right one.i can’t find the Turris dongle anywhere. |
Hi guys,merry Christmas.


![Uploading 2C1C47A9-E6EE-4177-848E-B14D2E5EE6A8.jpeg…]()

I tried to install Beeeon on my rasp. Unfortunately I did not managed to finish the installation.
Here my probs
Thanks for your support
The text was updated successfully, but these errors were encountered: