Allowing http request parameters

[linker3000]

Could the app be made to cope with config strings that include parse-able parameters, for example:

- nk,NK-Desktop5
  -- d_on,on,/watch?type=mqtt&trigger=cmnd&device=RELAY193&command=power&value=on
  -- d_off,off,/watch?type=mqtt&trigger=cmnd&device=RELAY193&command=power&value=off
  -- d_toggle,toggle,/watch?type=mqtt&trigger=cmnd&device=RELAY193&command=power&value=toggle

That would be really cool!

Thanks

[cmader]

Adding query parameters to the URL should actually work, I will test that. However, at the moment I'm doing a full code refactoring of the app so this might take some time...

[linker3000]

No rush. At the moment I am passing parameters in the URL and this works fine, but just looks a bit odd!

- nk,NK-Desktop6
-- nko,NK Office
--- d_on#green,ON,/watch/type~mqtt/trigger~cmnd/device~RELAY193/command~power/value~on
--- d_off#red,OFF,/watch/type~mqtt/trigger~cmnd/device~RELAY193/command~power/value~off
--- d_toggle,toggle,/watch/type~mqtt/trigger~cmnd/device~RELAY193/command~power/value~toggle
-- ldg#green, Landing
--- ldg_on#green,ON,/watch/type~ldg/command~on
--- ldg_off#red,OFF,/watch/type~ldg/command~off
-- lng#yellow, Ducal
--- sfa_on#green,ON,/watch/type~mqtt/trigger~cmnd/device~RELAY175/command~power/value~on
--- sfa_off#red,OFF,/watch/type~mqtt/trigger~cmnd/device~RELAY175/command~power/value~off

Looking forward to see whether the refactoring brings any new features. Let me know if I can help with end-user testing.

[cmader]

Hi! I added v2.0.0_RC1 version of the app to this repo. No really new features right now, most things have happened behind the scenes like improved performance, encrypted storage of settings, usage of the current Material 3 UI components, and so on. It's now much easier to maintain the project for future feature requests. I checked with the new version and it seems that query parameters that you mention in your first comment are actually sent and can be interpreted by the server.

[cynik606]

Hi! I added v2.0.0_RC1 version of the app to this repo. No really new features right now, most things have happened behind the scenes like improved performance, encrypted storage of settings, usage of the current Material 3 UI components, and so on. It's now much easier to maintain the project for future feature requests. I checked with the new version and it seems that query parameters that you mention in your first comment are actually sent and can be interpreted by the server.

The previous version 1.7.1 must be uninstalled first? When I try to update it directly it fails:

[linker3000]

Hi! I added v2.0.0_RC1 version of the app to this repo. No really new features right now, most things have happened behind the scenes like improved performance, encrypted storage of settings, usage of the current Material 3 UI components, and so on. It's now much easier to maintain the project for future feature requests. I checked with the new version and it seems that query parameters that you mention in your first comment are actually sent and can be interpreted by the server.

Thanks for the update. I'll try it out and check out sending query parameters.

Here's my complementary project based on Node-RED:

https://codeberg.org/linker3000/SmartBop

[cmader]

Hi! I added v2.0.0_RC1 version of the app to this repo. No really new features right now, most things have happened behind the scenes like improved performance, encrypted storage of settings, usage of the current Material 3 UI components, and so on. It's now much easier to maintain the project for future feature requests. I checked with the new version and it seems that query parameters that you mention in your first comment are actually sent and can be interpreted by the server.

The previous version 1.7.1 must be uninstalled first? When I try to update it directly it fails:

Right, sorry for that. The way of persisting the config has changed, so when using the release candidates it's better to uninstall the old version first.

[cmader]

Hi! I added v2.0.0_RC1 version of the app to this repo. No really new features right now, most things have happened behind the scenes like improved performance, encrypted storage of settings, usage of the current Material 3 UI components, and so on. It's now much easier to maintain the project for future feature requests. I checked with the new version and it seems that query parameters that you mention in your first comment are actually sent and can be interpreted by the server.

Thanks for the update. I'll try it out and check out sending query parameters.

Here's my complementary project based on Node-RED:

https://codeberg.org/linker3000/SmartBop

Cool, I'm also using Node-RED in my home automation setup, I'm very happy with it's flexibility. I was able to retrieve the query parameter from the URL in the msg.req.query structure in the "HTTP In" node which gives me hope that it might work in your setup as well.