I can not discover Homeduino rfdevices (nor through debug messages).
I manually added all rfdevices (from pimatic 0.8.107). The only way it works
The only devices discovered:
pimatic-ping: Scanning 192.168.1.220/24
pimatic-mysensors: Searching for nodes
pimatic-milight-reloaded: Scanning 192.168.1.0/24
-
Questions about the release of v0.9
-
@Andi-Tudor
in the announcement threat on the bottom you can read about this. You need to set the following on the config.json"debug": true, "logLevel": "debug",
So you can see the debug messages again.
A discovery for Homeduino rf devices is not yet implemented.
But if you have your debug data you are now able to quickly create a new device on the fly with the device editor.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
GUYS PLS. OPEN A NEW THREAD FOR EACH ISSUE
This here is getting complicated to follow and to answer.
Thx!!pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Hi everyone,
what are the new features of 0.9?
Cheers,
Leopold -
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@Anduril said in Questions about the release of v0.9:
I have updated my pimatic until step 5 of the procedure in the announcement. But then I can’t start it using the link
pimatic.js
. Also in myusr/local/lib/node_modules
there is only one entry,npm
.
So how to start pimatic 0.9?Do a
cd /usr/local/bin sudo ln -s /home/pi/pimatic-app/node_modules/pimatic/pimatic.js
Locations have changed. I had the same.
-
@Harry-van-der-Wolf said in Questions about the release of v0.9:
cd /usr/local/bin
sudo ln -s /home/pi/Or simply use
sudo npm link
which works great if you have a proper node setup. See also “Installing Globally” at https://pimatic.org/guide/getting-started/running/"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@kwittwer
the errors you see don’t really matter.
pimatic should start anywaypimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@Harry-van-der-Wolf @mwittig yeah if done this just yesterday evening and recreated the link. Seems to be working fine. Thank you.
-
Hello,
i found out that the permissions for the user don’t work.example:
"users": [ { "username": "user1", "password": "xxxxxxxxxx", "role": "admin" }, { "username": "user2", "password": "xxxxxxxxxx", "role": "user" } ], "roles": [ { "name": "admin", "permissions": { "pages": "write", "rules": "write", "variables": "write", "messages": "write", "events": "write", "devices": "write", "groups": "write", "plugins": "write", "updates": "write", "database": "write", "config": "write", "controlDevices": true, "restart": true } }, { "name": "user", "permissions": { "pages": "read", "rules": "read", "variables": "read", "messages": "read", "events": "read", "devices": "read", "groups": "read", "plugins": "read", "updates": "read", "database": "read", "config": "read", "controlDevices": false, "restart": false } } ],
user 2 can also add/change devices in the webfrontend.
Don’t know if this was working in v0.8. Didn’t use it there. But now i need this feature…edit:
devices,plugins,updates seems to have still write rights.
the rest has just read right.Mit freundlichen Grüßen
Chris -
@chris Most likely a bug - filed as https://github.com/pimatic/pimatic/issues/932
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Hi All, i have since 0.9 a problem with the following rule.
Then set $Oel-gestern to $Oel-dieser and after 100 ms set $Oel-volumen to round(($Oel-flaeche * ($Oel-hoehe-voll-($oelhoehe-gefilter*10))),0) and after 200 ms set $Oel-einsparung = round((1 - ($Oel-dieser/$Oel-letzter))*100,0) and after 300 ms set $Oel-dieser to round($Oel-volumen-zwischen - $Oel-volumen,0) and after 400 ms set $Oel-tagesverbrauch = round($Oel-dieser - $Oel-gestern,0)
For example start with this:
$Oel-gestern = 0 $Oel-volumen = 1920 $Oel-volumen-zwischen = 1920 $Oel-tagesverbrauch = 0
now at 6:00 the rule will be triggered.
$Oel-volumen-zwischen = 1920 new $Oel-volumen = 1910 new $Oel-gestern = 0 new $Oel-dieser = 10 new $Oel-tagesverbrauch = 10
next day: at 6:00
$Oel-volumen-zwischen = 1920 new $Oel-volumen = 1890 new $Oel-gestern = 10 new $Oel-dieser = 30 new $Oel-tagesverbrauch = 20
this was working with 0.8 and now with 0.9
i get this:
$Oel-volumen-zwischen = 1920 new $Oel-volumen = 1910 new $Oel-gestern = 0 new $Oel-dieser = 0 new $Oel-tagesverbrauch = 0
This part will not be trigggered
and after 300 ms set $Oel-dieser to round($Oel-volumen-zwischen - $Oel-volumen,0) and after 400 ms set $Oel-tagesverbrauch = round($Oel-dieser - $Oel-gestern,0)
hope i can descibe the problem clear enough so you guys understand it.
Thanks in advance. -
On my v0.9 System I can’t get updates…
Error message as picture in the link.
Error MessageBecause I can access my system via Internet the error is a bit curious…
Mit freundlichen Grüßen
Chris -
A few days ago I updated to pimatic v0.9, which neatly converted my old config.json. My question is whether it is possible to import the historical data from the old database?
-
@Rene-Arts
you can copy the sqlite database from v0.8
should work as testet here https://forum.pimatic.org/topic/1940/database@chris
still having this issue?pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Thanks, I tried to merge the new database with the old one, without luck --> I am not quite a database specialist. Though then I just replaced the new database with my old one and stuff works fine. Lost the last few days, but that is far better than losing an entire year
Really love pimatic 0.9 by the way, I seems to react a lot faster and the new configuration options via the GUI are great! -
@leader21
Yes the issue is still alive.Have found another info to npm…
See the picture below.
Update-issueMit freundlichen Grüßen
Chris -
@Chris You mention “Because I can access my system via Internet the error is a bit curious…”.
No it is not. If you can access your system from internet it means that you either- connect to the ip-address of your router, which will be forwarded and will always works if your router is correctly configured
- or to a domain name which will works if dns is correctly configured on that pc that you use to access your pimatic server.
That doesn’t mean dns is correctly configured on your pimatic box itself.
Try to do a ping from the command line from your pimatic box itself, likeping api.pimatic.org
and see if that works.
If that works there is indeed a strange issue with pimatic.If that ping doesn’t work I assume your pimatic server has a static ip-address but you forgot to configure the dns servers on your pimatic box which will take care of resolving the api.pimatic.org address from your pimatic box.
If you use a static ip please check your
/etc/resolv.conf
for correct dns servers. You can always enter in that resolv.conf file the following serversnameserver 8.8.8.8 nameserver 8.8.4.4
which are the Google dns servers and which are actually a huge number of dns servers so there are always hundreds of them up and running.
-
@chris check harry’s suggestion above.
If it fails I will take it to the team.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Hello @Harry-van-der-Wolf and @leader21
yes ping the api works.
i get this back.PING api.pimatic.org (37.120.167.13) 56(84) bytes of data. 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=2 ttl=57 time=21.4 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=3 ttl=57 time=28.1 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=4 ttl=57 time=21.6 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=5 ttl=57 time=21.5 ms
my network looks like the following.
Here i have a Windows Exchange Server wich is the dhcp-server and a fritzbox wich is the gateway.
In the DHCP server a made a reservation for the IP of the Raspberry.
So that he always gets the right/same IP.mfg
Chris