search

bbqkees / ems-esp-domoticz-plugin

Domoticz plugin for the EMS Wi-Fi Gateway with Proddy's EMS-ESP firmware
MIT License
7 stars 8 forks source link

With domoticz 2020.2, device list is empty #18

Closed jvm1000 closed 4 years ago

jvm1000 commented 4 years ago

Known issues

! Issue with latest Domoticz versions !

in my case that happens with a fresh installation of raspios-buster and domoticz stable version when activating the plugin the entire device list in Domoticz gets empty after a while if i disable or delete the hardware EMS gateway then appears the rest of the devices after create a new EMS gateway all devices appears and stay ok for near 3 minutes

this is the domoticz log EMS version 1.9.5

2020-09-10 17:47:19.392 (EMS) Creating device 'EMS thermostat setpoint HC3'. 2020-09-10 17:47:19.393 (EMS) Create Thermostat Setpoint Device HC4 2020-09-10 17:47:19.393 (EMS) Creating device 'EMS thermostat setpoint HC4'. 2020-09-10 17:47:19.394 (EMS) Create Thermostat mode selector HC1 2020-09-10 17:47:19.394 (EMS) Creating device 'Thermostat mode HC1'. 2020-09-10 17:47:19.395 (EMS) Create Thermostat mode selector HC2 2020-09-10 17:47:19.395 (EMS) Creating device 'Thermostat mode HC2'. 2020-09-10 17:47:19.396 (EMS) Create Thermostat mode selector HC3 2020-09-10 17:47:19.396 (EMS) Creating device 'Thermostat mode HC3'. 2020-09-10 17:47:19.397 (EMS) Create Thermostat mode selector HC4 2020-09-10 17:47:19.397 (EMS) Creating device 'Thermostat mode HC4'. 2020-09-10 17:47:19.398 (EMS) Create boiler mode selector 2020-09-10 17:47:19.399 (EMS) Creating device 'Boiler mode'. 2020-09-10 17:47:19.400 (EMS) Create ww mode selector 2020-09-10 17:47:19.400 (EMS) Creating device 'ww mode'. 2020-09-10 17:47:19.401 (EMS) Create on/off switch (tapwater active) 2020-09-10 17:47:19.401 (EMS) Creating device 'Tapwater active'. 2020-09-10 17:47:19.402 (EMS) Create on/off switch (heating active) 2020-09-10 17:47:19.402 (EMS) Creating device 'Heating active'. 2020-09-10 17:47:19.402 (EMS) Create on/off switch (Gateway online/offline) 2020-09-10 17:47:19.402 (EMS) Creating device 'Gateway online'. 2020-09-10 17:47:19.403 (EMS) Topiclist is: 2020-09-10 17:47:19.403 (EMS) home/ems-esp/thermostat_data, home/ems-esp/boiler_data, home/ems-esp/sensors, home/ems-esp/mixing_data, home/ems-esp/sm_data, home/ems-esp/hp_data, home/ems-esp/heating_active, home/ems-esp/tapwater_active 2020-09-10 17:47:19.404 (EMS) MqttClient::init 2020-09-10 17:47:19.404 (EMS) MqttClient::Open 2020-09-10 17:47:19.454 (EMS) MqttClient::onConnect 2020-09-10 17:47:19.454 (EMS) Successful connect to: 127.0.0.1:1883 2020-09-10 17:47:19.454 (EMS) MqttClient::Connect 2020-09-10 17:47:19.454 (EMS) MQTT CONNECT ID: 'Domoticz_1599752839' 2020-09-10 17:47:19.505 (EMS) onMQTTConnected 2020-09-10 17:47:19.505 (EMS) MqttClient::Subscribe 2020-09-10 17:47:19.505 (EMS) onMessage called with: CONNACK 2020-09-10 17:47:19.555 (EMS) onMQTTSubscribed 2020-09-10 17:47:19.555 (EMS) onMessage called with: SUBACK 2020-09-10 17:47:19.193 Status: (EMS) Started. 2020-09-10 17:47:19.357 Status: (EMS) Entering work loop. 2020-09-10 17:47:19.358 Status: (EMS) Initialized version 1.0 2020-09-10 17:47:29.376 (EMS) Heartbeating... 2020-09-10 17:47:29.377 (EMS) MqttClient::Ping 2020-09-10 17:47:29.427 (EMS) onMessage called with: PINGRESP 2020-09-10 17:47:39.394 (EMS) Heartbeating... 2020-09-10 17:47:39.394 (EMS) MqttClient::Ping 2020-09-10 17:47:39.445 (EMS) onMessage called with: PINGRESP 2020-09-10 17:47:49.364 (EMS) Heartbeating... 2020-09-10 17:47:49.364 (EMS) MqttClient::Ping 2020-09-10 17:47:49.414 (EMS) onMessage called with: PINGRESP 2020-09-10 17:47:59.382 (EMS) Heartbeating... 2020-09-10 17:47:59.382 (EMS) MqttClient::Ping 2020-09-10 17:47:59.433 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:09.402 (EMS) Heartbeating... 2020-09-10 17:48:09.402 (EMS) MqttClient::Ping 2020-09-10 17:48:09.453 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:19.371 (EMS) Heartbeating... 2020-09-10 17:48:19.372 (EMS) MqttClient::Ping 2020-09-10 17:48:19.422 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:29.393 (EMS) Heartbeating... 2020-09-10 17:48:29.393 (EMS) MqttClient::Ping 2020-09-10 17:48:29.443 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:39.413 (EMS) Heartbeating... 2020-09-10 17:48:39.413 (EMS) MqttClient::Ping 2020-09-10 17:48:39.463 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:49.380 (EMS) Heartbeating... 2020-09-10 17:48:49.380 (EMS) MqttClient::Ping 2020-09-10 17:48:49.431 (EMS) onMessage called with: PINGRESP 2020-09-10 17:48:59.399 (EMS) Heartbeating... 2020-09-10 17:48:59.399 (EMS) MqttClient::Ping 2020-09-10 17:48:59.450 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:09.420 (EMS) Heartbeating... 2020-09-10 17:49:09.420 (EMS) MqttClient::Ping 2020-09-10 17:49:09.471 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:19.391 (EMS) Heartbeating... 2020-09-10 17:49:19.391 (EMS) MqttClient::Ping 2020-09-10 17:49:19.442 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:29.411 (EMS) Heartbeating... 2020-09-10 17:49:29.411 (EMS) MqttClient::Ping 2020-09-10 17:49:29.462 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:39.432 (EMS) Heartbeating... 2020-09-10 17:49:39.432 (EMS) MqttClient::Ping 2020-09-10 17:49:39.482 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:49.402 (EMS) Heartbeating... 2020-09-10 17:49:49.403 (EMS) MqttClient::Ping 2020-09-10 17:49:49.453 (EMS) onMessage called with: PINGRESP 2020-09-10 17:49:59.421 (EMS) Heartbeating... 2020-09-10 17:49:59.421 (EMS) MqttClient::Ping 2020-09-10 17:49:59.472 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:00.405 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 38, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:00.405 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 39, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:00.406 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 40, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:00.406 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 41, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:00.407 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 42, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:00.407 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 43, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 17:50:09.390 (EMS) Heartbeating... 2020-09-10 17:50:09.391 (EMS) MqttClient::Ping 2020-09-10 17:50:09.441 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:19.411 (EMS) Heartbeating... 2020-09-10 17:50:19.411 (EMS) MqttClient::Ping 2020-09-10 17:50:19.462 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:29.432 (EMS) Heartbeating... 2020-09-10 17:50:29.432 (EMS) MqttClient::Ping 2020-09-10 17:50:29.483 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:39.403 (EMS) Heartbeating... 2020-09-10 17:50:39.403 (EMS) MqttClient::Ping 2020-09-10 17:50:39.454 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:40.096 Error: WebServer PO exception occurred : 'stoull' 2020-09-10 17:50:49.423 (EMS) Heartbeating... 2020-09-10 17:50:49.423 (EMS) MqttClient::Ping 2020-09-10 17:50:49.474 (EMS) onMessage called with: PINGRESP 2020-09-10 17:50:59.443 (EMS) Heartbeating... 2020-09-10 17:50:59.443 (EMS) MqttClient::Ping 2020-09-10 17:50:59.494 (EMS) onMessage called with: PINGRESP 2020-09-10 17:51:09.413 (EMS) Heartbeating... 2020-09-10 17:51:09.414 (EMS) MqttClient::Ping

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////// this is another domoticz log

EMS version V2 with a 18b20 temperature sensor

2020-09-10 18:34:39.296 (ems) MqttClient::Ping 2020-09-10 18:34:39.347 (ems) onMessage called with: PINGRESP 2020-09-10 18:34:40.449 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.93"}}' 2020-09-10 18:34:40.449 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:34:40.449 (ems) onMessage called with: PUBLISH 2020-09-10 18:34:49.267 (ems) Heartbeating... 2020-09-10 18:34:49.267 (ems) MqttClient::Ping 2020-09-10 18:34:49.318 (ems) onMessage called with: PINGRESP 2020-09-10 18:34:50.470 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.93"}}' 2020-09-10 18:34:50.471 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:34:50.471 (ems) onMessage called with: PUBLISH 2020-09-10 18:34:59.286 (ems) Heartbeating... 2020-09-10 18:34:59.286 (ems) MqttClient::Ping 2020-09-10 18:34:59.336 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:00.539 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:00.539 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:00.539 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:00.070 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 38, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:00.070 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 39, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:00.071 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 40, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:00.071 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 41, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:00.071 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 42, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:00.072 Error: UpdateMeter: Error converting sValue/sUsage! (IDX: 43, sValue: '', sUsage: '0', dType: 113, sType: 0) 2020-09-10 18:35:09.305 (ems) Heartbeating... 2020-09-10 18:35:09.305 (ems) MqttClient::Ping 2020-09-10 18:35:09.355 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:10.608 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:10.608 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:10.608 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:19.274 (ems) Heartbeating... 2020-09-10 18:35:19.274 (ems) MqttClient::Ping 2020-09-10 18:35:19.324 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:20.477 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:20.477 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:20.477 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:29.294 (ems) Heartbeating... 2020-09-10 18:35:29.294 (ems) MqttClient::Ping 2020-09-10 18:35:29.345 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:30.497 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:30.497 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:30.498 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:39.313 (ems) Heartbeating... 2020-09-10 18:35:39.314 (ems) MqttClient::Ping 2020-09-10 18:35:39.364 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:40.567 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:40.567 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:40.567 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:49.284 (ems) Heartbeating... 2020-09-10 18:35:49.284 (ems) MqttClient::Ping 2020-09-10 18:35:49.334 (ems) onMessage called with: PINGRESP 2020-09-10 18:35:50.437 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.87"}}' 2020-09-10 18:35:50.437 (ems) deviceId 221 value has not changed. Device not updated 2020-09-10 18:35:50.437 (ems) onMessage called with: PUBLISH 2020-09-10 18:35:59.305 (ems) Heartbeating...

bbqkees commented 4 years ago

Can you open plugin.py (sudo nano plugin.py in the right directory) and remove in the line near the bottom self.topicsList = list(["thermostat_data", "boiler_data", "sensors", "mixing_dat..... The topic: "boiler_data",

its strange that it gives an error on updating the meters because I don't have the problem here. let's see if that topic causes the error.

jvm1000 commented 4 years ago

now i create a new hardware ems2 and i delete meter quickly and is running wait some minutes

jvm1000 commented 4 years ago

it is working well without meters i also add all temperature devices and still working

bbqkees commented 4 years ago

Can you install http://mqtt-explorer.com/ and post the payload of boiler_data? There is a button 'Value' that will copy the whole message to the clipboard. image

You need to connect it to the IP of your MQTT server/broker.

jvm1000 commented 4 years ago

i stop domoticz sudo systemctl stop domoticz sudo nano plugin.py delete "boiler_data",

    # self.topicsList = list(["thermostat_data", "boiler_data", "sensors", "mixing_data", "sm_data", "hp_data", "heating_active", "tapwater_active"])
    self.topicsList = list(["thermostat_data", "sensors", "mixing_data", "sm_data", "hp_data", "heating_active", "tapwater_active"])

sudo systemctl start domoticz delete old ems2 working well without meters create new ems4 works only a few minutes

jvm1000 commented 4 years ago

i do not know how to install http://mqtt-explorer.com/ in the raspberry i do not have the EMS hardware conected to any boiler, i only have a ds18b20

pi@emonpi:~ $ sudo apt-get install mosquitto-clients pi@emonpi:~ $ mosquitto_sub -v -u 'emonpi' -P 'emonpimqtt2016' -t '#' ems-esp/status online ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/heartbeat {"rssid":100,"uptime":"000+01:03:01.126","uptime_sec":3781,"freemem":83,"mqttpublishfails":0,"txfails":0,"rxfails":3} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/heartbeat {"rssid":100,"uptime":"000+01:04:01.127","uptime_sec":3841,"freemem":83,"mqttpublishfails":0,"txfails":0,"rxfails":3} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.93"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/heartbeat {"rssid":100,"uptime":"000+01:05:01.128","uptime_sec":3901,"freemem":83,"mqttpublishfails":0,"txfails":0,"rxfails":3} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.93"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"30.0"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"34.6"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"33.6"}} ems-esp/sensors {"sensor1":{"id":"28-274C-79A2-0003-85","temp":"32.11"}}

was that what you need?

bbqkees commented 4 years ago

Using EMS-ESP just for the DS18B20 that's a first :-)

If you don't have the EMS hardware you cannot get a boiler_data topic. So when you removed the meters in 'ems2', what exactly did you do?

jvm1000 commented 4 years ago

I bought 2 EMS hardware and they are going to be installed in some days, in boiler´s friends, now i am only playing with them.

To delete the meters in domoticz, i go to devises, search for the 6 meters, select all of them and press delete icon at the top left corner (it is a trash can icon)

i have installed http://mqtt-explorer.com/ , it is a good program, thanks as you said there is no boiler_data topic

jvm1000 commented 4 years ago

a funny thing I have a micro sd card with a domoticz 2020.2 that works fine with EMS hardware, with 1.9.5 and with V2 , it was updated from a previous version of domoticz if you want i can try to see that you want

bbqkees commented 4 years ago

The Linux version on the SD card is then likely based on Raspbian Stretch and not Buster.

maxverstappen commented 4 years ago

Same problem here. reverted the database to a previous version. SD card is on Buster (upgraded) I only have the onMessage called with: PINGRESP message

jvm1000 commented 4 years ago

i have done severals installations, with Stretch, Buster, from scrash and also updating I am not able to find a pattern to know why one works and another does not

        This microSD works fine with the 6 meters in domoticz 2020.2 and BUSTER

pi@emonpi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" pi@emonpi:~ $ hostnamectl Static hostname: emonpi Icon name: computer Machine ID: 6cdeb89296d5413097cd476ea2d06f59 Boot ID: 1d7ccaa4d75c425dbb941b19fbdf8db4 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 4.19.118-v7+ Architecture: arm pi@emonpi:~ $

//////////////////////////////////////////////////////////////////////////////// This is another microSD and works fine with the 6 meters in domoticz 2020.2 and BUSTER

pi@emonpi:~ $ hostnamectl Static hostname: emonpi Icon name: computer Machine ID: 6cdeb89296d5413097cd476ea2d06f59 Boot ID: 1afb016c0dfc4b44851d10ba2e3be4fc Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 4.19.118-v7+ Architecture: arm pi@emonpi:~ $ 

        now i update with apt-get update, and apt-get upgrade and reboot

pi@emonpi:~ $ hostnamectl Static hostname: emonpi Icon name: computer Machine ID: 6cdeb89296d5413097cd476ea2d06f59 Boot ID: 2caf3f59846240e7a3410625c34c273c Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.4.51-v7+ Architecture: arm pi@emonpi:~ $ 

        and still working, next are information of the system

EMONCMS Versión low-write 10.2.6

Modules Administration | App v2.1.8 | Backup v2.2.4 | EmonHub Config v2.0.5 | Dashboard v2.0.8 | DemandShaper v1.2.6 | Device v2.0.6 | EventProcesses | Feed | Graph v2.0.9 | Input | Postprocess v2.1.4 | CoreProcess | Schedule | Network Setup v1.0.0 | Time | User | Visualisation | WiFi v2.0.3 Git URL https://github.com/emoncms/emoncms.git Branch * stable Describe 10.2.5-3-gf781bed0

SERVER OS Linux 5.4.51-v7+ Host emonpi | emonpi | (127.0.0.1) Date 2020-09-12 17:55:20 CEST Uptime 17:55:20 up 8 min, 2 users, load average: 0,79, 0,56, 0,32

HTTP Server Apache/2.4.38 (Raspbian) HTTP/1.1 CGI/1.1 80 MYSQL Versión 5.5.5-10.3.23-MariaDB-0+deb10u1 Host localhost:6379 (127.0.0.1) Date 2020-09-12 17:55:20 (UTC 02:00‌​) Stats Uptime: 478 Threads: 13 Questions: 192 Slow queries: 0 Opens: 45 Flush tables: 1 Open tables: 39 Queries per second avg: 0.401

REDIS Versión Redis Server 5.0.3 PHP Redis 5.2.1 Host localhost:6379 Size 29 keys (780.18K) Uptime 0 days

MQTT SERVER Versión Mosquitto 1.5.7 Host localhost:1883 (127.0.0.1) PHP Versión 7.3.19-1~deb10u1 (Zend Version 3.3.19)

Modules apache2handler calendar Core ctype curl date dom v20031129 exif fileinfo filter ftp gd gettext hash iconv json v1.7.0 libxml mbstring mosquitto v0.4.0 mysqli mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $ openssl pcre PDO pdo_mysql Phar posix readline redis v5.2.1 Reflection session shmop SimpleXML sockets sodium SPL standard sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter xsl Zend OPcache zlib

PI Model Raspberry Pi 3 Model B+ Rev 1.3 - 1GB (Sony UK) RebootShutdown Serial num. DD42754A CPU Temperature 54.77°C GPU Temperature 54.2°C emonpiRelease emonSD-02Oct19 File-system read-write ////////////////////////////////////////////////////////////////////////////////

this one does not work and is a Stretch and domoticz 4.97

pi@RPI3plusVALLEJERTE:~ $ hostnamectl Static hostname: RPI3plusVALLEJERTE Icon name: computer Machine ID: 2f3751f44d134117b60eade7edf8ccee Boot ID: 4370b733be0b486792cd3d8eb14ead5b Operating System: Raspbian GNU/Linux 9 (stretch) Kernel: Linux 4.14.89-v7+ Architecture: arm pi@RPI3plusVALLEJERTE:~ $

2020-09-11 13:42:11.630 Status: Domoticz V4.9700 (c)2012-2018 GizMoCuz 2020-09-11 13:42:11.647 Status: Build Hash: a3a45906, Date: 2018-06-23 16:24:51 2020-09-11 13:42:11.662 Status: Startup Path: /home/pi/domoticz/ 2020-09-11 13:42:12.088 Status: EventSystem: reset all events... 2020-09-11 13:42:13.847 Status: PluginSystem: Started, Python version '3.5.3'. 2020-09-11 13:42:13.956 Status: WebServer(HTTP) started on address: :: with port 8080 2020-09-11 13:42:14.238 Status: WebServer(SSL) started on address: :: with port 443 2020-09-11 13:42:14.241 Status: Proxymanager started. 2020-09-11 13:42:14.243 Status: TCPServer: shared server started... 2020-09-11 13:42:14.244 Status: RxQueue: queue worker started... 2020-09-11 13:42:16.245 Status: EventSystem: reset all events... 2020-09-11 13:42:16.245 Status: EventSystem: reset all device statuses... 2020-09-11 13:42:16.270 Status: PluginSystem: Entering work loop. 2020-09-11 13:42:16.457 Status: Python EventSystem: Initalizing event module. 2020-09-11 13:42:16.458 Status: EventSystem: Started 2020-09-11 13:42:16.458 Status: EventSystem: Queue thread started... 2020-09-11 13:43:13.921 Status: Incoming connection from: 192.168.0.15 2020-09-11 13:46:36.052 Status: EventSystem: reset all device statuses... 2020-09-11 13:47:17.373 Status: (ems) Started. 2020-09-11 13:47:17.671 Status: (ems) Entering work loop. 2020-09-11 13:47:17.671 Status: (ems) Initialized version 1.0 2020-09-11 13:47:42.948 Status: EventSystem: reset all device statuses... 2020-09-11 13:47:45.244 Status: EventSystem: reset all device statuses... 2020-09-11 13:47:54.279 Status: EventSystem: reset all device statuses... 2020-09-11 13:48:00.824 Status: EventSystem: reset all device statuses... 2020-09-11 13:48:06.129 Status: EventSystem: reset all device statuses... 2020-09-11 13:50:17.201 (ems) MqttClient::Ping 2020-09-11 13:50:17.201 (ems) onMessage called with: PINGRESP 2020-09-11 13:50:27.217 (ems) Heartbeating... 2020-09-11 13:50:27.218 (ems) MqttClient::Ping 2020-09-11 13:50:27.218 (ems) onMessage called with: PINGRESP 2020-09-11 13:50:36.584 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.30"}}' 2020-09-11 13:50:36.584 (ems) deviceId 221 value has not changed. Device not updated 2020-09-11 13:50:36.584 (ems) onMessage called with: PUBLISH 2020-09-11 13:50:37.235 (ems) Heartbeating... 2020-09-11 13:50:37.236 (ems) MqttClient::Ping 2020-09-11 13:50:37.236 (ems) onMessage called with: PINGRESP 2020-09-11 13:50:47.253 (ems) Heartbeating... 2020-09-11 13:50:47.253 (ems) MqttClient::Ping 2020-09-11 13:50:47.253 (ems) onMessage called with: PINGRESP 2020-09-11 13:50:57.219 (ems) Heartbeating... 2020-09-11 13:50:57.219 (ems) MqttClient::Ping 2020-09-11 13:50:57.220 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:06.737 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.25"}}' 2020-09-11 13:51:06.737 (ems) deviceId 221 updated with value 29.2. 2020-09-11 13:51:06.737 (ems - Dallas sensor 1) Updating device from 1:'29.3' to have values 1:'29.2'. 2020-09-11 13:51:06.748 (ems) onMessage called with: PUBLISH 2020-09-11 13:51:07.249 (ems) Heartbeating... 2020-09-11 13:51:07.249 (ems) MqttClient::Ping 2020-09-11 13:51:07.250 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:17.217 (ems) Heartbeating... 2020-09-11 13:51:17.217 (ems) MqttClient::Ping 2020-09-11 13:51:17.268 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:27.234 (ems) Heartbeating... 2020-09-11 13:51:27.234 (ems) MqttClient::Ping 2020-09-11 13:51:27.285 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:36.751 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.25"}}' 2020-09-11 13:51:36.752 (ems) deviceId 221 value has not changed. Device not updated 2020-09-11 13:51:36.752 (ems) onMessage called with: PUBLISH 2020-09-11 13:51:37.253 (ems) Heartbeating... 2020-09-11 13:51:37.253 (ems) MqttClient::Ping 2020-09-11 13:51:37.304 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:40.739 Error: WebServer PO exception occurred : 'stoull' 2020-09-11 13:51:47.221 (ems) Heartbeating... 2020-09-11 13:51:47.221 (ems) MqttClient::Ping 2020-09-11 13:51:47.272 (ems) onMessage called with: PINGRESP 2020-09-11 13:51:57.240 (ems) Heartbeating... 2020-09-11 13:51:57.240 (ems) MqttClient::Ping 2020-09-11 13:51:57.290 (ems) onMessage called with: PINGRESP 2020-09-11 13:52:06.707 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"29.30"}}' 2020-09-11 13:52:06.707 (ems) deviceId 221 updated with value 29.3. 2020-09-11 13:52:06.707 (ems - Dallas sensor 1) Updating device from 1:'29.2' to have values 1:'29.3'. 2020-09-11 13:52:06.718 (ems) onMessage called with: PUBLISH

////////////////////////////////////////////////////////////////////////////////

the next microSD do not work

pi@emonpi:~ $ hostnamectl Static hostname: emonpi Icon name: computer Machine ID: 6cdeb89296d5413097cd476ea2d06f59 Boot ID: 48bca64c8e4840a0b733f9efd1af79f9 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 4.19.97-v7+ Architecture: arm pi@emonpi:~ $

//////////////////////////////////////////////////////////////////////////////// the next microSD do not work

pi@raspberrypi:~ $ hostnamectl Static hostname: raspberrypi Icon name: computer Machine ID: 713228570cdb4a56beaf4e7e71280123 Boot ID: 119209d6ade2471c9532d17ad3abb0b5 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.4.51-v7+ Architecture: arm pi@raspberrypi:~ $ ////////////////////////////////////////////////////////////////////////////////

the next microSD do not work

pi@emonpi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" pi@emonpi:~ $ hostnamectl Static hostname: emonpi Icon name: computer Machine ID: 93708507ae324c39942f74c975c40891 Boot ID: 268eb32c7c0d46f49fd98d8ff5732b31 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.4.51-v7+ Architecture: arm pi@emonpi:~ $

EMONCMS Version low-write 10.2.6 Modules Administration | App v2.1.8 | Backup v2.2.4 | EmonHub Config v2.0.5 | Dashboard v2.0.8 | DemandShaper v1.2.6 | Device v2.0.6 | EventProcesses | Feed | Graph v2.0.9 | Input | Postprocess v2.1.4 | CoreProcess | Schedule | Network Setup v1.0.0 | sync | Time | User | Visualisation | WiFi v2.0.3 Git URL https://github.com/emoncms/emoncms.git Branch * stable Describe 10.2.5-3-gf781bed0

Server OS Linux 5.4.51-v7+ Host emonpi | emonpi | (192.168.0.32) Date 2020-09-11 11:15:31 CEST Uptime 11:15:31 up 16 min, 2 users, load average: 0.04, 0.05, 0.08

HTTP Server Apache/2.4.38 (Raspbian) HTTP/1.1 CGI/1.1 80

MYSQL Version 5.5.5-10.3.23-MariaDB-0+deb10u1 Host localhost:6379 (127.0.0.1) Date 2020-09-11 11:15:31 (UTC 02:00‌​) Stats Uptime: 1397 Threads: 13 Questions: 178 Slow queries: 0 Opens: 46 Flush tables: 1 Open tables: 40 Queries per second avg: 0.127

REDIS Version Redis Server 5.0.3 PHP Redis 5.3.1 Host localhost:6379 Size 18 keys (778.57K) Flush Uptime 0 days

MQTT SERVER Version Mosquitto 1.5.7 Host localhost:1883 (127.0.0.1) PHP Version 7.3.19-1~deb10u1 (Zend Version 3.3.19)

Modules apache2handler calendar Core ctype curl date dom v20031129 exif fileinfo filter ftp gd gettext hash iconv json v1.7.0 libxml mbstring mosquitto v0.4.0 mysqli mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $ openssl pcre PDO pdo_mysql Phar posix readline redis v5.3.1 Reflection session shmop SimpleXML sockets sodium SPL standard sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter xsl Zend OPcache zlib

PI Model Raspberry Pi 3 Model B+ Rev 1.3 - 1GB (Sony UK) RebootShutdown Serial num. DD42754A CPU Temperature 52.08°C GPU Temperature 52.6°C emonpiRelease emonSD-02Oct19 File-system read-write

//////////////////////////////////

jvm1000 commented 4 years ago

Rasbian Stretch from june 2018, domoticz 4.9700

running until this error occurs 2020-09-13 10:05:05.280 Error: WebServer PO exception occurred : 'stoull'

pi@raspberrypi3:~ $ hostnamectl Static hostname: raspberrypi3 Icon name: computer Machine ID: 2f3751f44d134117b60eade7edf8ccee Boot ID: 1ab3f7fcc28a4e049c392de46805cbfd Operating System: Raspbian GNU/Linux 9 (stretch) Kernel: Linux 4.14.78-v7+ Architecture: arm pi@raspberrypi3:~ $

log from domoticz 4.9700

2020-09-13 10:02:19.156 Status: Domoticz V4.9700 (c)2012-2018 GizMoCuz 2020-09-13 10:02:19.156 Status: Build Hash: a3a45906, Date: 2018-06-23 16:24:51 2020-09-13 10:02:19.156 Status: Startup Path: /home/pi/domoticz/ 2020-09-13 10:02:19.235 Status: EventSystem: reset all events... 2020-09-13 10:02:19.490 Status: PluginSystem: Started, Python version '3.5.3'. 2020-09-13 10:02:19.509 Status: WebServer(HTTP) started on address: :: with port 8080 2020-09-13 10:02:19.528 Status: WebServer(SSL) started on address: :: with port 443 2020-09-13 10:02:19.531 Status: Proxymanager started. 2020-09-13 10:02:19.534 Status: TCPServer: shared server started... 2020-09-13 10:02:19.534 Status: RxQueue: queue worker started... 2020-09-13 10:02:21.535 Status: EventSystem: reset all events... 2020-09-13 10:02:21.536 Status: EventSystem: reset all device statuses... 2020-09-13 10:02:21.724 Status: Python EventSystem: Initalizing event module. 2020-09-13 10:02:21.725 Status: EventSystem: Started 2020-09-13 10:02:21.725 Status: EventSystem: Queue thread started... 2020-09-13 10:02:21.738 Status: PluginSystem: Entering work loop. 2020-09-13 10:02:28.457 Status: Incoming connection from: 192.168.0.15 2020-09-13 10:03:06.386 Status: EventSystem: reset all device statuses... 2020-09-13 10:03:36.800 Status: (ems) Started. 2020-09-13 10:03:37.115 (ems) Create Temperature Device HC1 2020-09-13 10:03:37.115 (ems) Creating device 'EMS thermostat current temp HC1'. 2020-09-13 10:03:37.116 (ems) Create Temperature Device HC2 2020-09-13 10:03:37.116 (ems) Creating device 'EMS thermostat current temp HC2'. 2020-09-13 10:03:37.117 (ems) Create Temperature Device HC3 2020-09-13 10:03:37.117 (ems) Creating device 'EMS thermostat current temp HC3'. 2020-09-13 10:03:37.118 (ems) Create Temperature Device HC4 2020-09-13 10:03:37.118 (ems) Creating device 'EMS thermostat current temp HC4'. 2020-09-13 10:03:37.119 (ems) Create Thermostat Setpoint Device HC1 2020-09-13 10:03:37.119 (ems) Creating device 'EMS thermostat setpoint HC1'. 2020-09-13 10:03:37.120 (ems) Create Thermostat Setpoint Device HC2 2020-09-13 10:03:37.120 (ems) Creating device 'EMS thermostat setpoint HC2'. 2020-09-13 10:03:37.121 (ems) Create Thermostat Setpoint Device HC3 2020-09-13 10:03:37.121 (ems) Creating device 'EMS thermostat setpoint HC3'. 2020-09-13 10:03:37.122 (ems) Create Thermostat Setpoint Device HC4 2020-09-13 10:03:37.122 (ems) Creating device 'EMS thermostat setpoint HC4'. 2020-09-13 10:03:37.123 (ems) Create Thermostat mode selector HC1 2020-09-13 10:03:37.123 (ems) Creating device 'Thermostat mode HC1'. 2020-09-13 10:03:37.129 (ems) Create Thermostat mode selector HC2 2020-09-13 10:03:37.129 (ems) Creating device 'Thermostat mode HC2'. 2020-09-13 10:03:37.130 (ems) Create Thermostat mode selector HC3 2020-09-13 10:03:37.130 (ems) Creating device 'Thermostat mode HC3'. 2020-09-13 10:03:37.131 (ems) Create Thermostat mode selector HC4 2020-09-13 10:03:37.131 (ems) Creating device 'Thermostat mode HC4'. 2020-09-13 10:03:37.133 (ems) Create boiler mode selector 2020-09-13 10:03:37.133 (ems) Creating device 'Boiler mode'. 2020-09-13 10:03:37.134 (ems) Create ww mode selector 2020-09-13 10:03:37.134 (ems) Creating device 'ww mode'. 2020-09-13 10:03:37.135 (ems) Create on/off switch (tapwater active) 2020-09-13 10:03:37.135 (ems) Creating device 'Tapwater active'. 2020-09-13 10:03:37.136 (ems) Create on/off switch (heating active) 2020-09-13 10:03:37.136 (ems) Creating device 'Heating active'. 2020-09-13 10:03:37.137 (ems) Create on/off switch (Gateway online/offline) 2020-09-13 10:03:37.137 (ems) Creating device 'Gateway online'. 2020-09-13 10:03:37.138 (ems) Topiclist is: 2020-09-13 10:03:37.138 (ems) ems-esp/thermostat_data, ems-esp/boiler_data, ems-esp/sensors, ems-esp/mixing_data, ems-esp/sm_data, ems-esp/hp_data, ems-esp/heating_active, ems-esp/tapwater_active 2020-09-13 10:03:37.138 (ems) MqttClient::init 2020-09-13 10:03:37.138 (ems) MqttClient::Open 2020-09-13 10:03:37.189 (ems) MqttClient::onConnect 2020-09-13 10:03:37.189 (ems) Successful connect to: 127.0.0.1:1883 2020-09-13 10:03:37.189 (ems) MqttClient::Connect 2020-09-13 10:03:37.189 (ems) MQTT CONNECT ID: 'Domoticz_1599984217' 2020-09-13 10:03:37.239 (ems) onMQTTConnected 2020-09-13 10:03:37.239 (ems) MqttClient::Subscribe 2020-09-13 10:03:37.239 (ems) onMessage called with: CONNACK 2020-09-13 10:03:37.290 (ems) onMQTTSubscribed 2020-09-13 10:03:37.290 (ems) onMessage called with: SUBACK 2020-09-13 10:03:37.034 Status: (ems) Entering work loop. 2020-09-13 10:03:37.034 Status: (ems) Initialized version 1.0 2020-09-13 10:03:46.554 (ems) Heartbeating... 2020-09-13 10:03:46.554 (ems) MqttClient::Ping 2020-09-13 10:03:46.605 (ems) onMessage called with: PINGRESP 2020-09-13 10:03:50.449 Status: EventSystem: reset all device statuses... 2020-09-13 10:03:52.230 Status: EventSystem: reset all device statuses... 2020-09-13 10:03:56.572 (ems) Heartbeating... 2020-09-13 10:03:56.572 (ems) MqttClient::Ping 2020-09-13 10:03:56.622 (ems) onMessage called with: PINGRESP 2020-09-13 10:03:56.780 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"28.12"}}' 2020-09-13 10:03:56.780 (ems) Create temperature device (Dallas sensor 1) 2020-09-13 10:03:56.780 (ems) Creating device 'Dallas sensor 1'. 2020-09-13 10:03:56.783 (ems) Create temperature device (Dallas sensor 2) 2020-09-13 10:03:56.784 (ems) Creating device 'Dallas sensor 2'. 2020-09-13 10:03:56.785 (ems) Create temperature device (Dallas sensor 3) 2020-09-13 10:03:56.786 (ems) Creating device 'Dallas sensor 3'. 2020-09-13 10:03:56.788 (ems) Create temperature device (Dallas sensor 4) 2020-09-13 10:03:56.788 (ems) Creating device 'Dallas sensor 4'. 2020-09-13 10:03:56.790 (ems) Create temperature device (Dallas sensor 5) 2020-09-13 10:03:56.790 (ems) Creating device 'Dallas sensor 5'. 2020-09-13 10:03:56.792 (ems) deviceId 221 updated with value 28.1. 2020-09-13 10:03:56.792 (ems - Dallas sensor 1) Updating device from 0:'' to have values 1:'28.1'. 2020-09-13 10:03:56.794 (ems) onMessage called with: PUBLISH 2020-09-13 10:04:06.560 (ems) Heartbeating... 2020-09-13 10:04:06.560 (ems) MqttClient::Ping 2020-09-13 10:04:06.610 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:16.576 (ems) Heartbeating... 2020-09-13 10:04:16.576 (ems) MqttClient::Ping 2020-09-13 10:04:16.626 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:21.063 Status: EventSystem: reset all device statuses... 2020-09-13 10:04:26.544 (ems) Heartbeating... 2020-09-13 10:04:26.544 (ems) MqttClient::Ping 2020-09-13 10:04:26.595 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:26.795 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"28.12"}}' 2020-09-13 10:04:26.796 (ems) deviceId 221 value has not changed. Device not updated 2020-09-13 10:04:26.796 (ems) onMessage called with: PUBLISH 2020-09-13 10:04:26.018 Status: EventSystem: reset all device statuses... 2020-09-13 10:04:34.867 Status: EventSystem: reset all device statuses... 2020-09-13 10:04:36.562 (ems) Heartbeating... 2020-09-13 10:04:36.562 (ems) MqttClient::Ping 2020-09-13 10:04:36.563 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:46.578 (ems) Heartbeating... 2020-09-13 10:04:46.578 (ems) MqttClient::Ping 2020-09-13 10:04:46.579 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:56.596 (ems) Heartbeating... 2020-09-13 10:04:56.596 (ems) MqttClient::Ping 2020-09-13 10:04:56.596 (ems) onMessage called with: PINGRESP 2020-09-13 10:04:56.797 (ems) MQTT message: ems-esp/sensors b'{"sensor1":{"id":"28-274C-79A2-0003-85","temp":"28.12"}}' 2020-09-13 10:04:56.798 (ems) deviceId 221 value has not changed. Device not updated 2020-09-13 10:04:56.798 (ems) onMessage called with: PUBLISH 2020-09-13 10:05:05.280 Error: WebServer PO exception occurred : 'stoull' 2020-09-13 10:05:06.565 (ems) Heartbeating... 2020-09-13 10:05:06.565 (ems) MqttClient::Ping 2020-09-13 10:05:06.565 (ems) onMessage called with: PINGRESP 2020-09-13 10:05:16.583 (ems) Heartbeating... 2020-09-13 10:05:16.583 (ems) MqttClient::Ping 2020-09-13 10:05:16.583 (ems) onMessage called with: PINGRESP 2020-09-13 10:05:21.067 Error: WebServer PO exception occurred : 'stoull'

bbqkees commented 4 years ago

@jvm1000 can you remove the 6 meter devices from the list and see if it helps?

I have 4 different test systems myself but I can't replicate this problem. The 'stoull' error comes from Domoticz itself not from the plugin. It seems like some value is being converted but it fails.

Can everyone with this problem post a payload of all topics? (www.mqtt-explorer.com) Maybe you are having some parameters in it that I don't have here that cause panic in Domoticz.

bbqkees commented 4 years ago

It appears that with the new dev-2 plugin this might be solved. One user that had this problem reported it now works with the new plugin. I will push the updates to the main branch soon.

bbqkees commented 4 years ago

This seems to be solved with the new plugin version for V2.1.