Exactly, it was a crappy stop gap solution.
Exactly, it was a crappy stop gap solution.
So a game could release an “update” with less content and charge for it, and that would be ok to call a DLC, because they charged for it?
Yeah I still use their temp sensors and they seem to work fine. The door/window sensors seem to work ok too, but for the most part I’ve just swapped over to Aqara for anything new I’ve bought.
Yeah I gave up with them and went with Aqara ones. I just gradually replaced all the Sonoff motion sensors.
The Hue motion sensors are great, but quite expensive. I’ve found the Aqara ones to be best value for money. Haven’t had many issues with them.
Yeah I have been. But have a mix of apex and mini graph. Was going to migrate them all to apex and noticed it hasn’t been updated in years. Didn’t want to migrate everything and then have it stop working in a future home assistant update. Could be worrying about nothing though.
The only other thing I’ve noticed is that it’s quite power hungry compared to mini graph, albeit it having more functionality.
I don’t know, I haven’t used Grafana.
The event is being held 4 Oct, so shouldn’t be much longer.
What is/are Moto Flashlight and Camera gestures? And what phone do you now have?
It’s not a walled garden, it’s kind of the opposite. You can connect devices regardless of brand and it’s a server you can run locally. In theory you wouldn’t need to update it or ever connect it to the internet again, as long as your devices can run locally.
If you have an old laptop or a raspberry pi 4, you can always give it a try before scrapping what you’re currently using.
Thanks heaps for that. At the moment I’m relying on my Enlighten app login. Will check them out.
Mine has an integration which is handy (enphase). But it doesn’t tell me my grid usage. I’m trying to calculate it by taking my total consumption and subtracting my solar production. I think it roughly gives me the right overall number.
The problem is I can’t seem to get how much I’m feeding back into the grid. I might be able to work it out with some sort of calculation.
I might DM you about the P1, as it sounds like that might do the job.
Nice one. My system has that with its integration which is good. I’m yet to put it into a graph. The part missing from mine is working out how much I’m using from the grid.
My comments are actually after seeing the local pricing. I still think it’s too expensive. Perhaps other locations are more affordable.
This post is asking what apps are worth paying for. Someone suggested Sync is worth paying for. I disagree and offered a different opinion. No one said you had to pay for it, just whether it was worth paying for or not.
I’m sticking with Voyager for now. Sync is too expensive for a beta app. There’s no post functionality in it yet. I’m also not sure how I feel about paying so much for an app to access Lemmy. I’d rather put some of that money into the instances themselves.
Edit: I should say it’s totally up to you if you think it’s worth it. I’m all for supporting developers for their work. But in my opinion Sync isn’t worth the asking price in its current state, especially compared to the other apps available.
It already has it. If you click on your account and then edit, you’ll have the option to add another account.
“Because Xbox mandates that any games launched on its current-gen systems run smoothly on both Series X and Series S” - from the article
So no, they don’t get to just pick the minimum specs they support like on the PC version. They have to build a game that runs similarly on S and X, or not launch on either. Hence, the S is always going to limit what devs will be able/willing to do on the current gen consoles. More so than if they could just focus on the X and PS5.
That article is from 2021 and doesn’t provide links or details to any data. The claim in the article says it’s 50/50. But again, no data is provided.
If it’s so straight forward, then what are the devs complaining about?
Microsoft requires they meet a specific standard on both the S and X, which is making it harder for them to do. They don’t build to every specific PC variant. But they have to build to both the X and S.
Recently did this and yes it’s a pain. I don’t know if it’s going to help until next time we change phones, but what I did this time was name the device after the person, rather than the phone model.
The idea being that I can delete the old device in the future and replace it with the new device, named the same. That way I don’t have to change the device name in each automation every time. Hopefully that made sense. But I still haven’t tested it in reality.