-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Loxone Adapter (IOB) not connect with Miniserver #191
Comments
Can you please provide additional information about your Loxone Miniserver and your ioBroker installation? Version numbers, your configuration (except for the password of course). |
Have any of you done any updates recently? Other adapters or your OS or NodeJS or anything else? |
No, i startet from scratch.
Tried also the raspi image on the iobroker website, but it did not work. |
Hi, no. I have set up my raspi completely newm. No backups implemented. I just downloaded the loxone adapter and tried to get it online, but without success. |
Can any of you please set the adapter to "debug" and then restart it and then post those logs here? |
Ok, here my logs. With Adapter configuration IP-Adress and Hostname. |
Hi! I have the issue. Miniserver gen.2 |
Please, everybody who has the problem: provide all details about your system. It doesn't help at all to tell me that you have the same issue without telling me what's your environment and perhaps how/when the issue occured. Software usually doesn't fail without any changes to the systems involved. |
I installed this on a pi4 the day before yesterday. curl -sLf https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs
curl -sLf https://iobroker.net/install.sh | bash - nodejs had already been deleted this was my first attempt to get it done. without success |
Here an overview about the debug results:
|
Any news on this? I tried different versions of nodejs (12, 14), admin adapter, javascript adapter and loxone adapter, but the SIGBUS issue remains in any combination. |
Unfortunately not. I'm on vacation and have no access to a Raspi right now. I hope this issue is not at all related to the adapter but rather some other software. But for now it seems nobody has found the culprit yet. |
Hi erveryone, i did some testing and got it running with 'ubuntu-20.04.3-preinstalled-server-arm64+raspi.img' as OS for Raspberry. I think it is not a problem of the apapter. PlatformBetriebssystem:linux Hope it helps... |
Adapter Version v2.2.3 PLATFORM: LINUX |
This sounds promising! Thanks for your effort. For everybody else: can you try with an older Raspi OS image? Or with a lower patch version of NodeJS (e.g. 12.22.5)? |
Same with 12.22.5
I don't want to change raspi image because of other installed plugins |
It's funny, i wrote it was working with ubuntu 20.04.3 but today i tried to reproduce it and it now shows the same error. Found that it is working with 64bit only. Maybe it helps. |
because we research a comparable issue in alexa2 adapter ... can you please check dmesg and /var/log/syslog for entries when the SIGBUS error occurs? |
We are starting to see similar issues in another adapter. Can somebody please have a look at their dmesg or /var/log/syslog when the error happens? There should be an exception. Please post it including the surrounding messages. This will also be interesting for @Apollon77 |
Yes, there is an exception:
logged on a Pi4 with debian buster, Node.js: v10.24.1, NPM: 6.14.12, admin 4.2.2, javascript 5.2.13.....did some downgrading, but SIGBUS error still occurs. |
Second case with RPi 4 and such an memory alignment error ... looks more and more like a kernel issue to me |
I installed raspi OS again, here ist the dmesg. I hope it is the information you need. I just started with raspi and iobroker and i'm not familiar with it. If you need more details, no problem.. |
But you didn't install ioBroker, I guess. I can't see any error in your file. |
ok, but it was running and the error showed up in the log. Maybe i did something wrong getting the log. Is there a how to get it? |
Now i think i got a log for you |
We are narrowing down the issue. Is everybody who sees this issue using a Raspberry Pi 4? Please let me know if you use a different device. |
Hi, I'm using Pi 2B+ |
SIGBUS error on a Pi3b and Pi4
… Am 12.10.2021 um 23:20 schrieb Govraemd ***@***.***>:
We are narrowing down the issue.
Is everybody who sees this issue using a Raspberry Pi 4? Please let me know if you use a different device.
Hi, I'm using Pi 2B+
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Good and bad news: we found the underlying issue, but as of right now it is not yet fixed: |
We have a temporary workaround for this issue: |
You might have to uninstall and then reinstall the adapter to get the latest dependency. |
Still have the same problem.. I have reinstalled loxone adapter, still have the same message 'sigbus'
|
What do you mean by "reinstall"? Did you remove the adapter completely or just the instance? |
Yes.. I removed the adapter completely and reinstalled the adapter...
|
Do you have other adapters installed? Some that might also use WebSockets? If yes, please uninstall all adapters and then reinstall one after the other. If no, please uninstall ioBroker.loxone and then have a look at |
There is a folder 'bufferutil' (look at Screenshot) Attached also the Screenshots of the nodes_modules folder
|
Please use your browser or the GitHub app on your Android phone and not emails to respond to this thread. There are no screenshots attached and I have to clean up every message you write as it contains the original message and your signature. |
Everyone is green again and there are no more errors. Now I can start playing around with the miniserver :) THX 👍 |
@Sinus1986 can you please execute |
OK, so please uninstall the adapter again and then execute the command once more. You shouldn't see |
Bufferutil is still there... |
Perfect - now I got it.. Thanks for your help |
Failure: instance system.adapter.loxone.0 terminated due to SIGBUS
Whats the problem?
Can someone help me?
The text was updated successfully, but these errors were encountered: