-
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
Getting z/ip gateway running on Nerves Raspberry Pi 3B+ #567
Comments
@dvic thanks for reaching out! I am glad that you are giving Grizzly a spin! Admittedly, I haven't updated the Unfortunately, the docker container only compiles for 32-bit x86 and not ARM. To target ARM you will need a cross compiler toolchain or you can use the provided If you are using Raspbian then the I can walk you through the steps if you are targeting the Nerves system RPi3. I should probably make a guide anyways, so this will be a good opportunity to do this. As a side note, earlier this year our Z-Wave hub passed the Z-Wave Alliance certification process using Grizzly! I hope once you're able to get |
Ahhh clear!
That would be great! I'm indeed targeting Nerves RPi3. If you could give a rough outline / pointers where to start, I think I can manage from there. When I get it working I can submit a PR outlining the process in detail to get it running on RPi3.
Wow, that's awesome! Congratulations 🥳 |
@dvic I haven't forgotten about this, I just was tied up with some other things. I have the notes just about done, hopefully, I can finish them up here shortly and respond to you. |
No worries! I'm grateful you are willing to help, I can wait :) |
Hey there, just chiming in to say that I'm just getting started with Grizzly too. I got the |
Yes, sorry I have been trying to get notes going but I have run into a snag with the build from the source provided from Silicon Labs. Right now I only have instructions for Linux, so you might have to set up a VM or docker to build. Attached are the work-in-progress instructions. I run into a LibUSB issue when building that I haven't had time to look into when I run I know we apply some patches to You can see some of the patches here (https://github.com/smartrent/grizzly/pull/245/files), but I am not sure how valid they are since they targeted an older version of I really want to get provide a really easy way to compile |
Thanks Matt! This seems like something I can run with and see where I get. I wonder if it's worth while to reach out to Silicon Labs about this workflow or if you've already been in touch with them? |
OK, after a little work, I was able to get past the libusb issues. I created a custom nerves system for which I added libusb and json-c. Now I have a new error:
I think this is where the cross-compilation comes in. However, I'm not really sure how to proceed. If it helps, here are the two lines added to
@mattludwigs Let me know if there's something else you'd recommend trying at this stage. I'll probably keep trying to make progress on this as I have time. |
I went ahead and tried applying the patches, but they seemed to fail as well. I think I'm a little out of my element here:
|
@jasonmj thanks for looking into that more! I am curious, have you pushed your Nerves system yet, just so I can see and maybe test against it once I can jump back into looking at this? In regards to the patches, it would probably be best to ignore those as they are for a really old If you're following the script that was in the PDF one of the CMake flags disables testing: Thank you for testing things out and looking into this, it really helps to get more information. Hopefully, long term there can be an elegant solution to this. |
@mattludwigs Thanks for the reply. I have not pushed my nerves system for the beaglebone yet, but I think I may have time to do that this weekend. I also have an rpi 3, so maybe that would be better to try? (My end goal is to run the controller on the BBB if possible). I did try applying some of the patches manually since the line numbers were wrong on the old patches, but that didn't seem to resolve this error:
Hopefully, I will have a little more time for testing soon. |
Just a quick update to say I've not given up here. Still working through some compilation errors, but making progress (slowly, every now and then). I have everything in a containerized repo that I think I can share, but since it contains the zipgateway source code, I'm not sure if I should? Anyhow, I'll keep at it a little more and hopefully report back again soon. |
OK, I got it to build and now I have a zipgateway binary. I've pushed my work to a private repo. Next, I'll try to integrate this with the hello-home repo load it onto a BeagleBone Black. I'll let you know how it goes! |
Awesome! Thank you for the updates! I did start reworking https://github.com/mattludwigs/zipgateway-env to be more up to date with the current method of getting I really think there is a better way for all this to happen, one of my goals this year is to make compiling Also, this has been a blocker for exploring building something more useful to the greater community using Grizzly. |
Hey @jasonmj sorry for the delay, I was under the weather for a bit last week. Thank you for the update, I might poke around this week as I have time. I could do a quick check-in on this if you're still willing. |
@mattludwigs sorry to year you were feeling under the weather. Hope you’re enjoying n the mend now. I’m back from a week off myself and working to catch up. I think I could fit in a chat toward the end of this week or more easily, most times next week. I’m on eastern time and could check in either during the workday or afterwards. Feel free to reach out over email to continue the convo: jason@fullsteamlabs.com. Oh and! I’d be happy to share you on the private repo I used for compiling the zipgateway. It’s intended to work with the beagle bone black, but I think it would be pretty easy to swap that out for another nerves target. |
Hi!
First of all, let me start by thanking you (and SmartRent) for this wonderful library 👍 It look really promising 🙂
I'm trying to get the z/ip gateway running on my Raspberry Pi but I'm getting the following errors:
I'm on Mac and I compiled the sdk using zipgateway-env but I had to modify the dockerfile to get it to compile:
I was struggling first to get the source code from 'Simplicity Studio 5' but I eventually found it (for reference: on mac it's in
/Applications/Simplicity Studio.app/Contents/Eclipse/developer/sdks/zwave/zip_gateway/v7.16.1/Source
.After the compile step was succesfully completed i took the binary from the zipgateway-env folder
![image](https://user-images.githubusercontent.com/1214337/140815305-a6214b1b-2527-4e96-a0cc-f74530da8e08.png)
zipgateway-source/7.16.01/usr/local/build/src
, because I forgot to add the new version incompile.sh
:Then I added the binary to
rootfs_overlay/usr/sbin
and after burning the firmware to the SD-card, I ran:It seems that
zipgateway
is giving an exit 2, any idea where I can start to dig into this further :)? Is this is recommended way to get a properly compile binary for RP3?The text was updated successfully, but these errors were encountered: