It’s great to see car manufacturers go out of their way to screw their clients. They won’t be around much longer this way 
The sad fact is most of thier clients will never notice because the idea of connecting thier car to thier computer is so foreign to them that they don’t even know it’s important. They will never even blink unless people like us light Mazda up enough that they understand they made a mistake…
5 Likes
I think takedowns are automatic.
1 Like
I think the simple solution is to provide this as a custom_integration instead of having it inside core. I managed to get it working but getting a bunch of these errors. None of the entitiesID / Names are properly being filled out… any ideas? Not sure which door is which door. EntityID’s are showing like binary_sensor.2022_cx_5_2_5_s_ce_awd_door_6
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:371
First occurred: October 27, 2023 at 10:33:08 PM (7 occurrences)
Last logged: October 27, 2023 at 10:33:08 PM
* Entity None (<class 'custom_components.mazda.button.MazdaButtonEntity'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please report it to the custom integration author
* Entity None (<class 'custom_components.mazda.sensor.MazdaSensorEntity'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please report it to the custom integration author
* Entity None (<class 'custom_components.mazda.device_tracker.MazdaDeviceTracker'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please report it to the custom integration author
* Entity None (<class 'custom_components.mazda.lock.MazdaLock'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please report it to the custom integration author
2 Likes
12 Likes
This seems promising - did you get any further with it?
1 Like
Any updates and how can I get this working myself? 
1 Like
By the way, it seems that the repo with the Python lib for the Toyota Home Assistant custom component for North America has also been taken down with a DMCA notice: https://github.com/widewing/toyota-na
Let’s hope Toyota Europe doesn’t take similar steps. It’s sad to see this behavior of car makers currently.
2 Likes
I wonder if SmartCar got another recent addition to their integrations 
Just a thought.
Does Mazda App or connected services build on any open source code?
Can’t find a copyright statement in the app or the connected services documents.
Cant find any open source references either.
Hmmm. …
Who does not? It is very unlikely that they are not using some sort of code which is open source.
Since when can anybody copy code directly from a secure repository?
And when an API’s address and key has became copyrighted material?
I think that these guys taking down these repositories are happy to make their own company look shit…
Don’t they have to disclose.
As far as I can tell there is no copyright notice in the app.
I believe that depends on the license of the source code. But you can have a look what is compiled in the apk:
And you can notify the owner of the source code if you find any open source code which is not disclosed.
For example GPL has this:
The GPL additionally states that a distributor may not impose “further restrictions on the rights granted by the GPL”. This forbids activities such as distributing the software under a non-disclosure agreement or contract.
The fourth section for version 2 of the license and the seventh section of version 3 require that programs distributed as pre-compiled binaries be accompanied by a copy of the source code, a written offer to distribute the source code via the same mechanism as the pre-compiled binary, or the written offer to obtain the source code that the user got when they received the pre-compiled binary under the GPL. The second section of version 2 and the fifth section of version 3 also require giving “all recipients a copy of this License along with the Program”. Version 3 of the license allows making the source code available in additional ways in fulfillment of the seventh section. These include downloading source code from an adjacent network server or by peer-to-peer transmission, provided that is how the compiled code was available and there are “clear directions” on where to find the source code.
The FSF does not hold the copyright for a work released under the GPL unless an author explicitly assigns copyrights to the FSF (which seldom happens except for programs that are part of the GNU project). Only the individual copyright holders have the authority to sue when a license violation is suspected.
Source: GNU General Public License - Wikipedia
1 Like
Actually that has been taken down a year ago. The DMCA notice was from 2022.09.20.
But Mazda did another DMCA for forks of the original project:
give me the code and ill post it… , im judgement proof(i have no money for them to extract) im pretty sure i could one man this bs notice in court knowing f all about the legal system… id pretty much explain what an api is and what the software does lol… if it all goes south and they order me to pay money ill just declare bankruptcy on they ass lol
Shades of Slashdot 
@Chris_Holt this is a bit more complicated than that.
All of it was done by Mazda North America, if you have asked the European local distributors, they have not had any information about the whole situation and they did not even gave a flying F… To reach to somebody at Mazda Japan, you should have found your way around to get any contact with them.
The shittiest thing in is this, is the mentality that the US part of the company presented. They basically attached an opensource developer with bogus claims and alienated people with their attitude. They lost a few clients due to this shortsighted attitude. But Mazda has the idea to plant in your mind as a child that they have good cars. They try to support it how they interact with customers that a child would see next to a parent in a showroom or service the attitude and the feeling of the zoom-zoom, etc… They literally just shit into the middle of that for corporate greed for a short term income from subscriptions.
As the “trial” period of the 3 years connected car service ends with all the newer connected Mazda cars, they started to charge money for features like remote start. And to make sure that nobody would get around their subscription model, they had to weed out all the other options which communicates with their API, leaving everybody with a dumpster fire app. Which has a lot of negative reviews on PlayStore complaining about not updating details, missing notifications, etc. And if you check the responses from Mazda, they only reply to the 5 star reviews, like thank you for your positive feedback.
They don’t give an F about their customers, they do care about the milking cows who are paying for subscription, and do not realise, that how overpriced the service what they are paying for.
Watch a bit of Louis Rossmann videos on Youtube about the car industry’s rapist mentality, and you will know more. It is all about corporate greed. Just look around a check how many other manufacturers are supporting compatibility with other systems. And how many forcefully squashed it.
Of course, you have to pay some subscription fee for all of them, but when a company is selling your driving data to a company like LexisNexis and removes it from the context, and hikes your insurance, then really, why are you paying for a subscription when you are being cheated and robbed the same time.
Mazda still have really nice cars, I do drive an older model without the connected features, and if you look at the new electric or hybrid model what they are going to sell on the Chinese market, they look amazing. But they manage to build disasters as well, like their CX-60 range with all the suspension and transmission issues.
2 Likes