Closed tht closed 1 month ago
Congrats deciding for a Solmate 😃
Yes, you misread one point, maybe you are just too excited and eager to get it 🤣. You need to add the required libraries listed in requirements.txt into appdaemon, see: https://github.com/mmattel/EET-Solmate/blob/main/docs/appdaemon.md#install-appdaemon-as-addon This is quite easy, just not forget to restart appdaemon afterwards...
Let me know how it went.
(Mind to let me know where you are located, just a rough info would be great. Only to get an overview where esham is used)
Got it, thanks a lot.
I think I missed it, because AppDaemon was already installed and running. I was looking trough xxx many times but never went back to the AppDaemon installation.
Now it is looking as expected:
2024-08-28 19:59:38.802949 INFO AppDaemon: Calling initialize() for solmate_0
2024-08-28 19:59:38.825473 INFO solmate_0: Monitoring enabled for solmate_appdaemon_0
2024-08-28 19:59:38.830104 INFO solmate_0: To monitor this Solmate, you need to add an integration in HA manually. Settings -> Devices & Services -> Helpers -> Create Helper. Select the "Toggle (Schalter)" helper and name it: solmate_appdaemon_0 For the icon, select mdi:script-text-play-outline or any other you like. When done, restart Appdaemon. You can now stop and restart esham via HA/Appdaemon.
2024-08-28 19:59:38.832252 INFO AppDaemon: App initialization complete
Websocket: Initializing connection
2024-08-28 19:59:38.845592 INFO solmate_0: Websocket: Initializing connection
Websocket: Create socket
2024-08-28 19:59:38.851617 INFO solmate_0: Websocket: Create socket
Websocket: Connected to: wss://sol.eet.energy:9124/
2024-08-28 19:59:39.047627 INFO solmate_0: Websocket: Connected to: wss://sol.eet.energy:9124/
Websocket: Authenticating
2024-08-28 19:59:39.050310 INFO solmate_0: Websocket: Authenticating
Websocket: Response: {'type': 'DoesNotExist', 'message': ''}
2024-08-28 19:59:39.095961 INFO solmate_0: Websocket: Response: {'type': 'DoesNotExist', 'message': ''}
Websocket: Response: {'type': 'DoesNotExist', 'message': ''}
Websocket: Authentication to <solmate-serial-number> failed!
2024-08-28 19:59:39.101391 INFO solmate_0: Previous message repeated 1 times
2024-08-28 19:59:39.101747 INFO solmate_0: Websocket: Authentication to <solmate-serial-number> failed!
Websocket: Failed creating connection/authentication to class.
2024-08-28 19:59:39.104108 INFO solmate_0: Websocket: Failed creating connection/authentication to class.
Main: Websocket: Connection error - waiting 600s and reconnect.
2024-08-28 19:59:39.107020 INFO solmate_0: Main: Websocket: Connection error - waiting 600s and reconnect.
2024-08-28 19:59:41.847948 INFO AppDaemon: New client Admin Client connected
Fantastic! Again, thank you for the code and also for helping me out.
Great 😃 Have a lot of fun. Let me know if there is anything open. Feedback welcomed, really 😅 or how you use it. Just drop a note in the discussions section.
Hi,
I'm still waiting for my SoulMate but this does not prevent me from trying to install the integration in Home-Assistant 😄. I do not have any AppDaemon experience and I'm struggling during the install process. I'm quite sure I've missed something somewhere.
logs:
andapps:
are added to the corresponding config-files.esham
directory and copied all the files matchingsolmate*.py
.env_0
is created and filled with MQTT configuration (remember, I don't have the SoulMate yet so no serial available)When starting AppDaemon I get this output:
It looks like the Python modules are not available. As per documentation the
requirements.txt
is not needed in AppDaemon installations. But where does AppDaemon get the information about the modules from? Did I miss a step?Thanks!