Automate Mbus M Bus HTTPD
HumDay reads Mbus M Bus HTTPD’s own published API description and derives 7 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in Mbus M Bus HTTPD
5 documented operations change something in Mbus M Bus HTTPD.
- POSTTurns on power to the M-Bus
/mbus/hat/on - POSTTurns off power to the M-Bus
/mbus/hat/off - POSTScan the specified device for slaves
/mbus/scan/{device}/{baudrate} - POSTGets data from the slave identified by {address}
/mbus/get/{device}/{baudrate}/{address} - POSTGets data from the slave identified by {address}, and supports multiple responses from the slave
/mbus/getMulti/{device}/{baudrate}/{address}/{maxframes}
What HumDay can read from Mbus M Bus HTTPD
These are the operations a schedule or a trigger can watch.
- GETReturns this API specification
/mbus/api - GETGets Raspberry Pi Hat information
/mbus/hat
How automating Mbus M Bus HTTPD works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Mbus M Bus HTTPD account.
- Grant access, then go live. You approve the specific Mbus M Bus HTTPD operations it may use — and only those.
Automate Mbus M Bus HTTPD with these
- Gambitcomm MIMIC356 operations
- Meraki Dashboard263 operations
- ClearBlade220 operations
- Influxdata Influx OSS197 operations
- Intellifi Brain77 operations
- Adafruit IO71 operations
- Ijenko IoE² IoT to create end user applications67 operations
- smart me64 operations
- Opto22 PAC Control55 operations
- KeyServ24 operations
- Hardware Sentry TrueSight Presentation Server23 operations
- Netatmo19 operations
Categories
Questions about Mbus M Bus HTTPD automation
- Can HumDay connect to Mbus M Bus HTTPD?
- Yes. HumDay reads Mbus M Bus HTTPD's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 7 operations are documented.
- Do I need to write code to automate Mbus M Bus HTTPD?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Mbus M Bus HTTPD account.
- What can HumDay do in Mbus M Bus HTTPD?
- 5 of the 7 documented operations change something in Mbus M Bus HTTPD, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Mbus M Bus HTTPD account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Mbus M Bus HTTPD is held behind that approval.
Where this came from
The operations above are read from a published API description for Mbus M Bus HTTPD at raw.githubusercontent.com/packom/mbus-api/master/api/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.