probably a good idea...
maybe easier to use Dashboard replacement
Moderators: grovkillen, Stuntteam, TD-er
Re: maybe easier to use Dashboard replacement
Thank you for your work! You are much better with that, than i will ever be.Patou wrote: ↑15 Feb 2022, 14:18 Sorry I made it public now.
Here is the link https://docs.google.com/document/d/1rmj ... ue&sd=true

It looks really good.
some things caught my eyes:
- you dont need to write a slidervalue to the corresponding task anymore. this is now done by the dashboard.
- there are more options for time and date and there is also year. and you don´t need code for it anymore. the values will be displayed automatically
i´ll read it more thoroughly when i have more time for it...- You can call an item of a “bigVal” Task something that consists “clock”/”time”, “date”, “year” to get this displayed independent of the value. (german speaking person can also use “uhr” and “datum” -> for date format with dots)
Re: maybe easier to use Dashboard replacement
The reboot is only (really) needed when uploading config.dat or security.dat.
All other file uploads it is not needed.
But maybe I should enforce it when uploading one of those, as you will otherwise corrupt the settings file when saving anything.
All other file uploads it is not needed.
But maybe I should enforce it when uploading one of those, as you will otherwise corrupt the settings file when saving anything.
Re: maybe easier to use Dashboard replacement
please don´t.
i never needed a reboot for uploading a css or html file.
for testing these files it would be especially annoying...
Re: maybe easier to use Dashboard replacement
That's what I meant too...
Only when those files were updated, the node should reboot, or at least refuse to save.
Only when those files were updated, the node should reboot, or at least refuse to save.
Re: maybe easier to use Dashboard replacement
ahh i get it.. you mean an enforced reboot when uploading .dat files.
puhhh.. relieved
puhhh.. relieved

Re: maybe easier to use Dashboard replacement
Remember the second part of the name of ESPEasy

Re: maybe easier to use Dashboard replacement
Hello,
I did not find enough explanation in your post about date time day month and year so please adapt the text when you have more time
I added the last iframe at the end of the document.
Nice work ( I can only write manuals ! not able to do your job but I appreciate to use it)
https://docs.google.com/document/d/1O9_ ... ue&sd=true
Patou
I did not find enough explanation in your post about date time day month and year so please adapt the text when you have more time
I added the last iframe at the end of the document.
Nice work ( I can only write manuals ! not able to do your job but I appreciate to use it)
https://docs.google.com/document/d/1O9_ ... ue&sd=true
Patou
Re: maybe easier to use Dashboard replacement
there is nothing more to it

if in bigVal or bigValC you call a taskitem with these names then regardless of its value in espeasy it will show the time,date,year
Re: maybe easier to use Dashboard replacement
@Patou
I changed some small things without formatting
and some pictures are could be updated or missing.
If you have github i really would appreciate it if could publish/put the manual in the easyfetch repository. So it would be easier for me to collaborate.
I changed some small things without formatting
and some pictures are could be updated or missing.
If you have github i really would appreciate it if could publish/put the manual in the easyfetch repository. So it would be easier for me to collaborate.
- Attachments
-
- text2.zip
- (1.14 MiB) Downloaded 1160 times
Re: maybe easier to use Dashboard replacement
There is a new test.html with some new features for testing:
What’s new:
- url parameter: add ?unit=<unitnr> to the url to directly access a node (good for bookmarking)
- up to 4 buttons with one dummy: Name a dummy device something that consists "dButtons" and every value becomes a button.
You can add an option for colorbuttons with "?C"(see picture below)
- add a thingspeak value to display the last value of a field of a public thingspeak channel, use this scheme for a value-name: "name&<channel>&<fieldnumber>" optional you can give it a unit of measurement with ?<unit of measurement> (like in every other field):
- take the red pill: long press the house button and it will bring you to the devices webui without fetch...
What’s new:
- url parameter: add ?unit=<unitnr> to the url to directly access a node (good for bookmarking)
- up to 4 buttons with one dummy: Name a dummy device something that consists "dButtons" and every value becomes a button.
You can add an option for colorbuttons with "?C"(see picture below)
- add a thingspeak value to display the last value of a field of a public thingspeak channel, use this scheme for a value-name: "name&<channel>&<fieldnumber>" optional you can give it a unit of measurement with ?<unit of measurement> (like in every other field):
- take the red pill: long press the house button and it will bring you to the devices webui without fetch...
Re: maybe easier to use Dashboard replacement
small update to dButtons:
- add "&<nodenumber>" to the valuename and the button send its events (normal or long) to the corresponding node.
Edit "&A" will send an event to all connected nodes (it replaces the "allNodes" dummy-device) Buttonmania:
- add "&<nodenumber>" to the valuename and the button send its events (normal or long) to the corresponding node.
Edit "&A" will send an event to all connected nodes (it replaces the "allNodes" dummy-device) Buttonmania:
Re: maybe easier to use Dashboard replacement
Definitely needs detailed documentation.
I have been following it from the start and I have to go over a collection of older posts to get working now.
I have been following it from the start and I have to go over a collection of older posts to get working now.
-D
Re: maybe easier to use Dashboard replacement
I know..... i should rename the topic to: "maybe you have to study a lot to use this dashboard replacement" 
I just added a new feature:
- an empty bigVal-tile: name a value "noVal" and you’ll get an empty tile
and right now i update just test.html with new features....

I just added a new feature:
- an empty bigVal-tile: name a value "noVal" and you’ll get an empty tile
and right now i update just test.html with new features....
Re: maybe easier to use Dashboard replacement
Finally i found some energy to write a small documentation of easyfetch on github.
I hope it is halfway understandable...
and please contact me if i forgot something.
I hope it is halfway understandable...
and please contact me if i forgot something.
Re: maybe easier to use Dashboard replacement
Good guide ... easy to follow
Thanks
Patou
Thanks
Patou
Re: maybe easier to use Dashboard replacement
I added a url parameter live update (just found out that this is possible without reloading the page every time
)
Clicking on a unit in the list adds the corresponding url parameter (?unit=x) to the url.
So if you reload the page you start with the unit selected before.
Initially it was only possible to enter the parameter by hand to have direct access to a unit

Clicking on a unit in the list adds the corresponding url parameter (?unit=x) to the url.
So if you reload the page you start with the unit selected before.
Initially it was only possible to enter the parameter by hand to have direct access to a unit
Re: maybe easier to use Dashboard replacement
@TD-er can we make this Post Sticky? I think that's a pretty cool addon that should get more recognition.
@Chromo23 maybe update the First Post with all the new infos. And change Thread Title to something like 'Addon: Custom Dashboard "EasyFetch"'
@Chromo23 maybe update the First Post with all the new infos. And change Thread Title to something like 'Addon: Custom Dashboard "EasyFetch"'
Re: maybe easier to use Dashboard replacement
Board settings to avoid spam don't allow to edit messages after a couple of days...
/Ton (PayPal.me)
Re: maybe easier to use Dashboard replacement
I am not sure if this thread should be sticky since it only provides the reader with the history of rocky road to an alternative dashboard...
There is almost no useful content for using esyfetch in its latest form.
A instructions and the dashboard itself can be found on github (follow the link in my signature)
There is almost no useful content for using esyfetch in its latest form.
A instructions and the dashboard itself can be found on github (follow the link in my signature)
Re: maybe easier to use Dashboard replacement
Okay, well maybe make a new thread that explains how to set it up in a few short steps and a few example screenshots?
Then this one here can get lost im time.
i Do think this is a very practicall addon that more people should know about.
And as TD-ed made it stick he seems to agree.
Then this one here can get lost im time.
i Do think this is a very practicall addon that more people should know about.
And as TD-ed made it stick he seems to agree.
Re: maybe easier to use Dashboard replacement
Well I do agree that the amount of documentation on the dashboard functionality is far below what's acceptable.
But I also agree that it is way more important to have something properly documented instead of "see here is a thread where there should be information on how to use this feature, good luck!"
Re: maybe easier to use Dashboard replacement
@TD-er isn´t there a possibility to give thread-starters the ability to change the content of their first posts? I haven´t looked at phpbb yet but i am sure there is some kind of user management like profiles.
I can think of things like the release notes and announcements, newest updates on plugins and also addons like my dashboard that would be sticky and you do not have to scroll through the whole thread.
I think most of the people are used to a forum instead of using (and registering to) GitHub for the latest news.
On the other hand i really like the Tasmota approach where you have all the content in one place... The most confusing for me with ESPeasy at the beginning was gathering info from three different places. Fortunately this has changed with the progress of ESPEasy.readthedocs.io. Thanks a lot to all participants for that by the way!!!
I can think of things like the release notes and announcements, newest updates on plugins and also addons like my dashboard that would be sticky and you do not have to scroll through the whole thread.
I think most of the people are used to a forum instead of using (and registering to) GitHub for the latest news.
On the other hand i really like the Tasmota approach where you have all the content in one place... The most confusing for me with ESPeasy at the beginning was gathering info from three different places. Fortunately this has changed with the progress of ESPEasy.readthedocs.io. Thanks a lot to all participants for that by the way!!!
Re: maybe easier to use Dashboard replacement
@TD-er
is it possible to deactivate the authorization request for an individual index page?
As soon as i set a password in espeasy i also have to type my credentials when opening this dashboard.
A workaround is to run the dashboard on a different unprotected device because just fetching json data from a password protected device is no problem.
But at some places there is a need to protect all devices and just grant access only to my dashboard.
Could you help me with that?
is it possible to deactivate the authorization request for an individual index page?
As soon as i set a password in espeasy i also have to type my credentials when opening this dashboard.
A workaround is to run the dashboard on a different unprotected device because just fetching json data from a password protected device is no problem.
But at some places there is a need to protect all devices and just grant access only to my dashboard.
Could you help me with that?
Re: maybe easier to use Dashboard replacement
Not quite. The discussion there is about protecting sensitive information in json. I would like to have the ability to access custom HTML pages without a password prompt
Re: maybe easier to use Dashboard replacement
Small updates for "easyfetch"
- I fixed an issue where slider values were not updating on esp32s, caused by a bug described here: https://github.com/letscontrolit/ESPEasy/issues/4374
- Sliders now have a "switch" function. If you click on the left half of the slider, the value becomes the set minimum (default=0) and if you click on the right half, it becomes the maximum (default=1023)
Edit: reduced the "switch" areas of the slider to the upper and lower 1/6th
- I fixed an issue where slider values were not updating on esp32s, caused by a bug described here: https://github.com/letscontrolit/ESPEasy/issues/4374
- Sliders now have a "switch" function. If you click on the left half of the slider, the value becomes the set minimum (default=0) and if you click on the right half, it becomes the maximum (default=1023)
Edit: reduced the "switch" areas of the slider to the upper and lower 1/6th
Re: maybe easier to use Dashboard replacement
@TD-er and @Ath
I wanted to integrate an easier way to create a toggle-button in easyfetch.
Currently you have to add a rule for a Button to work:
For this new behavior you just name the value of a "switch"-device "bntState" + "?" + the gpio you want to toggle (e.g. "btnState?14")
It creates a tile that sends the toggle command.
The problem is, that the "GPIOToggle"-command doesn´t work when the gpio is already set in the devices page.
Is there a workaround for that?
I wanted to integrate an easier way to create a toggle-button in easyfetch.
Currently you have to add a rule for a Button to work:
Code: Select all
On ButtonEvent Do
GPIOToggle,14
Endon
It creates a tile that sends the toggle command.
The problem is, that the "GPIOToggle"-command doesn´t work when the gpio is already set in the devices page.
Is there a workaround for that?
Re: maybe easier to use Dashboard replacement
And i know, that this error message makes sense since the device is an input as the name switch suggest.
But me and probably other people too use this for outputs like a relay as well, since you immediately can see the output state in the devices tab.. (and easyfetch also uses the state of the device to color the virtual button accordingly)
But me and probably other people too use this for outputs like a relay as well, since you immediately can see the output state in the devices tab.. (and easyfetch also uses the state of the device to color the virtual button accordingly)
Re: maybe easier to use Dashboard replacement
You could set the pin to some output level at boot, or maybe on the Hardware tab at the bootstates section.
Re: maybe easier to use Dashboard replacement
That check & error message is only applied to GPIOToggle, so you could use an alternative like:
Code: Select all
gpio,14,=![plugin#gpio#pinstate#14]
/Ton (PayPal.me)
Re: maybe easier to use Dashboard replacement
This works, but contradicts the approach to make (easily) an user-friendly dashboard switch without using rules.
This doesn’t work...
That’s working but only for local usage. But i would need it to work also for the remote units via SendTo
I seems that the last part of the command doesn’t get parsed correctly at the receiver end.
sender:
Code: Select all
SendTo,12,"gpio,15,=![plugin#gpio#pinstate#15]"
Code: Select all
254980929: gpio,15,=!0
254980931: Command: gpio
Edit:
Code: Select all
=![plugin#gpio#pinstate#15]
Re: maybe easier to use Dashboard replacement
Yes, that's the case, can't yet see a way to prevent that, other than having a rule on the remote side that does this code, only needs 1 argument... but still a rule to be added therechromo23 wrote: ↑05 Dec 2022, 19:53 Edit:actually gets parsed but on the sender side....Code: Select all
=![plugin#gpio#pinstate#15]

/Ton (PayPal.me)
Re: maybe easier to use Dashboard replacement
Ok, thanks. I now solved it differently.
Re: maybe easier to use Dashboard replacement
I did some changes in code structure, functionality and appearance.
- new color-scheme for light mode
- simple toggle switch when adding a switch plugin without using rules,
available since the latest builds (if "Inversed Logic:" is set the value-name needs to be changed from "State" to "iState")
if you have an old build use "btnState" + ? + "gpio Number" instead (e.g. btnState?12)
(i also prepared a PWM slider but that needs pin states in json)
- number input (name a dummy-device "vInput"), enter a number and confirm with "enter" or "click" on the upper part of the tile
- always-square - layout always puts empty tiles automatically at the end to make it square
- sysinfo in the nodelist
- create empty Tiles in dButton and vInput that hides in mobile mode by entering "noValAuto" as a value-name (just "noVal" crates an empty tile without this ability)
Edit: almost forgot... the cron plugin is now properly visualized
New Colors: Simple toggle switch: Number input: Always square: Sysinfo: Cron Tile:
- new color-scheme for light mode
- simple toggle switch when adding a switch plugin without using rules,
available since the latest builds (if "Inversed Logic:" is set the value-name needs to be changed from "State" to "iState")
if you have an old build use "btnState" + ? + "gpio Number" instead (e.g. btnState?12)
(i also prepared a PWM slider but that needs pin states in json)
- number input (name a dummy-device "vInput"), enter a number and confirm with "enter" or "click" on the upper part of the tile
- always-square - layout always puts empty tiles automatically at the end to make it square
- sysinfo in the nodelist
- create empty Tiles in dButton and vInput that hides in mobile mode by entering "noValAuto" as a value-name (just "noVal" crates an empty tile without this ability)
Edit: almost forgot... the cron plugin is now properly visualized
New Colors: Simple toggle switch: Number input: Always square: Sysinfo: Cron Tile:
Re: maybe easier to use Dashboard replacement
Tip of the day:
You can use easyfetch more dynamically by enabling and disabling certain tasks dependent on user interaction.
(For now we have to link the device that needs to be en- or disabled with another device which keeps a state but in the latest builds it is possible to retrieve the state of a taks in rules. See here: https://github.com/letscontrolit/ESPEasy/pull/4421 This allows even more sophisticated scenarios.)
Here a very simple code example:
And the result:
Another example (a countdown timer for a light):
You can use easyfetch more dynamically by enabling and disabling certain tasks dependent on user interaction.
(For now we have to link the device that needs to be en- or disabled with another device which keeps a state but in the latest builds it is possible to retrieve the state of a taks in rules. See here: https://github.com/letscontrolit/ESPEasy/pull/4421 This allows even more sophisticated scenarios.)
Here a very simple code example:
Code: Select all
On TimerEvent Do
If [dButtons#Timer]=0
TaskValueSet,2,2,2
TaskEnable,3
Else
TaskValueSet,2,2,0
TaskDisable,3
Endif
Endon
Re: maybe easier to use Dashboard replacement
I found some time to enhance easyfetch a bit..
What´s new:
- auditive feedback
enable/ disable click sounds persistently (via cookie) -> longpress the "x" in the sidenav
- nodelist enhancements
-hover to open sidenav on desktop
-slide ltr or rtl to open/close the sidenav on mobile devices
What´s new:
- auditive feedback
enable/ disable click sounds persistently (via cookie) -> longpress the "x" in the sidenav
- nodelist enhancements
-hover to open sidenav on desktop
-slide ltr or rtl to open/close the sidenav on mobile devices
Re: maybe easier to use Dashboard replacement
Next will be trying to match icon files on the file system with task names?
Oh, which reminds me, you asked for a directory listing in JSON a while ago...
Oh, which reminds me, you asked for a directory listing in JSON a while ago...
Re: maybe easier to use Dashboard replacement
I will think about it?

Huh..did I? I asked so many things that i probably can´t remember this one.

But the more JSON you throw at me the better....

Re: maybe easier to use Dashboard replacement
I probably read your request between the lines then, but still sorry I didn't do it yet.
You maybe didn't know you wanted it but I don't like to keep people from features they eventually would want to have

Re: maybe easier to use Dashboard replacement
Very nice job ! congratulations ! I look at the code but
Would be nice to have an indication of version or revision in the dashboard
Fred, France


Would be nice to have an indication of version or revision in the dashboard
Fred, France
Re: maybe easier to use Dashboard replacement
Hi Fred,
happy to hear that you like easyfetch.
Like this? Edit:
I am not sure what should be displayed here anyway since it is redundant to the infos you can gather from the webui of the device itself.
happy to hear that you like easyfetch.
Do you mean an indication of the build of ESPeasy?
Like this? Edit:
I am not sure what should be displayed here anyway since it is redundant to the infos you can gather from the webui of the device itself.
Re: maybe easier to use Dashboard replacement
Hello
No I speak of the revison of YOUR html code
To know when to upgrade
No I speak of the revison of YOUR html code
To know when to upgrade
Re: maybe easier to use Dashboard replacement
Thank you Ath

Since i commit every small change immediately i see no need in versioning. I have not planned any new features in the future and since almost all of my commits are bug fixes so it is always time to upgrade to the latest file.

Nevertheless i will maybe add an info about the commit number to have a reference point. I have to look where i can squeeze this in because i am very close to my self-imposed 10k limit

The latest "version" of easyfetch will probably not change for a while since i hopefully have fixed all bugs. I will start to concentrate now on the more unpopular part of easyfetch...documentation

Re: maybe easier to use Dashboard replacement
Popularity depends on who you ask

I always love documentation.... when it is done

Re: maybe easier to use Dashboard replacement
Do we have a volunteer?

But seriously, i am a bit disabled and it takes a lot of energy to sit in front of the computer and do stuff. And since documentation comes last i simply often do not have any energy left for that. (i guess i could change my behavior to implement a better routine but this is easier said than done)
Re: maybe easier to use Dashboard replacement
I know the feeling.. well not about your body not cooporating.
I really don't think I could manage it when my body would refuse to cooporate. That would be extremely frustrating.
So please do what you can and nothing more!
I really appreciate the effort so far and it is to nobody's interest if you cause yourself to burn-out and loose interest (or energy to continue).
I know that starting documenting at the start of a design process often feels like wasted time as you can often throw away when you gain new insights.
On the other hand it may help to put at least a few ideas in writing, so there is some backlog of intentions for others to read.
So maybe you could add just a single readme txt file where you simply write down in a few sentences:
- Workflow
- Intented use cases
- New ideas
That would already be a good starting point for someone to pick up drafting some documentation which you then could review.
I really don't think I could manage it when my body would refuse to cooporate. That would be extremely frustrating.
So please do what you can and nothing more!
I really appreciate the effort so far and it is to nobody's interest if you cause yourself to burn-out and loose interest (or energy to continue).
I know that starting documenting at the start of a design process often feels like wasted time as you can often throw away when you gain new insights.
On the other hand it may help to put at least a few ideas in writing, so there is some backlog of intentions for others to read.
So maybe you could add just a single readme txt file where you simply write down in a few sentences:
- Workflow
- Intented use cases
- New ideas
That would already be a good starting point for someone to pick up drafting some documentation which you then could review.
Who is online
Users browsing this forum: No registered users and 12 guests