Replies: 6 comments 15 replies
-
Hi, there are many questions here, let's address some of them first:
I don't see any mention in OpenHASP documentation about arbitrary font size, and there is no such thing in LVGL either, unless you use TTF fonts. Can you be more specific?
Can you be more specific about what's missing? |
Beta Was this translation helpful? Give feedback.
-
Hi, just to let you know that I'm working on the following:
|
Beta Was this translation helpful? Give feedback.
-
Awesome ;-) I will see if I can squeeze Robotocondensed.ttf into file system and try and fix up incoming json in my script. |
Beta Was this translation helpful? Give feedback.
-
State of the script so far - Per openHASP docs handles most of the IN and OUT openHASP topics from the ESP. Also most of the useful commands - antiburn, backlight, page, clearpage, restart, reboot, config, screenshot , statusupdate , idle.
|
Beta Was this translation helpful? Give feedback.
-
@s-hadinger As promised summary of findings from my experimenting, basically key feature gaps.
|
Beta Was this translation helpful? Give feedback.
-
@s-hadinger ,With this code in jsonl -
And this function -
I get -
But it should be showing properties for text and val when selecting one of the options from the drop down, not sure if I broke my code or something has changed ? The new tag feature does show however ;-) |
Beta Was this translation helpful? Give feedback.
-
I post this here in case it is of interest to anyone ....
I have a node red flow which completely manages openHASP devices. As soon as a device is connected to MQTT it is setup and controlled automatically.
I wondered if it would be possible to make haspmota work with this flow (without changing the flow)
So I have been experimenting by using some berry code to replicate some of the missing openHASP functionality.
Basically its a question of listening to openHASP topics, and reacting as native firmware would.
By interpreting commands, adding OR updating objects, publishing touch events and status updates etc.
I had no design in mind, so I just set it up to talk to my NR flow and added bits of code to overcome each problem in the process of downloading my layouts.
As my flow requires information from openHASP, I cobbled this together to send statusupdate messages.
Publishing touch events is easy enough -
With this and the main bit of code below, my screen does actually talk to my flow and downloads the layouts etc.
However there are a number of "issues" which are beyond me at the moment.
My NR flows make use of the following widgets and features which are not implemented in haspmota.
msgbox and cpicker (I could live without msgbox but colour picker is essential for home automation)
tag attribute on objects (used to include extra data in touch events)
text_font=xx Because my flows scale screen content to the size of the screen I use arbitrary font sizes. openHASP creates new font sizes on the fly for the default fonts, whereas haspmota only seems to do this for added ttf fonts.
Please don't laugh at my coding "skills" I only just started looking at berry ;-).
I got further than I thought I would (thanks to help from @sfromis)
Beta Was this translation helpful? Give feedback.
All reactions