Thank you, @fvanroie, I will take a look at tty* to see if I can find the SenseCAP device and report back in a day or so on my progress.
Update: after reviewing notes from my original flashing of the SenseCAP device, I used /dev/cu.usbserial-4013110 to flash it with firmware to work with MQTT and Home Assistant. Itās showing up on my WiFi, so I know itās working. However, it is no longer showing up as /dev/cu.usbserial-4013110 when I plug it into USB.
Iāll be contacting Seeed Studio to find out whatās going on. More to comeā¦
Are you on a Mac? I sorta thought so from the device naming.
Anyway, if so does it have the dmesg command - it is a linux command so may be present on Mac OS. It will report what device was created when it was plugged in.
Thanks for your help and ideas, @nickrout !
Yes, Iām on a Mac. Thatās was a good idea to try the command. It looks like thereās a USB failure to create a device, but Iām not sure what Iām looking atā¦
FYI: Hereās the output that might be relevant that I will also pass along to Seeed Studio:
[15250.454597]: AppleUSB20HubPort@40134141: AppleUSBHostPort::disconnect: persistent enumeration failures
[15250.570742]: com.apple.p2p: isInfraRealtimePacketThresholdAllowed allowed:1 option:32 threshold:50 noRegistrations:1 cachedPeerCount:0 fastDiscoveryInactive:1 fastDiscoveryOnSince:15250570
[15250.570768]: com.apple.p2p: currentInfraTrafficType:8087 checking if realtime upgrade required with inputPackets:2 outputPackets:0 packetThreshold:50
[15250.792864]: AppleUSB20HubPort@40134141: AppleUSBHostPort::disconnect: persistent enumeration failures
[15251.074077]: AppleUSBEHCIPI7C9X440SL@40000000: AppleUSBHostController::abortPipe: pipe <ptr> withError 0xe00002eb forClient <ptr> completed with 0xe00002f0
[15251.074102]: AppleUSB20HubPort@40134141: AppleUSBHostPort::createDevice: failed to create device (0xe00002bc)
[15251.074106]: AppleUSB20HubPort@40134141: AppleUSB20HubPort::resetAndCreateDevice: failed to create device, disabling port
[15251.074337]: AppleUSB20HubPort@40134141: AppleUSBHostPort::disconnect: persistent enumeration failures
[15251.412941]: AppleUSB20HubPort@40134141: AppleUSBHostPort::disconnect: persistent enumeration failures
[15251.595396]: com.apple.p2p: isInfraRealtimePacketThresholdAllowed allowed:1 option:32 threshold:50 noRegistrations:1 cachedPeerCount:0 fastDiscoveryInactive:1 fastDiscoveryOnSince:15251595
[15251.595420]: com.apple.p2p: currentInfraTrafficType:8087 checking if realtime upgrade required with inputPackets:1 outputPackets:0 packetThreshold:50
[15251.747595]: AppleUSB20HubPort@40134141: AppleUSBHostPort::disconnect: persistent enumeration failures
Re the Seeed Studio SenseCap (no built in sensors) and loaded openhasp 0.7.0-rc8 e291060 on it. I have the custom component 0.7.1 installed.
It gets discovered by home assistant 2023.9.0b4 but when I put in a path to a jsonl file, the sample page does not get loaded. When I load the using the sample here How-To - openHASP with the file editor on openhasp I get this on the screen
So something is not quite right.
False alarm of sorts - the cutting off if the dropdown was fixed by making it taller - the text wasnāt fitting.
In answer to that, yes the sensecap is working. Cool device, and your code is amazing. Unfortunately it doesnāt seem to be getting a lot of airtime in this forum.
1 Like
Good to hear the device is working. I really like it too for monitoring / control purposes om my desk.
Had great success with a Lanbon L8. Installed outside in a very sheltered area to control all front yard systems.
1 Like
I have been playing with it, at the moment I am using it for one thing, monitoring my blood sugar level at night (I am a type 1 diabetic).
It really only has one page, one label, nice dark colors so it doesnāt keep me awake, but is visible if I wake up and look at it. One 300 point font with the chars 0123456789. - only 22kb .bin file.
It is very underused in terms of power, but it is tidy enough to get permission to put it on the bedside table. I will insert some more functionality in due course! Might add a clock for a start, and weather info.
I canāt stop enthusing about openhasp!
Hi all!
Iām playing with my first OpenHASP panel, and it looks great!
I have several light sliders on a page that are controlled by yaml like this:
- obj: "p1b21"
properties:
"val": "{% if state_attr('light.stue_taklampe','brightness') %} {{state_attr('light.stue_taklampe','brightness')}} {% else %} 0 {% endif %}"
event:
"changed":
- service: light.turn_on
data:
entity_id: light.stue_taklampe
brightness: "{{ val | int }}"
"up":
- service: light.turn_on
data:
entity_id: light.stue_taklampe
brightness: "{{ val | int }}"
"down":
- service: light.turn_on
data:
entity_id: light.stue_taklampe
brightness: "{{ val | int }}"
That is 19 lines of yaml, repeated for each of my lights (so far about 15, on different pages).
Is there a parameterized templating (or other) mechanism somewhere (OpenHASP or HA) that I can use to avoid duplicating all this code?
Hi guys, can I install openHASP on the following capacitive touch panel:
It has 320x240 2.4āā ILI9341 TFT and Capacitive touch - not sure but below is schematics:
Have tried all precompiled firmwares, non of them worked. Will try online compiler to see if GPIOs can be editedā¦
When I say it looks like a Sunton, it is not one of the models listed in the docs so far as I can see.
found this config working to initialize TFT, but canāt get Capacitive touch to work yet:
;***************************************************;
; Sunton ESP32-WROOM custom dev board with ;
; - ILI9341 TFT SPI 4-WIRE ;
; - XPT2046 touch controller ;
;***************************************************;
[esp32-2432s028r]
extends = arduino_esp32_v2
board = esp32dev
upload_speed = 921600
build_flags =
${env.build_flags}
${esp32.build_flags}
${esp32.vspi} ; Use VSPI hardware SPI bus
;region -- TFT_eSPI build options ------------------------
;-D USER_SETUP_LOADED=1
-D LGFX_USE_V1=1
-D ILI9341_DRIVER=1
-D TFT_ROTATION=2 ; 0=0, 1=90, 2=180 or 3=270 degree
-D TFT_WIDTH=320
-D TFT_HEIGHT=480
-D TFT_RST=-1
-D TFT_SCLK=14
-D TFT_DC=2
-D TFT_CS=15
-D TFT_MOSI=13
-D TFT_MISO=12
-D TFT_BCKL=27
-D SUPPORT_TRANSACTIONS
-D TOUCH_DRIVER=6336 ; XPT2606 Resistive touch panel driver
-D TOUCH_SDA=33
-D TOUCH_SCL=32
-D TOUCH_IRQ=21 ; not connected
-D TOUCH_RST=25 ; not used, connected to 3.3V
-D TOUCH_FREQUENCY=400000
-D SPI_FREQUENCY=27000000
-D SPI_READ_FREQUENCY=16000000
;endregion
Any Ideas?
Update:
From tech specs found that driver used for capacitive touch is CST820 and register is 0x15
changed the code to match that data, but touch still doesnāt work, guess there are no driver support.
You will need to implement the CST820 driver in openHASP, as this driver is currently not supported.
Yeah we know, any guidance or howto on that, other than trying to work out from existing driver code?
There is no cut-out path to add new drivers. This is basically how drivers are integrated:
- Read the datasheets and example driver code
- Apply that knowledge to existing drivers available in the source code
- Trial and error
- Lots of debugging
- Repeat until it works
I was worried that this was the case. Cheers, Iāll see what happens when I try.
Hi!
I also have just bought the SenseCAP Indicator D1, naively assuming it would work out the box as a Home Assistant dashboard. No matter, I have been looking at information and have stumbled on this thread. By the date of discussion, seems Iām right up at the cutting edge of getting this integration working!
I have not used openHASP before but from what I read thus far it looks doable, and youāve gotten it working on the same hardware 
If I understand correctly, itās not about piping a HA dashboard directly to the device, but rather creating a dashboard for this device and using MQTT to trigger and message to HA?
I want to ask about image display - the intention is to show an image slideshow when the tablet is idle, then upon touch would go to the control panel views. I read on openHASP website that image display is possible but requires additional RAM, intention looks like being image icon on controls rather than photo slideshow.
Note that the Opencap Indicator has a dual ARM Cortex so has more power than the ESP32. Putting openHASP on the Opencap, does that just use the ESP32 and not take advantage of the powerful hardware?
Looking for some general starter advice - is my intention to display photo slideshow possible through openHASP or am I barking up the wrong technology tree entirely?
Thanks!