Même pas avec sudo nano data.py (avec _ avant et après data) ?
Si tu es à jour, tu as la visu ici:https://github.com/Anthony-55/Maestro/blob/master/data.py
Rajoute les _ avant et apres DATA dans le lien !
J’ai réussi a lire le fichier avec _ avant et aprés DATA.
En revanche je ne vois que « Etat du ventilateur d’ambiance », rien par rapport au ventilateur de la sortie canalisé 
Bonjour 
Merci Anthony! Super que ce code existe.
My French is not good enough for me to participate in a discussion here, just wanted to say thanks.
I’m trying to get this to work in OpenHab home automation, it will require some tweaking and (google) translating I suppose.
@kimme; your problem seems to be unrelated to this script. You should probably look for answers elsewhere on internet for your error message. The first step is to get on the network of the stove and be able to ping it: > ping 192.168.120.1
@Chilbald
Thanks for the reply.
EDIT:
In the meantime I fixed the network connection issue and now I can ping to the stove.
However the issue still remains that I’m getting the same error when I try to start up the service…
Also when trying to run it not as a daemon I’m getting this output:
sudo bash install
Installation des dépendances
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: paho-mqtt in /usr/local/lib/python3.7/dist-packages (1.5.0)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: websocket-client in /usr/local/lib/python3.7/dist-packages (0.56.0)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from websocket-client) (1.12.0)
Copie des fichiers necessaires
Lancement du deamon
Anthony L. 2019
Niveau de LOG : DEBUG
Connection en cours au broker MQTT (IP:127.0.0.1 PORT:1883)
Traceback (most recent call last):
File "/opt/maestro/maestro.py", line 153, in <module>
client.connect(_MQTT_ip, _MQTT_port)
File "/usr/local/lib/python3.7/dist-packages/paho/mqtt/client.py", line 937, in connect
return self.reconnect()
File "/usr/local/lib/python3.7/dist-packages/paho/mqtt/client.py", line 1071, in reconnect
sock = self._create_socket_connection()
File "/usr/local/lib/python3.7/dist-packages/paho/mqtt/client.py", line 3522, in _create_socket_connection
return socket.create_connection(addr, source_address=source, timeout=self._keepalive)
File "/usr/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
1 « J'aime »
@kimme1024 your error message is about the connection with the mqtt broker. You should probably try to get a mqtt broker up and running first. Does homebridge have one built in?
Personally i use mosquitto for broker, and you can test the connection from bash in raspberry using mosquitto_sub and pub commands.
a good read:
@Chibald thanks man! I got the plugin running now and I can see it extracting data from the stove.
Now it’s just the case of converting that data into something that homebridge can see…
I’m very interested in what you already made. I don’t know it can be ported to homebridge?
EDIT:
I installed Jeedom on the RPi just to make sure everything works, and it does! As I don’t have any knowledge of Jeedom I can’t get it to display all the data on the dashboard but that isn’t what I’m looking for anyway.
The only thing left is to be able to read the plugin’s output into an MQTT plugin from homebridge… I’d only need current ambient temperature, and the basic controls for the stove (on/off) and temperature-select as I only use the stove in dynamic mode.
@MoMoPouetFoFo
Do you have any luck connecting the plugin to homebridge?
Est-ce que vous avez trouvé une solution pour connecter avec homebridge?
1 « J'aime »
@kimme1024 i don’t have anything really usefull right now. I’ll let you know when I have.
Also, something strange occured. My stove suddenly is on a whole different IP range; the ip address of the stove is right now 192.168.244.1.
c’est bizarre?
@Chibald that’s weird indeed!
As for the config.json, I think we can adapt the thermostat template as it mostly links with what we want to do.
{
"accessory": "mqttthing",
"type": "thermostat",
"name": "<name of device>",
"url": "<url of MQTT server (optional)>",
"username": "<username for MQTT (optional)>",
"password": "<password for MQTT (optional)>",
"topics":
{
"getCurrentHeatingCoolingState": "<topic used to report 'current heating/cooling state'>",
"setTargetHeatingCoolingState": "<topic used to control 'target heating/cooling state'>",
"getTargetHeatingCoolingState": "<topic used to report 'target heating/cooling state'>",
"getCurrentTemperature": "<topic used to report 'current temperature'>",
"setTargetTemperature": "<topic used to control 'target temperature'>",
"getTargetTemperature": "<topic used to report 'target temperature'>",
"setTemperatureDisplayUnits": "<topic used to control 'temperature display units'>",
"getTemperatureDisplayUnits": "<topic used to report 'temperature display units'>",
"getCurrentRelativeHumidity": "<topic used to report 'current relative humidity' (optional)>",
"setTargetRelativeHumidity": "<topic used to control 'target relative humidity' (optional)>",
"getTargetRelativeHumidity": "<topic used to report 'target relative humidity' (optional)>",
"setCoolingThresholdTemperature": "<topic used to control 'cooling threshold temperature' (optional)>",
"getCoolingThresholdTemperature": "<topic used to report 'cooling threshold temperature' (optional)>",
"setHeatingThresholdTemperature": "<topic used to control 'heating threshold temperature' (optional)>",
"getHeatingThresholdTemperature": "<topic used to report 'heating threshold temperature' (optional)>"
},
"heatingCoolingStateValues": "<array of values to be used to represent Off, Heat, Cool and Auto respectively (optional)>",
"temperatureDisplayUnitsValues": "<array of values to be used to represent Celsius and Fahrenheit respectively (optional)>",
"minTemperature": minimum_target_temperature,
"maxTemperature": maximum_taret_temperature,
"restrictHeatingCoolingState": "<array of allowed values - see notes above (optional)>"
}
The only thing we need to know now is which topics that are used for the plugin so we can subscribe to them in the config.json file.
Currently I’m testing this (topic from Jeedom)
{
"accessory": "mqttthing",
"type": "thermostat",
"name": "MCZ VIVO 90",
"url": "mqtt://192.168.1.157:1883",
"topics": {
"getCurrentTemperature": "PUBmcz{Température ambiante}"
}
}
It shows up in homekit but it doesn’t display the temperature value. Instead it’s 0 degrees.
I assume this means that I’m using the wrong topic…
1 « J'aime »
Bonjour,
je souhaiterais avoir l’info si on ets en mode silence ou non. on sait transmettre l’info, mais comment récupérer l’état de ce mode ?
@Chibald @MoMoPouetFoFo
I got it working well enough for now, big thanks to a great friend of mine for his help!
You can use the mqttthing thermostat template to check ambient temp, on/off and desired temp:
{
"accessory": "mqttthing",
"type": "thermostat",
"name": "MCZ VIVO 90",
"logmqtt": true,
"url": "mqtt://192.168.1.211:1883",
"topics": {
"getCurrentTemperature": {
"topic": "PUBmcz",
"apply": "return JSON.parse(message)['Température ambiante'].toFixed(1);"
},
"setTargetHeatingCoolingState": {
"topic": "SUBmcz",
"apply": "return message == 'HEAT' ? '34,1' : '34,40';"
},
"setTargetTemperature": {
"topic": "SUBmcz",
"apply": "return \"42,\"+message;"
}
}
},
If your a graph-enthousiast like me you can add a second accessory with fakegato support for the eve app with the temperatureSensor template:
{
"accessory": "mqttthing",
"type": "temperatureSensor",
"name": "Veranda",
"logmqtt": true,
"history": true,
"url": "mqtt://192.168.1.211:1883",
"topics": {
"getCurrentTemperature": {
"topic": "PUBmcz",
"apply": "return JSON.parse(message)['Température ambiante'].toFixed(1);"
}
}
}
1 « J'aime »
Je pense que c’est le numéro 24.
insérer dans _data_py:
[24, « Mode silencieux »]
L’info est remontée par le paramètre 49 (0: Mode silencieux, 1: Bips activés)
Bonjour a tous,
Je cherche un moyen de sauvegarder dans un historique l’information de l’état du poêle. (puissance 1…4 etc)
Sauf que comme il y a du texte, jeedom n’y arrive pas. Comme faire pour avoir puissance1=1, puissance5=5, éteins=0 ?
Anthony, Je parlais du mode silencieux du poêle au niveau de la ventilation, pas des bip de configurations.
Ok je vais essayer cela
Ok super cela marche j’ai ajouté dans le data silencieux en 24 merci
bonjour,
j’essaye depuis hier de lancer le stript install_daemon il install bien mais lors du lancement du maestro.service il me marque ca:
Job for maestro.service failed because the control process exited with error code.
See « systemctl status maestro.service » and « journalctl -xe » for details.
lorque je lance status maestro il me dit/
maestro.service - Passerelle Equipements MCZ Maestro avec serveur MQTT
Loaded: loaded (/etc/systemd/system/maestro.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-01-10 19:54:45 CET; 36s ago
Process: 15935 ExecStart=/usr/bin/python /opt/maestro/maestro.py (code=exited, status=1/
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Service RestartSec=100ms expire
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Scheduled restart job, restart
janv. 10 19:54:45 raspberrypi systemd[1]: Stopped Passerelle Equipements MCZ Maestro avec
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Start request repeated too quic
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Failed with result ‹ exit-code ›.
janv. 10 19:54:45 raspberrypi systemd[1]: Failed to start Passerelle Equipements MCZ Maest
lines 1-11/11 (END)…skipping…
● maestro.service - Passerelle Equipements MCZ Maestro avec serveur MQTT
Loaded: loaded (/etc/systemd/system/maestro.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-01-10 19:54:45 CET; 36s ago
Process: 15935 ExecStart=/usr/bin/python /opt/maestro/maestro.py (code=exited, status=1/FAILURE)
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Service RestartSec=100ms expired, scheduling restart.
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Scheduled restart job, restart counter is at 5.
janv. 10 19:54:45 raspberrypi systemd[1]: Stopped Passerelle Equipements MCZ Maestro avec serveur MQTT.
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Start request repeated too quickly.
janv. 10 19:54:45 raspberrypi systemd[1]: maestro.service: Failed with result ‹ exit-code ›.
janv. 10 19:54:45 raspberrypi systemd[1]: Failed to start Passerelle Equipements MCZ Maestro avec serveur MQTT.
j’ai reinstaller buster avec les paho-mqtt python et websocket et le probleme et pareil. J’ai aussi remarquer que j’ai pas le dossier /etc/init.d/maestro
Si quelqu’un a une solution je suis preneur.
florian
re,
apres plusieurs essai et lecture du programme fait par anthony.J’ai pas le droit pour ecrit dans le dossier maestro un chmod m’a permis de regler le probleme.
merci anthony pour le programme.
florian
Hi @kimme1024,
Sorry for the late, I didn’t see your post.
Honestly, I give up to implement the temp.
I just created to virtual for Eco and timer switch.
And I only display the temp.
If I may have some time to be watching again mqttthinq. But I had a little trouble to understanding the functioning of this plugin.
M.