My experience with the Mark II

Funny to see how neon seems to be doing more customer support than mycroft themselves :thinking:
Noticed that on the subreddit as well

Is neon ai just a fork of mycroft core?
If so, classic or dinkum?
Do all skills work?
How about mimic support?
Does it handle processing locally?
Can the device be managed via web interface? (as with mycroft currently)

Did I understand that correctly that homeassistant is not yet working on neon? Because that was pretty much one of the main reasons for me to get a mycroft

I’ve looked at your website but it feels a bit overloaded with information left and right

I found this comparison and concluded that neon seems to be better choice than ovos

Lots of questions, I know - maybe some of them will be resolved if I get to play around with the image in case I find the time for it later
Thanks!

3 Likes

Getting Spotify working is at the top of my list too. It was the first thing I tried to do when my Mark 2 arrived.

I’ve managed to port the hello world skill to my Mark 2 but at this stage anything more is beyond me. I’m eager to learn how to do more but it’s not at all clear what the best way to do that is.

As I understand it from some previous posts, it was Spotify who changed their policy of an Open API (as did Pandora), seemingly so they can control voice input to drive their platform(s).

But again, this is just as I understand it.

Hope this helps.

-Mike Mac
1 Like

The buildroot OpenVoiceOS image somes with Spotifyd pre-installed, which allow you to use it as Spotify device to stream to from Spotify.

However for controlling Spotify via voice you still need the Spotify skill from Forslund;

It can be configured manually utilizing your own API key, however I am not sure if the skill works as expected under OpenVoiceOS OCP as I have not ran that skill for ages.

1 Like

I’m planning on trying out Neon on my Mark II in the coming weeks.

1 Like

Unfortunately, I’m only a novice in Python. I work in IT on the data side but my skills lie mostly in sql and project management/scrum master.

I keep hearing this but the thing is, I build raspberry pi streamer computers using DACs and screens and every one of the OSes I use for this have a place or a plugin where I can connect to Spotify natively(Not through Spotify Connect though that is usually also an option). HiFiberry has it albeit a but clunky as does Volumio. It has been a while but I believe Balena’s solution also has it.

The Mycroft team is remaining silent on this. About all you can get out of them is some direction on flashing classic core. I am guessing the tactic is to avoid any legal dust ups but that is just a guess.

I filed an FTC complaint as this is a bait & switch tactic - illegal in the US and many other countries. More people need to file complaints if they feel they have been sold a different product from what was described at time of purchase.

To file an FTC complaint, you can go here. It takes less than 5 minutes to do and will go a long way in forcing Mycroft to either make good on the product promised or offer a refund.

1 Like

Hifiberry and Volumio both use the same Spotifyd / Raspotify underneath as what I was talking about.

As showcase;

Or

Showcase of the MPRIS open standard included within

1 Like

I’m from the EU so the ftc won’t do much for me

I’ll likely Flash classic core as neon ai seems to be a bit slow when it comes to understanding and then outputting audio

I still hope that they get their stuff together although hearing that the lead developer for dinkum left makes me feel a bit uneasy
Really wanting this product to work

3 Likes

Nice. spotifyd works well for my usage. I just need to display album art and control the music. I would prefer to control by voice but if I have to use the screen or a phone, I will live with that for the time being.

Ah well! Worth asking. If anyone else reading is interested, please let me know. :slight_smile:

Yes, we’re focusing on Napster because they have kept their API public.

Seems like the Mycroft2 will never do what I want it to do then. I have an entire family on Spotify and they aren’t going to want to move to Napster. I am still gonna play with Neon and OVOS for a bit to see if I can salvage this for anything(maybe for a recipe machine in the kitchen) but I feel like I am just going to end up parting it out or using it as something it was not intended to be used as like a drive-in movie screen for my daughter’s toy dolls.

@AlertSubject Here are lots of answers, sorry about the WOT :wink:
We at Neon are glad you feel some customer support coming from us. If you’ve heard the saying “a rising tide lifts all boats”, we feel strongly that supporting our community benefits us all.

Is neon ai just a fork of mycroft core?
We started off that way back in 2017, but we have a lot more to offer now.

Do all skills work?
I’m thinking you mean the Mycroft skills? We’ve done our best to stay compatible with Mycroft’s “Classic Core” and community built skills as various updates have come along.

How about mimic support?
Yes, we use Mimic and others in our on-device TTS processing. If you drop in to one of our Matrix rooms, our tech team can help you with more details for specific applications. My understanding is we’re actually getting better results than Mimic alone by using Coqui and other speech processing we’ve been working on in-house.

Does it handle processing locally?
Yes it can - though I’m not sure exactly which processing you’re referring to, it was critically important to us to provide the option for complete data privacy, which means local processing.

Can the device be managed via web interface? (as with mycroft currently)
Yes

Did I understand that correctly that homeassistant is not yet working on neon? Because that was pretty much one of the main reasons for me to get a mycroft.
Two people that I know of have gotten it to work, one on here - https://matrix.to/#/#NeonMycroft:matrix.org - and Daniel our tech lead. However, it’s not yet the sort of quick & easy process a non-developer would want. We’ve also offered a skill bounty (a Mark II device) in hopes that someone has time to work on the skill sooner than we can get to it.

I’ve looked at your website but it feels a bit overloaded with information left and right.
It’s been very helpful to get so much input recently into what information is important to our users. We want all the information to be available - the trick of course is to organize it so that you don’t have to wade around looking for answers. Of course we also have a lot of information on there that is oriented toward corporate clients. We’ve started some user documentation on Github, and would be very happy to have community members contribute there. If there are specific changes that you think would benefit our website, please do send me an email.

My understanding too is that this issue isn’t at Mycroft’s feet - Spotify revoked the API key that was being used for the Spotify skill, even though the Spotify skill only worked if you had a Premium subscription. There is a thread on this over on the Spotify forum.

You can still have people create their own key. There is a 3rd party plugin for Volumio that does that very well.

When I download this and try to install, it fails. I just get a lot of command line errors. I would try to get those errors for reporting but I cannot get SSH working using the Mycroft instructions.

Possiblly this bug:

where Mycroft II does not accept valid keys.

(Yes, I opened the bug against the “hardware” repo - there were no other Mycroft II repos at the time.)

1 Like

I had problems with ssh too, it’s picky about line feeds. What worked for me is to have the ssh-rsa then carriage return, then key and the comment can’t have any spaces in it.