Directing the Berg cloud bridge #8
100 participants
and others
Is there any where I can find out how to do this? as remote.bergcloud.com is down at the moment.
I would love to know how to get the new firmware. I don't care if I brick the bridge since I'll be tossing it if I can't revive it.
An update would be nice. I'm a programmer so just knowing the first steps would be nice.
Ok, my intention was to roll out the new Bridge software to everyone... but I'm having trouble understanding how to get the Bridge update servers to do a bulk update. I'll be able to figure it out, it'll just take me some more time.
But I want you all to be able to use this ahead of me figuring that out. So I can manually get you the software if I can get the MAC address of your Bridge.
There are instructions to find the MAC address on the old troubleshooting page -- go down to the header "I’ve plugged in the Bridge, and the ethernet light is flashing constantly" and there are instructions about using software called Bonjour Browser and some alternatives. Get the MAC address and let me know. (Here? Or does github have a private message function? I don't know tbh)
After I've added your MAC address to the update servers, the process is:
- Power cycle the Bridge, and wait some minutes for the update to run. Cross fingers it doesn't get bricked
- Use Bonjour Browser (or equiv) to find the local IP of your Bridge
- Go to the URL (local IP):81/configure
From there you're dropped into step 2 of the Updating the Bridge instructions.
you can then either point your Bridge at my alpha server, or download the code and install it on your own server.
Thank you, not just letting this hardware die is good of you. MAC: [40:d8:55:19:79:57]
@sfcgeorge have flagged that MAC address for an update -- this is the first time I've used this particular bit of the system, so I hope it works!
It worked! I got to the /configure page, logged in as per updating the bridge instructions on the wiki. Changing then endpoint isn't working for me, it keeps going back to berg. But remote and bergcloud seem to be working so that's nice for now.
Hi Matt, can you add in my mac address please: 40:d8:55:01:cd:fd
This is the first time I've plugged my little printer in for a few months, and I'm no longer getting the 'upstream' light turn on (all others are solid white). Is this because the Bergcloud services are finally turned off or do I have another issue?
Thanks for your hard work keeping this going!
@simonpfry Bridge flagged for update. The old servers are up and down now... not entirely sure why they seem to work for some people and not for others
Yay, it works, thanks! :) Note: The server URL change didn't seem to want to save until I power cycled the bridge one more time.
Would appreciate mine done as well: 40:D8:55:01:C3:40
Anything we can do to help automate this right now?
@interlock done!
tbh I'm happy doing this manually right now, it's nice to have a little contact with folks giving this a go! Going to tackle the automation question after the next focus (which is to pretty up alpha and add a couple of mini features). I say focus like this is a big deal, it's all background work for me still I'm afraid
I think you should also post a link to this thread on LP blog so other enthusiastic power users are aware we're already doing the updates :)
Many thanks @genmon - all working locally, think there may be a db glitch at the moment with alpha.littleprinter as it's giving Internal Server Error when I try to sign in. Thanks for continuing to support this!
Hi Matt,
I finally got some spare time to get our Little Printer up and running again, seems like I made a typo with my original mac address request 
. Could you add this one please:
40:d8:55:01:ce:22
Thanks again!
Kevin
Hello. here's my numbers and gubbins if you could add it, thanking you muchly.
40:d8:55:01
73
limits of understanding truly exceeded :D
... oh I actually have the letters C and D not a cd in the middle of my MAC address.
4 0 : d 8 : 5 5 : 01 : c d : 73
Thanks. Just went to power cycle the bridge and saw the MAC address is printed on the underside... that makes the first step easier. oops. Silly me.
I'm getting an 'Internal Server Error' when i try to log in alpha.littleprinter.com.
All other steps completed successfully though!
Update: Persisted to try logging in and eventually it happened! Got the thing working. Horay. We're back.
Is there any details on character limit and such?
Can you add my printer's address to the list?
40:d8:55:19:77:b7
This is how I retrieved the address:
Find the bridge
dns-sd -B _ssh | grep bridge
17:19:12.829 Add 2 10 local. _ssh._tcp. berg-cloud-bridge-p9tsns3hz
Get the ip (add ".local" to the name)
ping berg-cloud-bridge-p9tsns3hz.local
PING berg-cloud-bridge-p9tsns3hz.local (192.168.11.56): 56 data bytes
64 bytes from 192.168.11.56: icmp_seq=0 ttl=64 time=0.864 ms
Get the MAC address
arp -an | grep "11.56"
? (192.168.11.56) at 40:d8:55:19:77:b7 on en4 ifscope [ethernet]
Happy Sunday @genmon!
Mind adding mine as well? 40:D8:55:01:CC:81 Thank you!
Cheers,
David
@davidneudorfer done!
@booyaa looks like there's a typo in the MAC address.. should be another character in that "1" segment?
quick note -- I'm still on my hols and unlikely to be able to see this thread again (or action bridge updates) until 28 sept. sorry for the delay!
Guys, as @jimlockey noted, the MAC address is also on the label on the bottom side of the bridge :)
Hi @genmon I have got my Berg bridges out, I appear to have 3 (one was from the dev kit for berg cloud i think). I know I only need the one and can connect the two computers too it, but if you could add them all then I can maybe take one over to other family houses. Anyway the mac addresses:
MAC addresses of BERG Bridges
1. berg-cloud-bridge-p9tsmusc8 [40:d8:55:01:c0:f8]
2. berg-cloud-bridge-p9tsmusab [40:d8:55:01:c0:b3]
3. berg-cloud-bridge-p9tsmuuwg [40:d8:55:01f0]
Cheers!
Mark
Perfect, it is working, printing and a bit of awesomeness is back! :) Is there any way to join and improve even more?
Hi @genmon. I just found out about this yesterday. I have a couple of Little Printers that I'd love to see working again! Would you please add these two mac addresses?
- 40:d8:55:01:c7:93
- 40:d8:55:01:c5:e7
Thanks in advance :)
@genmon I think you should also post a link to this thread on LP blog so other enthusiastic power users are aware we're already doing the updates :)
Hi @genmon
Seems like the label had faded slightly on the bridge. My MAC address is: 40:D6:55:19:78:28
@dan-harding done
@designerscartel done
@kpeeem done
@chepeme done
Sorry for the delay all! Busy this end. Yes @markostamcar I agree -- will add to my todo :)
Hi the url where I'm supposed to learn how to get my MAC address doesn't work anymore. How to get the bridge MAC address?
Edit: the MAC address is written on the lower right corner of the sticker underneath the Bridge itself.
You can find the mac address underneath your bridge or written on the back of the bridge.
Hi @ibftp -- it looks like you already have the latest version of the Bridge software.
So now your process is to follow the instructions in this comment to get the latest software, reach the configuration page, and re-point the Bridge at different backend software.
I'm very confused... I went until I type my bridge IP:81/configure address then I'm required login and password. What do we type here?
I logged in and get this:
http://vincent.polenordstudio.fr/snap/cd7jx.jpg
I am sorry, I don't understand any of what is said on the page. Not a line. I don't know where I'm going, I don't know if the bridge being disconnected means anything bad; I don't know why I would whose https instead of http...etc.
@ibftp ok looks like the alpha server isn't working today, sorry. the main route is to install the code (the same code that the alpha server runs) on your own server, there are details in the readme on the front page of this repository. some people in this thread above have got the code running on raspberry pis.
it's all pretty technical and i'm afraid it's not going to get much simpler soon -- this is really so tech folks can build their own replacement Little Printer servers
Ok thanks for your help. I guess I'm back into LP frustration :) I had wanted so much to build dozens of publications for it, I had all the content, and have been digging into the docs numerous time without being able to do anything. This is a bit like it :)
Could you explain what happens on /configure for when the alpha server runs again or if I get someone to install my own server?
@rmckenzi if the lights on your Bridge are flashing (all of them, up and down), leave it for a few minutes, that's the update happening. If they aren't flashing, you can trigger the update by unplugging the Bridge, waiting 30 seconds, and plugging it back in again. The update will take a couple minutes. I've updated the instructions to say this too
Yeah - it works! Little Printer is alive! And HTML is working - so it is possible to print some pictures, bigger fonts...
But: How do people send messages to my little printer? Is it possible trough their own twitter-account? Is there a hashtag or something..? Thanks a lot...
@chwode this is all explained once you sign in on alpha.littleprinter.com -- your friends can sign in on that site, and then they can send messages to your printer (only if you follow them on Twitter). but a quick warning: alpha.littleprinter.com is a demo site only, and will mostly not be functioning at all. the intended use is for you to install this sirius code on your own back-end server, claim your printer on that server, and have your friends sign in and send you messages from there.
Hi Matt, I know it's almost Christmas but if you're online it would be great if you could add the mac address of my little printer: 40:D8:55:01:CC:12 You're doing a fantastic job getting everyone back online with their little printers - it's great. I bought one for my parents which they absolutely love and I intend to get the github code working on my server over Christmas so I can get it back up and running for them! cheers Owain
[40:d8:55:01:c0:3c]
And me too, thanks a lot for bringing "him" back. Berg cloud seems gone for good two days ago.
M.
I'm getting nothing but "internal error" when I access alpha.littleprinter.com .. are there issues there or am I missing something?
Hello, thank you for saving the lifes of our little printers! ¨
Here is my MAC-Address: 40-D8-55-19-71-CE
thank you very much!
And a little Question to all the users: Is there someone who is selling these Paperrolls?
Hello! Thank you for helping many of us out with keeping our units breathing.
Please add the following MAC address
[40:d8:55:01:c3:bb]
bridge updates queued up @owainrich @Patrickh60 @mjbrej @gsm-com @pixelwiese @arnoldsuperstar @t8ert0t @futureshape -- sorry for the delay over the holidays!
re alpha.littleprinter.com -- this is really just a demo site for this code. what I hope folks withl do with the code is run it on their own server! alpha.littleprinter.com points at a server I run personally for hobby projects, and it's often not running properly.
cc @rmckenzi since you asked
@genmon thanks! update worked on my side but as you said alpha.littleprinter.com is flakey ... are there any instructions/hints/requirements around installing it on my own server?
@msmabry @pattan @jorishuizinga @nicocentre -- done!
@futureshape in terms of installation tips, it's worth reading through README.md and notes/dokku.md in the main repo. but also other folks here might have had good luck... have a look through the thread and see who has got installs working. maybe they'll chip in :)
@genmon Could you please add MAC address 40:d8:55:01:c3:98? Thank you so much!
Hi there, can you please add MAC address 40-D8-55-01-C6-D6.
Was about to throw this out and made one last check. Glad I did.
Thanks
Dave
Wow that was quick - Thanks!
Got the Bridge redirected to Alpha.littleprinter.com OK but when I sign in with twitter and it tries to redirect back to the alpha site I get an internal server error.
I'll try again later.
Cheers
Dave
@drconline hi, this is a problem most of us have. But there is to say that alpha.littleprinter.com is just a small server hosted at his home for hobby projects. So the main idea is to set up your own server and direct your bridge to this address.
Scroll up some messages to see the comment from matt for this topic.
@genmon We're already a little into the new year, but... Happy New Year! :-)
May I ask you to also please add mine 40:d8:55:19:71:cf? THX a ton!
Hello - please can you add me as well - hoping to get the Little Printer back up and running. Thank you. 40:d8:55:01:cb:90
Heyy... I'm desperately hoping for my little printer's resurrection
here's my bridge's mac address: 40:d8:55:012b
THX
Hi @genmon
Our Little Printer for Business seems to have stopped working over the holidays. I can't reach remote.bergcloud.com, so that's probably why.
We still use it at work every day, so I'm really keen on getting it working again.
Here's its MAC address: 00:f7:6f:6f:55:30
Once that's done, I'll try to get Sirius running on our servers, so it can remain working forever ;)
Thanks!
Hi @genmon please add my MAC address: [40:d8:55:01:cb:33]
Thanks so much!
Hi @genmon
Can you add MAC address 40:d8:55:19:71:03
Thanks so much!
Thanks for this project!
Hi @genmon, would love to bring our little back to live. So if you could ad the MAC address [40:d8:55:01:c3:3c], I will be very happy.
Thanks!
Hi @genmon, and thanks so much for continuing to invest time to help us with our Little Printers. :-)
My MAC address is: 40:D8:55:01:CC:58
However, I'm concerned that there might be something wrong with my Bridge because it stopped connecting Upstream some months ago, even before I believe the Bergcloud servers were turned off. (I only have the Power, Ethernet, and Downstream lights.)
So if getting the update depends on the Bridge trying to connect to the old servers when it's booting up, then I might be out of luck. But I guess it's worth a shot; I'll let you know what happens after you've had a chance to queue it up for me. Thanks!
I'm going to look into setting up a server for as soon as mine gets updated. See how much a DO droplet would cost to run this for a bit, I'll post it here if I can get one set up.
Hello fellow little printer keepers :)
Ok, so I think the bridge reset worked, but when i try to run sirius on a local raspberry pi it gives an internal server error when trying to print? Any ideas why? I have some time this week to try and collate a 'how to get things running' and can even try and set up a server for people to use?
cheers people!
just queued the updates for @amcewen @driesderoeck @semanticdreamer @littlestanley @morozmatik @drueben @jmb4u @ajarink @chrisjelley @patrickngscription @kuiche @relainworld @braucci @PieterDiepenmaat @narururu @johndietrich @krigedi @lanzwerk -- should be done now
@johndietrich the bergcloud servers were up and down for most of last year -- the original intention was to turn them off in May 2015 but I was trying to keep them running. turns out that they were running ok for about half the little printers, but not working at all for the other half. the final shutoff was in December
@ketz I can't find that MAC address in the update server. that might be because the business printers ran through a different set of code -- I don't know the technicals ins-and-outs. but while I managed to get this little printer backend code done, it's possible that the business printers won't be supported
Thanks @genmon not sure this worked for me. Can't seem to access the configure page....perhaps the bridge is bricked...
Hi @genmon Thanks for adding my MAC address. I worked through all the actions and am now trying to claim my printer though the code it has created. So, the hub is updated, working and it is connected to the right server. Reset of Little Printer also worked out and I got the claim-code. However: the alpha website says "Internal Server Error".
Anything I can do to make that work?
hi @hako Could you please tell us how? There are a lot of People that don't know what to do with this piece of code.
You would help a lot of People!
Please post it in this issue, for a little bit better overview: #15
Me and I think a lot of others would really be happy if you could do that!
Thanks Karl
@hako Thanks for the tip, but I am not much of DIY-er when it comes to this... I can see that the alpha site is creating the app registration on my Twitter account, but then it goes into the error message afterwards. As mentioned on Matt's guide, the alpha site might be on or off, so maybe it is a process of trial and error.
@pixelwiese : I don't know either, but apparently @hako has an idea ;-). If there is a manual of some sort, I could also do that on the Apple Server I have running.
So... @hako ....no pressure.....but....help!!!!
Thanks @genmon the update did work for me! The little one just talked to me... :-)
@ajarink I have published a DIY guide here
sirius.extrovert.io by @kuiche is also a good alternative to alpha.littleprinter.com
Hello @genmon,
Please add my Adress as well: 40:D8:55:01:C4:B2.
Thank you for this project.
@kuiche Just curious if your instance of the server is running on a private server or if you in fact got it up and running on a DO droplet or other public-cloud hosting? Would be happy to kick in some $$ toward getting a permanent instance on DO or AWS or wherever.
At the moment extrovert.io server gives me an internal server error like alpha.littleprinter.com
@kuiche @johndietrich
i, too, would be happy to kick in a few $ to help fund a permanent cloud instance...
For what it's worth, I'm investigating how easy it might be to write a bit of middleware that can sit between the Bridge and http://printer.exciting.io
How do I see, if the Software is now updated? Power and Ethernet are light up and the Downstream is blinking. When i put my IP with :81/configure in my Browser nothing happens. What did I wrong?
I've already unplugged the bridge und put it back on.
@johndietrich it's a DO droplet. It's setup using Dokku, so if it's erroring like @pixelwiese is saying then it may be because it's only on the smallest DO droplet. It says here that there may be problems with docker running out of memory. I'll see if there are any errors in the logs.
I will look into upping the memory on the droplet (once I get my little printer actually working). If I do I'll try and just stick a donate button or something on there and see how it goes.
@ajarink @pixelwiese I've just restarted extrovert, looks like that has fixed it. Kinda annoying that that happens. @genmon would I be correct in assuming this is due to docker not freeing memory?
@hako Thank you very much for the guide, i got the server running on an Ubuntu Laptop! With your guide it was very easy :)
@kuiche @genmon Well, success at getting the Bridge updated, so it wasn't in fact bricked as I had feared. Can successfully point to new servers now and the settings stick. However it looks like neither sirius.extrovert.io nor alpha.littleprinter.com are working at present since I can't get the Twitter authentication bit to work so I can claim the printer.
I do I have Raspberry Pi sitting around that I could use, although I'm afraid I don't have the Linux know-how to figure out how to take the code here and get it running on the Pi. If anyone has a good step-by-step guide they want to share, that would be super helpful. :) (I know there are some "tips" on getting it running on the Pi in some of the other threads here, but I think I'm still missing some of the necessary knowledge.)
@johndietrich I've done a guide here, #8 (comment) It can be done on the Pi. (Note that this is for OSX and Linux)
If you're on Windows, I could try getting sirius to run on Windows and documenting it in the guide.
@kuiche That did the trick, thanks. Nice to see the little guy still works after all these months. :)
Hi Matt, could you add mine as well:
40-D8-55-19-7A-26
Thank you very much for keeping these friendly little things alive.
Found your notification not before now
Got two little guys
40:D8:55:01:C4:FD
40:D8:55:19:75:53
Also have a server with spare space, and capacity, happy to use that for anything needed?
Dave
Hi guys, I've got the server up and running on my mac using @hako 's brilliant guide. Everything works and I've been able to message the printer. If anyone wants to try using the server, the address is owaindisk.no-ip.org:5000 Will be interesting to see if I get the docker memory problem. I'm going to leave it running with the aim of moving it to a raspberry pi which I can leave on all the time. Brilliant work by @genmon - Little Printer once again lives!
@owainrich if you used @hako's guide, then you probably won't have the issue as I believe it doesn't use dokku. Which is what uses docker :)
@kuiche thanks man - that's useful to know - I didn't realise that. I'll be watching how things go with the stability of the server. I can see a couple of people's bridges connected to owaindisk.no-ip.org and anyone is welcome to direct their bridges over here - I'll be keeping the server on. I'm not much of a programmer but I've been tweaking the code to increase the font size of messages and have changed the face of my printer to a custom graphic using @genmon 's admin code. Would love integration with @lazyatom printer project.
Hi Matt,
that sounds terrific, could you please add my MAC: 40:d8:55:01:ca:49
Thanks!
hi folks -- updates done: @gsellator @dllightman @Landry76 @nixnombre @littleprinter
@dspalton -- the second address says the update is already queued up but the Bridge hasn't been online since March last year?
@vjaitly -- this is the same MAC address as given by landry76, you should have a different one?
@mvk2010 -- there's a missing character in this, ":1:" should be two characters
Hi @genmon could you process my MAC address please it is 40:D8:55:01:C7:8B
Thanks.
Hi @genmon Thanks for this, I was worried about my little printer to be forever obsolete but after a quick dig I found this repo, I hope I can get everything running.
My MAC is [40:d8:55:01:cd:35]
BTW, I used the bonjour browser to find it but as @chepeme pointed up, the MAC is written on the back of the bridge
@kuiche @owainrich Just wondering if anyone has a server up and running currently? Extrovert still seems to require resetting, and Owaindisk seems to be unreachable lately (although the no.IP DNS may have just gotten out of sync).
I'd love to get this up and running on my Raspberry Pi but I haven't had much luck with the guides because mine is running NOOBS and I think that creates some complications in terms of the configs being different from Debian or whatever.
It might be a bit off-topic, but if anyone here is interested in buying the whole set (printer+bridge+3 paper rolls+cables), let me know...
Hey, hopefully I understood well!
my MAC address is [40:d8:55:01:cb:98]. Thanks a bunch!!
@genmon thanks for undertaking this project, Matt.
Please queue up [40-D8-55-01-C7-15]
Hey @genmon,
Hope you see this. I'm not techie at all, but the red light is making me sad and I reckon if I can get this going it might help others.
MAC address to add: 40:d8:55:01:c1:3e
Others in this thread. I'm looking to run this on a Pi, so if anyone has good instructions then let me know - either here or via Twitter @purplesime
I've had my LP since the first batch went on sale. Two months without it and want it back!
Thanks!
Hey, my Mac address is 40:d8:55:01:c0:f3
Hoping to get this back up and running soon :)
Cheers
Hi @mvk2010 @mguth @dalecousins @pablonoel @stantonsteward @tomwagner @alfo @Matteosmth @jonhickman @valeksenko @jensbraun @purplesime @jonathanrelf @schafferhans -- your Bridge updates are queued up
I've also rebooted alpha.littleprinter.com so that should run for a few days before whatever memory leak that takes it down, takes it down again
Sorry for the delay -- real life is giving me a very busy few months so I'm not able to check in here as much as I'd like.
Well, I've got to the point where I have a registration code (which is something to celebrate!)
Seems the instructions made sense, with some trial and error.
Now getting internal server errors, so guessing 3 days is the time it takes for the memory leak to take the alpha site down :)
Now, can this non-technical chap get code installed on a Pi? That remains to be seen, but will give it go in a week or so.
@genmon
Hey mate,
Ty for your awesome support.
please update my lil buddy
40:d8:55:19:72:e0
cheers
D
@genmon here is my MAC Address to update:
40:D8:55:19:71:D5
also, am getting an 'Internal Server Error' during Authentication process on http://alpha.littleprinter.com/
Thanks
My own experience...
After getting my LP updated with the new firmware as per here, and here, I realized that the "http://alpha.littleprinter.com/" site was not going to be (or was ever advertised to be) reliable.
So I bought a cheap-ass-piece-o-crap-ubuntu-linux-laptop on ebay and followed @hako's most excellent directions for installing the server on it and managed to get all pieces running and to talking to each other through persistent googling and dumb luck. [I'm almost 60 and could code once upon a time, but that time has long passed, and I've treated the whole process as looking at a book of incomprehensible magic spells where I've blown up more things than I've gotten to work. LittlePrintiarmus!!]
(I also found this posted by @markostamcar to be incredibly useful.)
The Twitter login crap is just a quick-and-dirty way of using the Twitter API to deal with login credentials for access to a LP. Once logged into the LP server, you're not using tweets in any way, shape, or form to interact with the printer. Ugly, but workable.
As someone with only vague, archaic coding skills, as well as a full-time non-tech job, I'd love to have some guidance on how I might change the server code to use a userid/pw system rather than the TwitterCrap, and how to add the capability to insert an image into a message.
BTW, you might wonder why I have such an affinity for Little Printer. I'm a nursery school teacher (children ages 3-5 years). For the past couple of years, I've used the LP direct messaging capability in my classroom as a way for parents, siblings, extended family, pets(!), etc. to send msgs to the children in my classroom. Both families and children have very much appreciated a way to connect electronically while away from each other, but in a concrete, tangible format that the children often carry with them throughout their day. The most appreciative families are the ones who have mums and dads who travel a lot for their jobs - the LP connection has been profound for them. So, a belated thank you from all of my classroom community, Matt.
Best, Mark
@genmon plugged in my bridge and confirmed the MAC address is correct but the bridge isn't updating/flashing lights after multiple power cycles, verified by port 80 not being open. Anyone have an idea of why or what I can do to fix?
Many thanks @genmon.
@davidneudorfer did you try login to the control panel regardless of if you think the update happened? I blinked and missed the light show on mine.
thanks @jonhickman, I used fing to find the IP address of the Bridge and tried to connect on port 81 but had no luck. Hoping I don't have to go the route of setting up a proxy to see what the Bridge is doing.
@genmon after many reboots the Bridge just sits there mocking me ;) with a blinking ethernet light. Does this mean its bricked? If so, are there any alternative interfaces to communicate with the Little Printer?
Hi @genmon,
Could you kindly help bring my Little Printer back to life?
MAC address: [40:d8:55:014c]
Thanks in advance!
P.S. Obviously that weird emoticon in my address actually means "cd"... thanks Github, for being weird.
@kpeeem what is this bridge dump? I'd love to learn more and possibly revive my Little Printer.
Well, finally today I got a Pi to try this out. Having some issues (I am NOT a technical person at all). Managed to get about halfway, and now stuck at Step 3 of @hako's guide.
Error says Profile does not exist.
Have successfully completed all steps up until I start Honcho/Foreman (I have installed both)
Will keep trying, but any help appreciated :)
@hako - I have worked out a bit more. Starting honcho I get this output:
21:17:14 web.1 | Error: class uri 'flask_sockets.worker' invalid or not found:
21:17:14 web.1 |
21:17:14 web.1 | [Traceback (most recent call last):
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/gunicorn/util.py", line 139, in load_class
21:17:14 web.1 | mod = import_module('.'.join(components))
21:17:14 web.1 | File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
21:17:14 web.1 | import(name)
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/flask_sockets.py", line 15, in
21:17:14 web.1 | from geventwebsocket.gunicorn.workers import GeventWebSocketWorker as Worker
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/geventwebsocket/init.py", line 18, in
21:17:14 web.1 | from .server import WebSocketServer
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/geventwebsocket/server.py", line 1, in
21:17:14 web.1 | from gevent.pywsgi import WSGIServer
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/gevent/pywsgi.py", line 12, in
21:17:14 web.1 | from gevent import socket
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/gevent/socket.py", line 659, in
21:17:14 web.1 | from gevent.ssl import sslwrap_simple as ssl, SSLError as sslerror, SSLSocket as SSLType
21:17:14 web.1 | File "/usr/local/lib/python2.7/dist-packages/gevent/ssl.py", line 386, in
21:17:14 web.1 | def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None):
21:17:14 web.1 | NameError: name 'PROTOCOL_SSLv3' is not defined
21:17:14 web.1 | ]
21:17:14 web.1 |
21:17:14 system | web.1 stopped (rc=1)
Please bear in mind that I'm not technical, but I am willing :)
@hako Output is:
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
load_entry_point('pip==1.5.6', 'console_scripts', 'pip')()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 356, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2476, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2190, in load
['name'])
File "/usr/lib/python2.7/dist-packages/pip/init.py", line 74, in
from pip.vcs import git, mercurial, subversion, bazaar # noqa
File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9, in
from pip.download import path_to_url
File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in
from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead
Try reinstalling pip again. sudo apt-get -y remove python-pip && sudo easy_install -U pip
Thanks @hako I appear to have got to Step 5! I'll pick up the remaining pieces tomorrow. Thanks for all your help.
Other non-tech types might also find this link useful: https://github.com/beyondio/LittlePrinterPi
Short-lived success! My LP Bridge constantly falls over. Even powering it down isn't working now. Anyone else noticed this?
Bridge just went to flashing Downstream light and no upstream light about an hour after I got things going this morning. I haven't looked into any of the code as I assumed it is a hardware fail.
Here they are. It's a long list!
14:20:57 web.1 | DEBUG:sirius.protocol.protocol_loop:Received EncryptionKeyRequired(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e', hardware_xor=6131745).
14:20:58 web.1 | INFO:sirius.protocol.protocol_loop:Initialized next_command_id as 14
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received BridgeLog(bridge_address=u'000d6f0001b307b0', records=[{u'name': u'cloud.socket', u'created': 1459779579.211718, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779584.374403, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779589.52939, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779594.683998, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779599.836807, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779604.988969, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779610.138776, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779615.278443, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779620.4187088, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779625.564481, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779630.714238, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779635.8640127, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779641.01686, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779646.1669512, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}, {u'name': u'cloud.socket', u'created': 1459779651.317886, u'process': 462, u'levelno': 40, u'processName': u'MainProcess', u'message': u'Socket connection refused', u'levelname': u'ERROR'}]).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received EncryptionKeyRequired(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e', hardware_xor=6131745).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received EncryptionKeyRequired(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e', hardware_xor=6131745).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received BridgeCommandResponse(bridge_address=u'000d6f0001b307b0', command_id=15, return_code=0, timestamp=1459779658.376762).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Got BridgeCommandResponse, ignoring.
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received BridgeCommandResponse(bridge_address=u'000d6f0001b307b0', command_id=16, return_code=0, timestamp=1459779658.5062523).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Got BridgeCommandResponse, ignoring.
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Received BridgeCommandResponse(bridge_address=u'000d6f0001b307b0', command_id=17, return_code=0, timestamp=1459779658.648851).
14:20:58 web.1 | DEBUG:sirius.protocol.protocol_loop:Got BridgeCommandResponse, ignoring.
14:20:59 web.1 | DEBUG:sirius.protocol.protocol_loop:Received EncryptionKeyRequired(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e', hardware_xor=6131745).
14:20:59 web.1 | DEBUG:sirius.protocol.protocol_loop:Received DeviceDidPowerOn(device_address=u'000d6f00015d9c4e', device_type=3, firmware_build_version='\x00\x00J\x00\x00\x00\x00\x00\x00\x00v0.5-12-g26e82f0\x00\x00\x00\x00\x00\x00', loader_build_version='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00v0.5-0-g14859cb\x00\x00\x00\x00\x00\x00\x00', protocol_version=0, reset_description=0).
14:21:00 web.1 | DEBUG:sirius.protocol.protocol_loop:Received DeviceConnect(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e').
14:21:00 web.1 | DEBUG:sirius.protocol.protocol_loop:Received BridgeCommandResponse(bridge_address=u'000d6f0001b307b0', command_id=18, return_code=0, timestamp=1459779660.158957).
14:21:00 web.1 | DEBUG:sirius.protocol.protocol_loop:Got BridgeCommandResponse, ignoring.
Now repeating this:
DEBUG:sirius.protocol.protocol_loop:Received DeviceHeartbeat(bridge_address=u'000d6f0001b307b0', device_address=u'000d6f00015d9c4e', uptime=(1,)).
In
README.mdit says "First point your bridge at your laptop". How does one do this?Cheers.