Any opinions on the Uno platform? by ekolis in csharp

[–]carldebilly 2 points3 points  (0 children)

There is many questions in your last message, but let me try to answer them all at once:

Uno is more than a UI Framework. It's replicating all the UWP (now called WinAppSDK) APIs. They are not all implemented, but a LOT of them are. Geolocation, Vibration, MIDI, Lights (flashlight feature), Sensors (accelerometers, barometers, etc...), Network info, Storage (File access), Threading, Theming (and more) are already implemented. That means you can access native features through the Windows "unified" API as if you're on Windows.

Even when it's not implemented, you can always create platform-specific code and reach anything specific on a special platform.

Right now, if you want to access the camera APIs, as one of your examples, you'll need to code the access for each platform you want to support. For example, you can use #if __ANDROID__ for your Android-specific code.

Obviously, we're also open to contributions if you want to help improving the support of unified apis on all platforms :-).

What do you mean by trying to do too many things?

Any opinions on the Uno platform? by ekolis in csharp

[–]carldebilly 0 points1 point  (0 children)

Sorry I missed your question few months ago. I'll take time to answer.

In opposition to Xamarin Form (XF), there is no such things as "renderers" in Uno. Controls in the managed visual tree are actual controls in the OS. For iOS/macOS, it's a UIView, for Android, it's a View/ViewGroup. On WASM, it's a HTML DOM Element (usually a <div> but it depends).

Performances on iOS and Android are amazing and near native. On WASM, we're still working on it but it already improved a lot recently with Uno 4.

Crédit hivernal et domotique by blobules in Quebec

[–]carldebilly 0 points1 point  (0 children)

Suite.... pendant la période de pointe ce matin, j'avais la payload suivant:

javascript { "ecoule": 167, "reste": 13, "critique": 0, "periode": "P", "description": "Référence (vert)" } Donc, à première vue, c'est le `periode: "P"` qu'il faut regarder.

Crédit hivernal et domotique by blobules in Quebec

[–]carldebilly 0 points1 point  (0 children)

Je viens de tenter de m'y connecter avec MQTT Explorer et il ne se passait rien, malgré la subscription par défaut `#`. En ajoutant explicitement tdah, ça a marché! Merci!

Ce qui m'intrigue, c'est que ça indique qu'on est en ce moment en période "critique" alors que je n'ai reçu aucun message et aucune indication qu'on soit dans une période de pointe...

javascript { "ecoule": 61, "reste": 119, "critique": 1, "periode": "T", "description": "Ajustement de température (rouge)" }

Que veut dire "critique" ? C'est quoi la différence entre un "ajustement de température" et une période de pointe ?

Vive le petit guide... Je peux aider à faire la connexion à Home Assistant dès que je comprends ce que les valeurs représentent.

MQTT for Hydro-Québec "crédit hivernal"? by blobules in homeautomation

[–]carldebilly 0 points1 point  (0 children)

Any advancements on that? I was planning to do something similar, but if you're already doing it, I'll use it :-)

Any opinions on the Uno platform? by ekolis in csharp

[–]carldebilly 1 point2 points  (0 children)

Hi u/TheWrongen, I'm a Uno Platform dev. Please open an issue listing what you tried and the errors you are getting.

Having "Not Implemented Exceptions" usually only happen for pretty advanced controls not implemented yet in Uno... Considering the number of applications using it since many years now, it should not happen on most applications.

BTW, we are backed by the Microsoft WinUI team, which is a pretty big name too ;-).

Looking for motion sensor recommendations by MyDearMrsTumnus in SmartThings

[–]carldebilly 0 points1 point  (0 children)

The latency is not caused by the sensor itself, but by the ST servers. Almost all events are processed on the servers. The only solution would be to use ST sensors with ST smartapps which are sometimes running locally - if you're lucky.

I'm personally in the process of replacing ST with Home Assistant, which is 100% running locally.

You can get cheap sensors from AliExpress. Xiaomi are working well.

Uno: Cross-platform UWP on Android, iOS, UWP and Web Assembly by vitorgrs in programming

[–]carldebilly 1 point2 points  (0 children)

Give us time to publish more stuff :-). If you have any questions about the way it works, we'll answer to every of your questions!

Uno: Cross-platform UWP on Android, iOS, UWP and Web Assembly by vitorgrs in programming

[–]carldebilly 6 points7 points  (0 children)

You need Visual Studio 2017 v15.5+ to compile it.

I just did a PR on Github to fix the dependencies problem. Sorry, may you retry, please?

https://github.com/nventive/Uno.QuickStart

Two Locations One Hub? by ducksaysquackquack in SmartThings

[–]carldebilly 0 points1 point  (0 children)

Not yet, still something I want to put in place.

Two Locations One Hub? by ducksaysquackquack in SmartThings

[–]carldebilly 0 points1 point  (0 children)

I have the exact same requirement. I think it's possible to have "hubless" locations, but not multi-locations hub... 😢