I won’t be helping beata-anita again, but I don’t see why people are flagging her posts.
2 Likes
Hello all,
Could someone give me a little knowledge on openhasp vs haspone. I have been doing quite a bit of reading over the last week or so trying to pick which direction I would like to go. Codingwise- do they both use the same language to create the pages? And I’m sure you can already tell by my language but I can work with tutorials/ how-tos but am not a programmer by trade.
The only other question I really have right now is in my comparing of the screenshots between the gui of openhasp vs. haspone. Haspone seems to have 3 named pages as kind of like the authors main way of using the system. Can openhasp be set up the same way instead of having the navigation buttons at the bottom left/ right as in the project gui screenshots. Thank you all for your guidance on this.
I may have 1-2 other questions as followups based on your all’s responses. Thank you all again!!
openHASP is historically a “spin-off” from the HASPone project. While both share a common goal, the approach is quite different. The choice for one or the other depends on the hardware you (want to) use.
HASPone
- Uses the ESP-D1-mini with a Nextion/TJC display.
- Screen layout in HASPone is based on blueprints which you can deploy to a plate (device). This can be done through Home Assistant Blueprints.
- 12 pages with pre-defined layout.
- If you want to customize the screens or use a larger Nextion display, you need to use the Nextion Editor application.
- Support for a motion sensor on GPIO D0/D1.
openHASP
- Uses an ESP32 with a commodity display.
- The integration into HA is done using the openHASP Custom Component which you can install using HACS.
- 12 pages without any screen layouts. It expects you to upload your own layout in JSON Lines format. You can find several examples in the documentation to get you started, but you are free to create any layout you desire.
- There is no editor, but changing the layout is essentially like editing a JSON file.
- Up to 8 GPIO input/output pins can be configured.
So I would conclude: it depends on what devices you want to run the firmware on and the intended use-case.
Thank you for your response @fvanroie. Could you tell me what “value_str”:"\uE6E8" stands for. I was looking through the json examples and couldn’t figure out where/ what that was coming from.
https://www.openhasp.com/0.6.3/integrations/openhab/integration_openhab/#demo-screens
Also, could you lead me to somewhere that can show me how to get the device to go dim at idle?
Sorry for all of the questions, I would prefer to use this project over having to use a specific piece of hardware (nextion screen) but I’m getting worried that I may not quite be at the technical level to do so. I was seeing how haspone is template/ blueprint based and it almost babies a person into setup.
My only goals are to start scripts, automations, and entity control from the device.
Thank you again for any guidance you or others can give.
Hi there,
a little quesiton, if we look at the files on the openHASP we see in the file online.cmd the variable %ip%
question:
- Is there a way to use this in the jsonl file as a content?
- is there a list of this variables?
Regards
Adrian
There is currently: hostname, ssid, ip, model, version. You can use them in jsonl too like so "text":"%hostname%".
The dim level is handled by the openHASP custom component or can be set for example by a timer in HA.
If you have HACS installed in HA then the installation of the custom component should be a breeze…
Thanks for your reply. Would bi nice to also have %rssi% and maybe %rssi_percent%.
Not sure if I answer your question but all of those parameters are available as attributes of the openhasp entity in HA:
1 Like
Good day, hoping for some advise.
I run several lanbons in my house and have implemented the Handle offline state process.
However, this does not stop the plate from rebooting when mqtt is lost.
To clarify wifi is still working, but mqtt crashes or similar. In this instance the plate keeps rebooting.
Is there a solution for that. Another comnad script?
Thank you
Sounds like you should focus on fixing the MQTT crashes first …
Which version of openHASP are you running ?
Thank you.
Mqtt is not crashing. Occasionally the server goes offline for whatever reason I.e maintenance and when it happens there’s no mqtt.
At this point the plates just continuesly reboot, which at 3am presents itself in the form of a full bright screen in a dark room.
I’m in version 6.3.
This is how it is currently implemented in 0.6.3. If MQTT goes offline the plate locks up due to how PubSub MQTT client implements connect(). If several retries continuously fail, the plate reboots.
It’s a longstanding point of improvement for 0.6.4-dev that can be tracked here. It invloves swapping the PubSub MQTT client library with esp_mqtt. If you have a spare device, feel free to test it.
@fvanroie thank you very much for your response and explanation.
I’d be happy to try it with one of the running L8s. Is there a 0.6.4-dev .bin?
@fvanroie
So I installed this bin on one of my running L8s turned off mqtt and voila, no reboot.
All else seems ok all though the information tab in the web-interface is empty as well as all configuration parameters ie. wifi, mqtt, display, etc. However, the plate does seem to have the config as it’s connected to mqtt and responding in home assistant.
1 Like
Indeed, the latest development build can be found in the Actions tab on GitHub. Good to know it is working as intended. I don’t regularly test the Lanbon L8 build, so thanks for that. Just know that there may be some bugs. If you do run into an issue, please report it.
@fvanroie thank you. I’ve now installed on 5 plates.
I’ve had 2 loose wifi connection a couple of times (which didn’t happen before) but I need to observer longer. They seem ok in general.