Notices


Reply
Thread Tools
Posts: 439 | Thanked: 1,194 times | Joined on Feb 2012 @ Germany
#11
Originally Posted by glo-worm View Post
/home/user/MyDocs/maebble-v0.90 # python maebbled.py
Traceback (most recent call last):
File "maebbled.py", line 654, in <module>
dbus_listen()
File "maebbled.py", line 448, in dbus_listen
bus = dbus.SessionBus()
File "/usr/lib/pymodules/python2.5/dbus/_dbus.py", line 219, in __new__
mainloop=mainloop)
File "/usr/lib/pymodules/python2.5/dbus/_dbus.py", line 108, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/pymodules/python2.5/dbus/bus.py", line 125, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException
So what I can say, as somebody who never did something with python, try to comment out line 448 and 449 in the maebbled.py.
Maybe then the rest is working.
On the first sight i guess there is a problem to talk to the session bus or to it's signal "media_changed" from media player.
But at least it tries to talk so the dbus python modul seems to be present.
Maybe the thread creator could give better solutions or explanations to his script.
 

The Following 3 Users Say Thank You to Halftux For This Useful Post:
proprog's Avatar
Posts: 27 | Thanked: 104 times | Joined on Jul 2012
#12
I'm afraid I can't add much to the previous answer. It looks like you cannot get the session bus but the message doesn't say much about why. I'll see what I can find.

If you comment out the two lines as suggested the "now playing" will not be updated but everything else should hopefully work.
 

The Following 3 Users Say Thank You to proprog For This Useful Post:
Posts: 22 | Thanked: 50 times | Joined on Jul 2013 @ Prague
#13
Hi there,

Thanks for the advice. I tried editing out the two lines and when I execute I do no get any errors at all. It appears to just execute.

I tried sending test SMS but got no notification on the pebble.

As I am a noob with python I guess I have reached the limit of my capabilities. So sadly my pebble and N900 will not have the relationship I hoped :-(

Thanks again.
 

The Following 2 Users Say Thank You to glo-worm For This Useful Post:
proprog's Avatar
Posts: 27 | Thanked: 104 times | Joined on Jul 2012
#14
Can you run maebble with parameter --print_maemo for extra logging and post or pm me the output?

If you see a sms notification on your n900 you should get a message on the pebble as well.
 

The Following 2 Users Say Thank You to proprog For This Useful Post:
Posts: 22 | Thanked: 50 times | Joined on Jul 2013 @ Prague
#15
Originally Posted by proprog View Post
Can you run maebble with parameter --print_maemo for extra logging and post or pm me the output?

If you see a sms notification on your n900 you should get a message on the pebble as well.
Here is what it generated

/home/user/MyDocs/Maebble-v0.90 # python maebbled.py --print
_maemo
setup
00:18:33:7D3:74
5
30
True
[]
connect
<bluetooth.bluez.BluetoothSocket instance at 0x296d50>
process
response
1
17
_phone_version_response
_send_message
17
_send_message
response
30
49
response
1
32
_send_message
32
_send_message
response
30
49
response
30
49
timeout: update media status
response
514
6778
response
594
6778
sms from Miles Revell
New sms received
Incoming SMS uses GSM-7 alphabet
Sms from: +420xxxxxx627
Sms content: Testing@
sms message is Testing@
notification_sms
Miles Revell
Testing@
_send_message
3000
_send_message
response
383
6778
response
622
6778
response
30
49
response
30
49
response
2
18
response
2
18
response
30
49
response
30
49
response
30
49
response
30
49
response
3
0
timeout: update media status
response
2
6778

Phone showed SMS notification but nothing on pebble. BT on pebble says connected to N900. BT indicator on N900 is blue. Pebble running V3.12.3 firmware.
 

The Following 2 Users Say Thank You to glo-worm For This Useful Post:
proprog's Avatar
Posts: 27 | Thanked: 104 times | Joined on Jul 2012
#16
Unfortunately maebble is only compatible with older versions of the firmware. My pebble is v1.14.4 and that's the one I've tested. Apologies for the confusion.

When I've added support for email and made it run on startup (both very soon) I'm going to have a look at the changes needed in the protocol. Not even sure it's possible but your test looks promising.
 

The Following 3 Users Say Thank You to proprog For This Useful Post:
Posts: 22 | Thanked: 50 times | Joined on Jul 2013 @ Prague
#17
Ok, thanks for the clarification. I will follow your work here with interest.
 

The Following 2 Users Say Thank You to glo-worm For This Useful Post:
Posts: 14 | Thanked: 9 times | Joined on Jan 2012
#18
What's the status with this project as far as pebble firmware > v1.14.4?

I found a cheap pebble classic and am considering buying it
 

The Following 2 Users Say Thank You to badcloud For This Useful Post:
Posts: 256 | Thanked: 329 times | Joined on Jan 2010 @ NYC
#19
What would it take to get the function that n9 has? Mainly being able to load and control apps from the the n900?

Thanks for sharing and working on this project, what you have already is great. I can see call, not msg yet and slow but working omp stop/play/next/previous. Trying to figure out how to get the song to update. But the worst is having to use an iPhone to update the watch. Or forget to sync the apps then have no app till next iPhone connection ..
 

The Following 2 Users Say Thank You to xman For This Useful Post:
proprog's Avatar
Posts: 27 | Thanked: 104 times | Joined on Jul 2012
#20
I've finally updated maebble to support other firmware versions. Tested with v1 (on pebble classic), v3 (on pebble classic) and v4 (on pebble time).

Download the new version at:
https://www.dropbox.com/s/m5p92uj8ru...v0.91.zip?dl=0

Instructions from first post still apply. New in config-file is that you can specify how often time on watch should be updated (setting is in hour, set to 0 to not update).

New in this update:
- v3 notifications
- email notifications (very basic, just account and number of new emails)
- ping method
- set time method
- get watch version method
- music volume up/down
- new parameter --config_file to use multiple watches (mainly for testing purpose)
- the delay in music control should be much less of a problem now with minor bug fix and changed sleep values

I'll try to add app methods next but don't hold your breath.

Last edited by proprog; 2017-05-22 at 06:59.
 

The Following 7 Users Say Thank You to proprog For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 19:06.