This code was moved
This code is usable only if you are on Home Assistant 0.114 or older
For Home Assistant 0.115 and newer please go to: https://github.com/AdamNaj/ZWaveGraphHA
|diff -Naur ./Marlin/Marlin/Configuration.h ./Marlin-patched/Marlin/Configuration.h|
|--- ./Marlin/Marlin/Configuration.h 2020-02-25 15:06:10.000000000 -0500|
|+++ ./Marlin-patched/Marlin/Configuration.h 2020-02-25 15:35:58.000000000 -0500|
|@@ -1,3 +1,7 @@|
|+// This is all the base stuff + manual mesh bed levelling, so that users who have a stock printer|
|+// and an SKR Mini E3 can use this patch|
|* Marlin 3D Printer Firmware|
kiosk.js file with the content below to your
www folder in config.
Like any other custom script, use
ui-lovelace.yaml resources section to reference the
Make sure you add
kiosk somewhere in your URL. You can use it in the id of your view or in the query string.
|<Import Project="Sdk.props" Sdk="Microsoft.NET.Sdk" />|
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with
7668 lines of CSS (and just 2
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
Customers periodically ask "Why am I getting errors when talking to Redis". The answer is complicated - it could be a client or server side problem. In this article, I am going to talk about client side issues. For server side issues, see here
Clients can see connectivity issues or timeouts for several reason, here are some of the common ones I see: