DigitalOutput en SignalK
Hi, i would like to make a ESP32 module with about 8 digital outputs that can be controlled by SignalK. I've been at it with my best friend (ChatGPT) for days now but my friend and I keep running back and forth between different putrequest objects, but nothing modifyble shows up in the data browser.
Could somewone be so nice to give some pointers? That would be greatly appriciated.
Full disclosure: I also posted this question at the GitHub SensESP discussion group.
Kind regards,
Koen
8 Replies
Nothing would show in the Data Browser that it is modifiable
You can’t modify data in the Data Browser.
Okay, that is correct. But the path that has just been created and shows up in the databrowser cannot be modified in KIP. How would i go about making the path writable in SensESP so that KIP knows the path can be written.
Maybe ask in #sensesp
ChatGPT is total crap for anything outside the simplest stuff. You should install HomeAssistant and ESPHome on your Pi (I assume you're running SignalK on a Pi), preferably in Docker containers, that will give you all you need to control them. I run SignalK and SignalK plug-ins in web page windows in Hass.
Definitely don’t need HomeAssistant for this
Really? Well, then I'm out and as much help as ChatGPT. That's my goto way of doing most stuff. 😆
I don’t know the details on the sensesp side, but it does support digital switching.
I doubt the problem is on the SensESP side. When i make a listener to listen to some sensordata (HDM) i can read the sensor data without any problem. I can get putrequest and putrequestlisteners up and running ... The path just doesn't appear to be writeable if i try to add a button to KIP.
There must be some setting like "write"=true that has to be added in json but i can't find how to do it in the SensESP docs.
I thought this is #sensesp section ... Sorry to bother i'll go there.
I have the problem solved using an example from the SensESP package. I am now able to toggle a LED using a toggle switch in KIP.
A strange thing however is that KIP does not find the path while the toggle switch is selected. The workaround is to select an indicator, then select the path and roll back to the toggle switch and then save the widget. Knowing this, that sounds suspiciously like a KIP flaw.