Domoticz

Posted: **Friday 01 March 2019 16:28**

Daffy61 wrote: ↑Friday 01 March 2019 16:24 I've serveral times install/uninstall the toonapilib 3.0.2 en python3.5, and read the installation guide from github.com/JohnvandeVrugt/toonapilib4domoticz.
After the installation i restart domoticz or reboot my RPI3.
I add the toonapilib, and fill in the credentials they are nessesary.
The logging give the messages (Toon) Creating Toon devices.....!
But nothing is happened, and there are no devices added.

In the logging i see the folowing messages:
2019-03-01 15:55:02.730 (Toon) An error occurred updating power usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating gas usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating temperature
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat state
2019-03-01 15:55:02.731 (Toon) An error occurred updating burner state
When i set de debug mode for the toonapilib, i see the temperture value and gas value etc. but, no devices

What's going wrong..?

Best is to install toonapilib version 3.0.10 now, version 3.0.2 is no longer necessary.

Furthermore the devices are probably created but not yet visible, you have to go into Setup --> devices and then add them.

Posted: **Friday 01 March 2019 16:36**

darkrain wrote: ↑Friday 01 March 2019 16:28
Daffy61 wrote: ↑Friday 01 March 2019 16:24 I've serveral times install/uninstall the toonapilib 3.0.2 en python3.5, and read the installation guide from github.com/JohnvandeVrugt/toonapilib4domoticz.
After the installation i restart domoticz or reboot my RPI3.
I add the toonapilib, and fill in the credentials they are nessesary.
The logging give the messages (Toon) Creating Toon devices.....!
But nothing is happened, and there are no devices added.

In the logging i see the folowing messages:
2019-03-01 15:55:02.730 (Toon) An error occurred updating power usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating gas usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating temperature
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat state
2019-03-01 15:55:02.731 (Toon) An error occurred updating burner state
When i set de debug mode for the toonapilib, i see the temperture value and gas value etc. but, no devices

What's going wrong..?
Best is to install toonapilib version 3.0.10 now, version 3.0.2 is no longer necessary.

Furthermore the devices are probably created but not yet visible, you have to go into Setup --> devices and then add them.

Thanks, i'll try these options...!

Posted: **Friday 01 March 2019 16:45**

dressie wrote: ↑Friday 01 March 2019 7:48 Next step is being able to control the Toon through another Domoticz Server. Our main one is a stable one while I run this API through a beta one. I did connect both Domoticz servers but the devices arn't created on the stable one. I did install the API on the stable one, but it doesn't seem to run by itself, hence the option to do it this way.
Any thoughts?

This afternoon I tried to get the plugin running with the latest stable domoticz version.
The onStart method is not called, so no devices are created.

First I needed to symlink some python libs to make the plugin being loaded.

Code: Select all

sudo ln -s /usr/local/lib/python3.5/dist-packages/toonapilib /usr/lib/python3.5/toonapilib
sudo ln -s /usr/local/lib/python3.5/dist-packages/coloredlogs /usr/lib/python3.5/coloredlogs
sudo ln -s /usr/local/lib/python3.5/dist-packages/humanfriendly /usr/lib/python3.5/humanfriendly

However, I cannot make it work. Relates to https://www.domoticz.com/forum/viewtopi ... 65&t=27096
Even when I import the toonapilib at a later stage, the plugin stops working.
This is probably also related to the fact that you have to restart domoticz after changing parameters in the hardware section.

Posted: **Friday 01 March 2019 16:55**

Daffy61 wrote: ↑Friday 01 March 2019 16:36
darkrain wrote: ↑Friday 01 March 2019 16:28
Daffy61 wrote: ↑Friday 01 March 2019 16:24 I've serveral times install/uninstall the toonapilib 3.0.2 en python3.5, and read the installation guide from github.com/JohnvandeVrugt/toonapilib4domoticz.
After the installation i restart domoticz or reboot my RPI3.
I add the toonapilib, and fill in the credentials they are nessesary.
The logging give the messages (Toon) Creating Toon devices.....!
But nothing is happened, and there are no devices added.

In the logging i see the folowing messages:
2019-03-01 15:55:02.730 (Toon) An error occurred updating power usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating gas usage
2019-03-01 15:55:02.730 (Toon) An error occurred updating temperature
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat
2019-03-01 15:55:02.731 (Toon) An error occurred updating thermostat state
2019-03-01 15:55:02.731 (Toon) An error occurred updating burner state
When i set de debug mode for the toonapilib, i see the temperture value and gas value etc. but, no devices

What's going wrong..?
Best is to install toonapilib version 3.0.10 now, version 3.0.2 is no longer necessary.

Furthermore the devices are probably created but not yet visible, you have to go into Setup --> devices and then add them.

Thanks, i'll try these options...!

toonapilib 3.0.10 is installed, detecting new device is turned on....but no results...!

Posted: **Friday 01 March 2019 18:25**

waspy wrote: ↑Friday 01 March 2019 12:41
eenernl wrote: ↑Friday 01 March 2019 7:21
eenernl wrote: ↑Friday 01 March 2019 1:39 It looks like the room temperature sensor has a precision of 0,5 degrees? Just like it’s displayed on the Toon itself.

The previous integration had a precision of 0,1 degrees. Is this possible to change? Then the measurement will be more accurate.
you see?

A99673DA-F891-4612-B676-F1C90EBE50E2.jpeg
The temperature is retrieved through the toonapilib which reads the currentDisplayTemp variable from the Toon web api.
There are not other temperature readings that can be used to have a more accurate reading.
Apparently, the precision of this and other temperature related variables is 0.5 degrees.
One can argue how accurate the temperature reading actually is...

Hmm... previously the precision was 0.1 degrees.
More accurate then the displayed value. There should be a possibility to get the real measured value.

If I look at https://toonapilib.readthedocs.io/en/la ... pilib.html I think it should possible.

: C2AE20D2-2306-4630-899E-AB0E2D52EB1F.jpeg (202.1 KiB) Viewed 2039 times

Posted: **Friday 01 March 2019 18:38**

That's exactly the attribute I use.
The eneco servers do not expose the 0.1 precision readings anymore. It exposes only the displayed toon temperature. Which has a 0.5 degree rounding.

Verstuurd vanaf mijn SM-G935F met Tapatalk

Posted: **Friday 01 March 2019 19:25**

Are you sure?
Because there is also a value for the displayed temperature:

: 2253A351-439C-4AC0-BED2-21EE88B38339.jpeg (238.9 KiB) Viewed 2033 times

Can’t we ask quby for this?

Posted: **Saturday 02 March 2019 21:17**

Thanks waspy for helping out before! I wanted to add a bit more customization so I've just been playing around with some python that uses the latest toonapilib library. The Lua scripts that controlled the thermostate state or setpoint temperatures are now working smoothly again.

I've added currentModulationLevel (also see below) in Domoticz as well as a temperature device. It's interesting to compare that value to the temperature of the water that flows out of the boiler/CV.

And yes the precision readings are not accesible at the moment:

Code: Select all

{
  "currentSetpoint": 2000,
  "currentDisplayTemp": 2000,
  "programState": 0,
  "activeState": 1,
  "nextProgram": -1,
  "nextState": -1,
  "nextTime": 0,
  "nextSetpoint": 0,
  "errorFound": 255,
  "boilerModuleConnected": 1,
  "realSetpoint": 2000,
  "burnerInfo": "1",
  "otCommError": "0",
  "currentModulationLevel": 19,
  "haveOTBoiler": 1,
}

.. is as good as it gets but that's okay for most intents and purposes.

Posted: **Saturday 02 March 2019 22:28**

On this side the Windows version is also working now!

Like the Raspberry version you must also run the beta version in Windows

Only I get now in the log file that there is an problem with creating the Toon Devices.

Posted: **Sunday 03 March 2019 14:03**

Maybe some what off-toppic (hope i'm excused and not executed

):

Due missing support (at this time

) for the Fibaro Smart plugs controlled by Toon I wanted to connect the Smart plug via my Aeotec Z-Wave USB controller on Domoticz.
But the Smart plug is included and controlled via Toon itself already. I can't include the plug also on the ZWave USB stick (Only by exclude first on Toon but don't want this).

I was reading something about using Domoticz as "Secondary controller" but can't figure it out how this works with the Toon controller.
https://www.domoticz.com/wiki/Zwave#Run ... controller

I have made an another topic about this on this forum:
https://www.domoticz.com/forum/viewtopi ... 24&t=27203
Thought I will share this...

Posted: **Sunday 03 March 2019 15:00**

Anybody knows what's going on here? domoticz crashes when using this toonapilib4domoticz??

When adding toonapilib & toonapilib4domoticz domoticz crashes with segmentation error ..
Python 3.6.8 on voidlinux rpi2, domoticz beta
Tested with toonapilib (without domoticz), that is fine. Just integration with domoticz crashes domoticz??

Code: Select all

Status: (ToonThermostaat1) Initialized version 1.0.12, author 'John van de Vrugt'
(ToonThermostaat1) Starting toonapilib4domoticz with debug logging
(ToonThermostaat1) Creating toonapilib object
Domoticz(pid:4966, tid:4969('PluginMgr')) received fatal signal 11 (Segmentation fault)
Error: siginfo address=0x1300046, address=0x6ff32f9c
Error: Failed to start gdb, will use backtrace() for printing stack frame
Error: #0  /home/domoticz/app/domoticz() [0x2d6d9c]
Error: #1  /home/domoticz/app/domoticz : signal_handler(int, siginfo_t*, void*) + 0x27c [0x2d7830]
Error: #2  /usr/lib/libc.so.6 : __default_rt_sa_restorer + 0 [0x76c17310]

Posted: **Sunday 03 March 2019 16:48**

phoenixblue wrote:On this side the Windows version is also working now!

Like the Raspberry version you must also run the beta version in Windows

Only I get now in the log file that there is an problem with creating the Toon Devices.

Also this issue solved, I have accept new devices for 5 min. So the plugin can made new devices.

Verstuurd vanaf mijn CLT-L29 met Tapatalk

Posted: **Tuesday 05 March 2019 9:02**

Ritchie wrote: ↑Friday 01 March 2019 9:51
rene2716 wrote: ↑Friday 01 March 2019 8:28
Ritchie wrote: ↑Thursday 28 February 2019 19:27

This might be the cause of the issue I am facing, no power updates for some times:

2019-02-28 19:17:39.127 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:19:39.249 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:21:39.390 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:23:39.515 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:25:39.616 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:27:39.740 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:29:39.812 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:31:39.863 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
2019-02-28 19:33:40.989 (Toon) Update power/solar usage: 6290709;4293963;0;0;285;0
correct, i see the same behaviour and also the toon app stalls at that same moment. A developper from quby is checking the logs and getting back to me today to see if its their side or the apilib
Thanks, awaiting their answer.

Hi,

Well the problem is clear, alltough on my side. Olisto webhooks are interfering with api calls. After troubleshooting with quby we found dat disabeling the olisto toon channel helped to get back readings without nil values. And no more stalls on the toon app also. The stall happens every hour on minute 31. Quby is working on a solution on this, they will keep me posted.

Furthermore Quby todl me regarding the api :
The moment you get a token and make the first /status call, our backend will start a subscription to your device. This is active for 2 minutes. The token itself is valid for 30 minutes.

And also that toon refreshes data on demand, so every change in readings is reported to the backend where the api is talking to

hope this helps

Posted: **Tuesday 05 March 2019 10:02**

rene2716 wrote: ↑Tuesday 05 March 2019 9:02
Ritchie wrote: ↑Friday 01 March 2019 9:51
rene2716 wrote: ↑Friday 01 March 2019 8:28

correct, i see the same behaviour and also the toon app stalls at that same moment. A developper from quby is checking the logs and getting back to me today to see if its their side or the apilib
Thanks, awaiting their answer.
Hi,

Well the problem is clear, alltough on my side. Olisto webhooks are interfering with api calls. After troubleshooting with quby we found dat disabeling the olisto toon channel helped to get back readings without nil values. And no more stalls on the toon app also. The stall happens every hour on minute 31. Quby is working on a solution on this, they will keep me posted.

Furthermore Quby todl me regarding the api :
The moment you get a token and make the first /status call, our backend will start a subscription to your device. This is active for 2 minutes. The token itself is valid for 30 minutes.

And also that toon refreshes data on demand, so every change in readings is reported to the backend where the api is talking to

hope this helps

Ah! I indeed have the Olisto app as well, I will disable the Toon channel for now. Thanks!

Posted: **Tuesday 05 March 2019 10:08**

Checked everything at least three times, but still

2019-03-05 10:02:42.027 (Toon) Using toonapilib version : 3.1.0 by Costas Tyfoxylos <[email protected]>
2019-03-05 10:02:42.523 (Toon) Could not create a toonapilib object
2019-03-05 10:02:42.525 (Toon) Possible solution:
2019-03-05 10:02:42.525 (Toon) * Check your credentials
2019-03-05 10:02:42.525 (Toon) * Restart Domoticz

Using the credentials and API keys that I got from the developers site (under apps), and with localhost as callback url.

Posted: **Tuesday 05 March 2019 10:12**

EdwinK wrote: ↑Tuesday 05 March 2019 10:08 Checked everything at least three times, but still

2019-03-05 10:02:42.027 (Toon) Using toonapilib version : 3.1.0 by Costas Tyfoxylos <[email protected]>
2019-03-05 10:02:42.523 (Toon) Could not create a toonapilib object
2019-03-05 10:02:42.525 (Toon) Possible solution:
2019-03-05 10:02:42.525 (Toon) * Check your credentials
2019-03-05 10:02:42.525 (Toon) * Restart Domoticz
Using the credentials and API keys that I got from the developers site (under apps), and with localhost as callback url.

did you use the mijn eneco credentials? developper site credentials do not work. Did you enable accpet new hardware in domoticz?

Posted: **Tuesday 05 March 2019 10:18**

Yes, used the mijn eneco crednetials, and new hardware was enabled.

Posted: **Tuesday 05 March 2019 10:24**

EdwinK wrote: ↑Tuesday 05 March 2019 10:18 Yes, used the mijn eneco crednetials, and new hardware was enabled.

and you use the latest domoticz beta, and you did a pi reboot and sudo service domoticz start ?
if that all doesnt work i suggest a reinstall of the toonapilib and python script, should work

Posted: **Tuesday 05 March 2019 10:25**

Yup, did all that.
I think Toon hates me...

Trying it some more later

Posted: **Tuesday 05 March 2019 22:09**

After some testing and updating sessions... everything works as it should be. With the ToonApiLib 3.2.0 and the latest plugin.py of the ToonApiLib4Domoticz (and the latest Beta of Domoticz). Setting and reading the state (whether program on or off), setting the setpoint, everything OK. Thanks to all programmers!

Domoticz

Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat

Re: Error ToonThermostat