Skip to content
This repository has been archived by the owner on Oct 1, 2023. It is now read-only.

Two instances #9

Closed
Lockzi opened this issue Oct 6, 2019 · 8 comments
Closed

Two instances #9

Lockzi opened this issue Oct 6, 2019 · 8 comments

Comments

@Lockzi
Copy link

Lockzi commented Oct 6, 2019

Hey,

I have two robots, I've configured ICantBeliveItsNotValetudo for the secondary instance to run on port 3001, but I believe that the robot has problems with connecting to it?

Anyone else running two instances for two robots?
How did you configure it?

@pax2011
Copy link

pax2011 commented Oct 18, 2019

Did you solve this?

@Lockzi
Copy link
Author

Lockzi commented Oct 18, 2019

Nope, got occupied by firmware reset...

Any tips would be helpful!

@hillbicks
Copy link

I'm also wondering about this, but since I just got started with HA, I'll focus on the things that work out of the box.

I suppose we could run two instances of this on the same host with minor changes. Then we can use the different config in two different lovelace cards.

@Apocrathia
Copy link

Apocrathia commented Mar 5, 2020

It would be nice if we could simply specify a wildcard within the configuration (ie prefix/+/map_data) but the application does not understand how to handle it. Additionally, the processed map location is hardcoded to /api/map/image.

@LordMike
Copy link

Eh, you could run two docker containers and duplicate the entire thing. ;)

@dbeltman
Copy link

Eh, you could run two docker containers and duplicate the entire thing. ;)

This. Just map it into a different port with docker and configure a separate MQTT topic for both the second robot and the second instance of ICBINV

@sblasch
Copy link

sblasch commented Jul 9, 2020

This. Just map it into a different port with docker and configure a separate MQTT topic for both the second robot and the second instance of ICBINV

sorry, Noob question: I see, there is a Dockerfile in the repository. Is there also an instruction how to do this? there is no Docker know-how on my side :-(
currently i am running it with nohup npm start &

@sblasch
Copy link

sblasch commented Jul 11, 2020

Solved by myself. but even though i used nearly the same configs only the mqtt name (valetudo/xxx) differs, only the icbinv for the v5 sends a map. the instance for the v1 seems not to work (it get's the raw data from mosquitto but isn't publishing anything)

This is the working instance (v5):
2020-07-11T16:25:20: Received PUBLISH from wischwisch (d0, q0, r1, m0, 'valetudo/wischwisch/map_data', ... (306872 bytes)) 2020-07-11T16:25:20: Sending PUBLISH to mqttjs_c249674b (d0, q0, r0, m0, 'valetudo/wischwisch/map_data', ... (306872 bytes)) 2020-07-11T16:25:21: Received PUBLISH from mqttjs_c249674b (d0, q0, r1, m0, 'valetudo/wischwisch/map', ... (23868 bytes)) 2020-07-11T16:25:21: Sending PUBLISH to homeassistant (d0, q0, r0, m0, 'valetudo/wischwisch/map', ... (23868 bytes))

And this instance don't work (v1):
2020-07-11T17:48:51: Received PUBLISH from mqttjs_e4b515c2 (d0, q0, r1, m0, 'valetudo/nomnom/map_data', ... (932 bytes)) 2020-07-11T17:48:51: Sending PUBLISH to homeassistant (d0, q0, r0, m0, 'valetudo/nomnom/map_data', ... (932 bytes)) 2020-07-11T17:48:51: Sending PUBLISH to mqttjs_ffe23bfb (d0, q0, r0, m0, 'valetudo/nomnom/map_data', ... (932 bytes))

@Hypfer Hypfer closed this as completed Feb 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants